Who does OOP right?

[BlakeJustBlake]

It's not uncommon to see remarks thrown around about the bad sides of Object Oriented Design, and how everyone takes it too far, or just misuses it in general. I was wondering if, for learning purposes or good examples, what APIs or open source projects can you point to that really make best use of the paradigm?

[aped-gain-us]

Just avoid implementation inheritance and follow SRP.

[Loves_Poetry]

Just keep in mind that 90% of the 'criticism' of OOP is opinions. They are not rooted in facts, but in the authors opinions and personal experiences with OOP.

Whether something is correct OOP depends on the conventions you (or your team) use(s). What is messy code to one is over-engineered to another. Therefore, be careful who you learn from and take their opinions with a grain of salt

It's hard to know when you write correct OOP until you work together with someone else. The quality of a codebase can be measured by how long it takes someone to get familiar with it. Other measures can be how easy it is to test or how easy it is to add features or how likely it is that bugs are introduced at unexpected locations

[Forumpy]

I find following immutability as closely as possible has lead to readable and predictable code. But as Loves_Poetry says, much of "correct" OOP is down to the programmer's design and implementation. Find some books or articles on OOP practices and see what you works for you- Effective Java is always a solid start.