@jinpa said in Standarditis:
Is Object-Oriented Programming the best programming paradigm? No. It’s fucking stupid. But it’s the industry standard.
It's funny that this thread is titled "Standarditis". The exact problem here isn't the value of OOP, it's that programmers are disengaging their brains and "doing what everyone else is doing", aka following a so-called standard.
Let's assume everyone else that lives on your block works in construction and they buy big trucks. You are a programmer. If you buy a truck, you aren't "following the standard", you are engaging in cargo-cult behavior.
This applies to the original analysis. The people making disasters are the one simply doing what other people do rather than learning a set of tools and applying them appropriately to their work.
OOP training isn't helping here. It's really easy to explain inheritance by using real-world analogies like animals, but inheritance doesn't come in all that handy in the real world, and it is actually pretty hard to do correctly in non-trivial cases. Interfaces, on the other hand, are harder to explain and have few easily graspable real-world analogies, so OOP students sometimes come out of training with a lesser grasp of interfaces than of inheritance. Yet, interfaces are the real workhorse of OOP. Writing base classes intended for inheritance is usually best left to framework developers and architects.