Maybe OO isn't the problem.
Maybe OO isn't the problem.
I've found that OO is incredibly confusing to some people because there are many ways to do one thing. That can be a feature to some and a bug to others.
I've also found that OO requires a level of discipline (e.g. SOLID) that's almost impossible to enforce. I've known companies who essentially have someone on the team whose full-time job is monitoring the code quality of the OO code base. I haven't observed the same thing in functional code bases (though my sample size is smaller).
I've encountered such programmers. They're generally just mediocre programmers who don't put a lot of effort into upping their game. They typically don't find functional programming any easier.
>I've also found that OO requires a level of discipline (e.g. SOLID) that's almost impossible to enforce.
Enforcing SOLID categorically is a bad idea, period. And I think one of the worst things about OO is the copious dogma that has grown up around it. In that sense, you could say it's a victim of its own success.
I would much rather look at a single function to figure out what it does rather than having to go look for how changes in it affects the hierarchy of classes.
>I would much rather look at a single function to figure out what it does rather than having to go look for how changes in it affects the hierarchy of classes.
I don't deny that there are many people like you in the programming world who struggle to understand things that many others have no trouble at all grokking. But my observation is that there are far more people like me, who don't struggle with understanding OO code.
For decades, OO has been the dominant programming paradigm. And for decades, functional programming has been, as declared by many, on the cusp of taking over the world. And yet it never seems to happen.
Whatever. I don't really care. The fact is, they, by their own admission, have difficulty with it, and I don't.