Please refrain from such self-centered, flippant dismissals. They tend to get in the way of potentially good discussions. >>Clearly OOP works for a lot of peop

Please refrain from such self-centered, flippant dismissals. They tend to get in the way of potentially good discussions. >>Clearly OOP works for a lot of people. Something can work for a lot of people, and still suck. >> If it doesn't work for you, don't use it. Language and tool choices in our industry are made by a tiny minority. In fact, sometimes the people making those decisions are not even developers themselves! From that perspective alone, articles like this one are valuable. Aside from that though, the question isn't whether OOP "works" or not. Rather, it is when it works, and for how long, until you run into a myriad of problems, such as leaky abstractions or inheritance hell. These are worth discussing. If you disagree, you can move on. No need to voice your misgivings.