4 ms·
The problem, I think, is that OOP is teach with lots of inheritance. And people think is all about inheritance, and is the only valid tool. Correctly (sparingly
by f1shy 4y ago
The problem, I think, is that OOP is teach with lots of inheritance. And people think is all about inheritance, and is the only valid tool.
Correctly (sparingly) used is ok, but 99% of the time is over used. That is the "All has to inherit from something" illness.
Another thing that is overused is hiding: all has to be private, all accessed through getters/setters, all so deeply hidden as possible...
OOP has good ideas, but they have their place. They are way way way to much overused.
- menaerus 4y agoAgreed. OOP is a valid tool and we use tools to solve problems but the moment it becomes a wrong tool to use is when you find yourself trying hard to retrofit the original problem only so that it can match your abstract OOP puzzle. That's just calling for more problems in my experience.