As someone who has fifty or sixty thousand lines of code using the new class syntax, I find this hard to understand. When I run into cases that aren't suited for the new class syntax, the solution is easy: *I don't use it*. If one tool isn't fit for the job, pick up another! After all, no one is proposing we *remove* the old prototypal stuff.
The class syntax solves one set of problems. The more flexible prototypal stuff solves another, and from my own experience they work pretty well together. Joe On Wed, Mar 4, 2015 at 5:03 AM, Benjamin (Inglor) Gruenbaum < [email protected]> wrote: > Did you seriously just plug your blog post in es-discuss? > > Are you really explaining the open-closed principle and composition vs > inheritance to a mailing list of people interested in language design? > > About why class is added: > https://esdiscuss.org/topic/is-class-syntax-really-necessary > > ECMAScript would have looked different had it been designed from scratch > today - but given your criticism everything apart from mixins for classes > is impossible without breaking compatibility and mixins are being explored > separately anyway. > > From: Eric Elliott <[email protected]> > > > I've already posted this on my Medium blog here: > https://medium.com/@_ericelliott/how-to-fix-the-es6-class-keyword-2d42bb3f4caf > > > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
