3 ms·
There's people here claiming that the problem is OOP done wrong. Let's talk about stuff that pretty much every OO language shares: * syntax that favours inheri
by moomin 10y ago
There's people here claiming that the problem is OOP done wrong. Let's talk about stuff that pretty much every OO language shares:
* syntax that favours inheritance over composition
* inability to specify polymorphism over two input types
* inability to specify polymorphism over return type
(Both of these are symptoms of close identification of type and table)
* Syntax that makes generics unwieldy to the point that many think they're just for collections
* Inability to make third-party types expose your own interfaces (Clojure manages this. Some languages manage this through monkey-patching, but that's a cure worse than the disease.)
OO is broken. The biggest problem is that we're all so invested in it we have trouble seeing there's another way.