Posted by Scott Auge on 07/19/05 17:29

In article <1121777730.300672.138240@g47g2000cwa.googlegroups.com>,
"dracolytch" <dracolytch@gmail.com> wrote:

> Alright, this is a controvercial question for my fellow gurus: Why do
> we bother with Object-Oriented programming in a web environment?
>
> The web, by nature, is a stateless environment. Web-based applications
> are, on the whole, fairly uncomplicated things. Objects are, generally,
> conceptually thought of as entities that have a lifespan. Having an
> object survive for longer than the execution of a single page can be a
> pain. Having an object only survive for one page hardly seems worth the
> trouble.
>
> Encapsulation, the grouping of like concepts, can be done with a well
> thought-out library, or even file naming structure.
> I don't think I have ever used inhertiance or true polymorphism in any
> web project, ever.
>
> So what gives? Why are people using mysql_fetch_object instead of
> mysql_fetch_array? Is it habit? Is it what we're taught? Do we percieve
> some additional value?
>
> ~D

1)

Well, I would disagree with the idea of Web based applications are
fairly uncomplicated things. Explain that to salesforce.com or the
multitude of other web based app servers popping up.

If anything, web apps are becoming more and more complicated every year.

2)

OOP is an application design method. If you like:

Note_Add()
Note_Delete()
Note_Update()

and it works for you - that is fine and dandy. People have been doing
that for years and years.

Personally I like the level of encapsulation of data and level of
abstraction OOP can provide.

[Back to original message]