In this article, we will try to understand why OOP is the worst thing that happened to programming, how it became so popular, why experienced Java (C#, C++, etc.) programmers can’t really be considered great engineers, and why code in Java cannot be considered good.
My conclusion is that the author doesn’t know how to use OOP properly and thus is calling the entire thing garbage. You only have to look at the method vs function argument to see that.
I program in both styles every day. They both have advantages and disadvantages. Though, admittedly, it’s difficult to differentiate between IDE benefits, language benefits, and language style (FP vs OOP) benefits.
I’ll tell you what I hate about the FP language I use. How do you determine if two objects are related to one another in some way? Hope and pray to God someone documented it because the language sure won’t give you any hints. If you set up your objects in OOP right, it’s all laid out in the models.
My conclusion is that the author doesn’t know how to use OOP properly and thus is calling the entire thing garbage. You only have to look at the method vs function argument to see that.
I program in both styles every day. They both have advantages and disadvantages. Though, admittedly, it’s difficult to differentiate between IDE benefits, language benefits, and language style (FP vs OOP) benefits.
I’ll tell you what I hate about the FP language I use. How do you determine if two objects are related to one another in some way? Hope and pray to God someone documented it because the language sure won’t give you any hints. If you set up your objects in OOP right, it’s all laid out in the models.