2 ms·
For those who will vote this up without bothering to read past the title: the conclusion is that no, OOP is not responsible for bad programming. Bad programmer
by timr 18y ago
For those who will vote this up without bothering to read past the title: the conclusion is that no, OOP is not responsible for bad programming. Bad programmers are responsible for bad programming.
News at 11.
- joe_the_user 18y agoOOP has had several phases. The first phase conflated encapsulation into objects with generic reuse. It also advocated complex object diagrams, deep inheritance trees and a variety of over-elaborate approaches. The second phase was more closely related to patterns and agile methologies. Here, the illusion of OOP creating generic reuse was abandoned, the idea of "containment over inheritance" was broached, and the paradigm became closer to "the right tool for the job". I am actually amazed that methodologies were able to improve but I can't argue with what I've seen.