"10 things I hate about oop" notes
OOP is that it isn’t a paradigm like procedural, logic or functional programming. Instead, OOP says “for every problem you should design your own paradigm”
Obviously this seems like a bad idea. This means everything requires the reader to learn your new ad-hoc paradigm
OOP is about taming complexity through modeling
"We thought that OO conferences like ECOOP, OOPSLA and TOOLS would last for 4 or 5 years and then fade into the mainstream"
- shouldn't it? If it's so hard to do right is there a way?
"Clearly classes should be great. Our brain excels at classifying everything around us. So it seems natural to classify everything in OO programs too.
However, in the real world, there are only objects. Classes exist only in our minds."
Classes shouldn't be as real as they seem in object oriented code. The fact that changing a class causes a huge ripple of change throughout our code seems to indicate they aren't what they say they are
http://blog.jot.fm/2010/08/26/ten-things-i-hate-about-object-oriented-programming/comment-page-2/
Tags: OOP, Best practices, Complexity, Refactoring