Most of the times, OOP is overrated, and OOP languages are bloated pieces of shit, if not braindead and broken in several parts, like Java. People, especially managers, think OOP is some sort of panacea which is more correct, more productive and more maintainable than other approaches, and I estimate that 50%-67% of the times they are wrong. Each problem is different and different paradigms fit different programs. The most productive language is the one that doesn't shove OOP up your ass, but allows you to design your own object system (and provides a working one as an additional feature) and allows you to use the appropriate tools for the job, mixing imperative, OOP, functional and declarative programming, and maybe providing additional features such as easy domain-specific language creation.
I like OOP for what it's good at, but I don't understand why do ENTERPRISE morons get so excited with it. They just got to fap over it like they do over XML, SOAP, and all that. Just magazine/"blog" hype. They could just as easily have taken any other feature, such as continuations or regular expressions, build a whole industry around it, get obsessed with it, and end up misusing it most of the time.
>>3
Ah, design patterns. More enterprise bullshit. Glorified copypasta. Enterprise faggots managed to convert the questionable practice of copypasta into a Best Practice™, selling books and writing bullshit articles in the process. Enhance your business with design patterns. They include the most retarded forced OOP crap ever, which should be the very examples of where
not to use OOP.
>>5
This man understands OOP.