8: Ember wouldn't be able to use ES2015 classes as-is. I gave my agreement for them and immediately got to work on the next steps.
-
-
Ahhhhh - seems like a bug in the earlier proposal. Glad it was fixed.
-
Honestly seems pretty esoteric—unlikely to matter usually. Given react's JS-first, class fields were pretty necessary over manual binding
-
class MyInput extends HTMLInputElement { type = "text"; } doesn't do what you think it does.
-
So class fields are purely to create new properties, not sure ctor initialization.
-
Anyway, it's fine. You've been able to use Babel's field transform in Ember if you want for ages. Ember itself has a higher stability bar.
-
Guess I just don't grok what "Ember itself" means - you talking about core contributors not being able to use these js features?
-
There's questions like: how do computed properties work with classes. Similar in react: how does PureComponentMixin work
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.