The point isn't that OOP is inherently bad and should never be used, but that writing OOP code well (as opposed to merely using objects) is nontrivial. Hence the "seeing how most adult programmers do OO poorly" comment. We've had lots of problems with universities starting off with OOP in the introductory course. I would not deem it suitable for kids unless they are already good at procedural programming.
Of course good stuff has been written in OOP. I personally like that Django uses OOP - it's a good fit. Doing it well is not easy, though. And many problems are easier solved without it.
> JS is a prototypal language, classes are just sugar on top of the prototypes.
Is OOP now a vague term, akin to "functional programming"?
I still maintain that not having data encapsulation (i.e. Python) means it's not OO. (Not that I particularly want it to, either).
Of course good stuff has been written in OOP. I personally like that Django uses OOP - it's a good fit. Doing it well is not easy, though. And many problems are easier solved without it.
> JS is a prototypal language, classes are just sugar on top of the prototypes.
Is OOP now a vague term, akin to "functional programming"?
I still maintain that not having data encapsulation (i.e. Python) means it's not OO. (Not that I particularly want it to, either).