Eric ElliottFeb 31 min read
Doesn’t this demonstration show that concatenation *does* have the same problems?
Byrd
11
It shows that you can model class-style inheritance IS-A relationships using concatenation. You can do the same with delegate prototypes, too, which is what happens when you use `class…extends`.
But the example is not a good example of composition done right. You can drive off a cliff in any model car.
Related tags
Rogério ZambonMar 217 min read
Kai KuchenbeckerSep 7, 20152 min read
Improving your Web App with Functional Object-Oriented Design
Brad Urani
778
Hey Brad,
You advocate some great concepts and I’m always happy to see more people thinking about how to fix the problems our decade long misuse of the MVC pattern in frameworks such as Rails has caused.
However, while I couldn’t agree more with some of the approaches you mention and while I do agree…
Jeff MOct 22, 20151 min read
As a fan of ES6 classes, it should not be hard to tell that I’m also a fan of the `new` keyword. :P
Thai Pangsakulyanont
2
Though, Eric is still making the same mistake of laying all blame on new and class.
Eric Elliott:
But you still have `new`, and somewhere, somebody is going to extend your MurderRobotDog via ordinary class inheritance, and your pretty design is…
class MurderRobotDog extends Murdering(Driving(Barking(Object))) { }
Classical composition
Thai Pangsakulyanont
94
Clever. Object composition via class factory composition.
But you still have `new`, and somewhere, somebody is going to extend your MurderRobotDog via ordinary class inheritance, and your pretty design is going to turn into a pile of twisted classes.
=)
