Despite Eric Elliott’s claims, classes and stamps do the same thing.
Jeff M

The discussion isn’t about the problems of JavaScript’s poor abilities to work with inheritance like in class based OOP. In fact, the best practice is to avoid it, where possible. Stampit supports composition of objects. Classes support inheritance between them. It’s certainly a different perspective, despite the issues they may share.

Let me ask this. Isn’t it a known best practice in classical OOP to avoid deep class hierarchies? Isn’t the pillar of code reuse in inheritance replaced by the idiom, “use composition over inheritance”?

It sure is and that is what Stampit is offering. Everyone from the classical OOP world is fighting to get inheritance to be the non-plus-ultra in JavaScript, when in fact, it shouldn’t be. I think that is underlying message of Kent’s article.