[UPHPU] Is OOP really bad in PHP?

[Scott Hill]

On Wed, May 14, 2008 at 11:20 AM, Sean <sean at lookin3d.com> wrote:

> Nathan Lane wrote:
>
>> This site, http://reinholdweber.com/?p=19, seems to say that OOP is bad
>> in
>> PHP - like #26 and #27 give me this impression. Is that really true? If
>> so,
>> then why is PHP 5 even more heavily OOP-based than previous versions?
>>
>>
>>
> After reading his list of 40, I would love to see this guy's code, it's
> probably garbage...
>

Shouldn't we really be looking at the results of his code?  It's difficult
for me to judge a person based on their code.  I mean, if it works, isn't
that enough?  As a C++ programmer, my performance is judged by whether the
program I wrote works and follows specs and is done on time (or within a
reasonable time period).  The people who control my financial destiny here
at work could give a bleep less what my code looks like or how it is
organized.  With PHP shouldn't we be looking at the web site or web app to
determine whether or not it is good?  I know it's different if you are on
the unpleasant end of cleaning up someone else's mess but since most
programmers evolve and improve with time, it seems that we should give
everyone the benefit of the doubt.  I would hate to have to even look at
code that I wrote 20 years ago (the computer systems that ran that code
don't even exist any more).  It would probably look like crap to me now.
However, since I am still gainfully employed, I have to assume that none of
the employers I have worked for (including myself) ever took that old code
into consideration.  Like I said, it's very frustrating to have to work with
code that we're "not used to".  But we can look forward with the hope that
they have improved even if the improvement is only in their own minds.

IMHO

-- 
Scott Hill

Food for thought:
An eagle may soar but a weasel will never get sucked into a jet engine.
A closed mouth gathers no foot.
Never squat with your spurs on.