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>)
>
> As for the content of the article - the author is entitled to vent out his
> grievances against the OOP. This does not make OOP less effective and
> efficient in solving many real-life, very complex problems, and delivering
> more robust solutions with fewer resources committed. This is my personal
> experience, and it just happens to coninside with the generally recognized
> virtues of OOP.
Totally agree. When OOP is appropriate it is a very powerful tool, and
there are a lot of situations where it is, or can be, appropriate.
Again, my impression of the web site is that the author has issues with
OOP being used unconditionally, without further thought. So the author
has indicated some areas where it may not be appropriate, or where there
have been difficulties.