Common Objections
OOP was originally designed as
I don't see any point in discussing someone's long-forgotten fantasies; I base my argument on where we've ended up.
Functional and procedural programming are different things.
I often see FP being used when people actually mean PP, and I rarely encounter PP itself. The concept of a procedure is almost never used anymore, whereas the function is constantly used, likely due to keywords in popular languages like function or func. At the same time, I frequently encounter the term "functional style," so I decided to separate the concepts of paradigms and programming styles. I also try to avoid unnecessary concepts in this article, such as imperative and declarative styles.
Drawbacks
1.The first red flag that made me question the success of the OOP concept was a childhood trauma task from my first OOP interview for a language I had just started learning at the time — C#, which has stayed in my memory to this day:
Task: What will be printed to the console when the program is run? The first thought at the time was — how and why did the human mind come up with something like this — a program creates itself (what? o_0) from its own method, and then even darker magic begins — many other methods are called in a sequence that is almost impossible to predict without knowing this magic from the inside.