Subject and tackle are typical troll style, but assuming you are not a
trolling idiot ...

The way I read it, [s]he's basically saying there are parts of OOP that
causes major pain in the niche in which [s]he's working.  Also says
there are some areas in which OOP is useful.  (Seems fair.)

Scanning though the page, I find many of the statements are attempts to
debunk the OOP _religion_ rather than OOP per-se, and the author expresses
a lot of frustration at the idea of OOP being the do-all and end-all of
programming.  (See where religious fanaticism gets the world?)

IOW, there seem to be a fair number of comments around 'use it as a tool,
and use the tool where appropriate, but don't follow blindly.'   (This is
bad, how?)

IMO, there's nothing wrong with the author's conclusion, just the same
as it's not wrong to use languages other than Java - when appropriate.

(and now, to give thanks to gmail for their filters <g>)

<posted & mailed>

OOP is bad the same way procedural programming is, or aspect-oriented
programming is, etc. A decent programmer will tell you that ideally you
want to use the right tool for the job. Sometimes OOP is, sometimes it
isn't. If you're good at what you do, you'll know the difference.

Keep in mind, there are frequently bureaucractic / political / financial /
contractual reasons why you don't use the best tool for the job. That will
always be true.

OOP is very good IF you know how to use it.  it is terribly abstract when
implimented properly

Just because you know JAVA doent mean you are a OOP Programmer.

OOP is nessesary for very large projects, but for 99% of projects it is not
ness.

OOP must be adhered to religiously if it is to be a success in a large
project otherwise ,like the author said, it will be unnessesarily
complicated with no other derived benefits

Java is Great OOP is OK,

I like java for the API hands down

Sean