Ben McCormick

Hmm, a bit more experimentation shows that this is only true when combined with the Nucleus Dark ui theme. https://github.com/ignism/nucleus-dark-ui So I probably should be opening this there, unless it...

> Aside from consistency, is there any reason to use the class keyword with Backbone over extend? I addressed this in the blog post. Practically? No. In theory it would...

The ES7 proposal is just that, a very early community driven proposal. Not at all clear it will actually ever be part of an official spec. Current implementations cause properties...

@milesj hmm? That will error out immediately with the final ES6 class spec > In a derived class, you must call super() before you can use this Even if it...

@milesj did you read the original blog post? Running super first means the properties aren't processed. See here for a full in depth explanation: http://benmccormick.org/2015/04/07/es6-classes-and-backbone-js/

Decorators were mentioned above in this thread (specifically [Yehuda Katz's proposal](https://github.com/wycats/javascript-decorators)), and it was unresolved whether that would solve this issue. I was just playing around with them as proposed,...

@andrewrota I'm literally writing a blog post following up on this stuff right now (was reading through this thread when you commented). That is a big "other than", but I...

Here's a preview of the followup post I'm putting up: http://benmccormick.org/2015/07/06/backbone-and-es6-classes-revisited/ **Updated with permanent link now** It'll move to a permanent url early this week sometime. But the basic summary...

@StevenLangbroek see above for discussion about static properties. The syntax as currently specced creates a local property on each instance rather than adding to the prototype. Those properties are added...

@just-boris as discussed in my blog comments, the behavior you're seeing there is an implementation detail of Babel's handling of the class properties and decorators specs. Its not defined behavior...