There is a lot of good wisdom from the 60s, 70s, 80s that people forget and end up re-inventing. I don't think I'm the first person to make this comment.
> OO
It's very subjective I'll admit. But I don't like OO, and it took me along time to realize why. There are many people who feel the same way. The difficulty is in explaining it. Because you have to look at large systems, explore the evolution of these systems, and pluck enough examples where things don't work.
You don't consider the fact that I've worked successfully with OO many times on various systems of various sizes to be of any significance, then tell me "there are a ton of resources online" which translates to "now go and google for viewpoints that support grumblingdev" instead of actually giving me any data.
You've given me nothing to work on, nothing to learn from, nothing I can even oppose because your objection is so nebulous. I can't even knock down your claims because you haven't really made any except "muh, OOP baaad". I haven't learnt anything, equally you haven't learnt anything... what was the bloody point in you saying anything at all?
> I think knowing that this viewpoint exists is a good lesson in itself
I'll skip the sarcastic reply and just say I draw rather different conclusions.
There is a lot of good wisdom from the 60s, 70s, 80s that people forget and end up re-inventing. I don't think I'm the first person to make this comment.
> OO
It's very subjective I'll admit. But I don't like OO, and it took me along time to realize why. There are many people who feel the same way. The difficulty is in explaining it. Because you have to look at large systems, explore the evolution of these systems, and pluck enough examples where things don't work.