3 ms·
I always believed composition and interfaces was saner than inheritance, but this was sneered at during the 90s and 2000s. Still, OO isn’t all bad. It’s perfe
by nobodyandproud 6y ago
I always believed composition and interfaces was saner than inheritance, but this was sneered at during the 90s and 2000s.
Still, OO isn’t all bad.
It’s perfectly suitable within a self-contained project or library. i.e., a hidden implementation detail.
But there are API land mines if you expose non-final classes for public use.
API design is fundamentally hard, and every language reverts to
some sort of versioning.
- hellofunk 6y agoYou are exactly correct, the author has a misguided perspective. Inheritance is rarely considered these days to be the hallmark feature about OO. Composition and encapsulation far exceed inheritance in importance in nearly any software development circle.