4 ms·
I think that's the idea though. It's for domain modeling. What's wrong with OOP as an abstraction over your FP foundation?
by pull_my_finger 4y ago
I think that's the idea though. It's for domain modeling. What's wrong with OOP as an abstraction over your FP foundation?
- rcme 4y agoGenerally, OOP makes it very difficult to reason about what is happening. Sub-classes can override methods in subtly different ways, internal state can be updated, super classes require changes to implement certain things in sub-classes, etc. Composition over inheritance has been much more robust in my experience.
- pull_my_finger 4y agoSounds like most of your complaints are about things that even OOP advocates recommend against these days. Multiple inheritance is rare in practice, and even rare in language support. Some newer OO languages, like Pony for example, don't support sub-classing at all and instead uses interfaces to represent that sort of information.
- ilyt 4y ago..the idea your code contains apples and oranges? I'm talking about the tutorials that wish the examples out of some random everyday items instead of having example app that uses the inheritance in useful way on code that someone with actual problem might write.