Lunacy has a name: OOP Is Much Better in Theory Than in Practice

I was doing more digging in the area of software development improvement and stumbled across the article “OOP Is Much Better in Theory Than in Practice” by accident.  (It was referred to by a Design Patterns/GoF anniversary article I was reading.)

While I believe that Richard Mansfield has a few solid points (like few people understand OO, it’s more intellectually challenging than procedural code (my words), etc.)  However, I fundamentally disagree that OO is not the right way for every mainstream business application to be written.  I understand that real-time systems, operating systems, and a variety of other specialized applications shouldn’t use OO as their fundamental design foundation, but in just about every other case, the benefits seem to far out weigh the down sides.

This is just a reminder to me that we have a long way to go to get everyone to understand not only the how of OO but the why as well.