https://medium.com/dailyjs/we-jumped-the-gun-moving-react-components-to-es2015-class-syntax-2b2bb6f35cb3 … 1: As much as it hurt, I'm happy Ember hung back on ES2015 class syntax.
-
-
I don't understand. class fields and decorators have been supported by Babel for ages - why can't Ember devs use them just like React devs?
-
1: Nothing is stopping Ember devs. https://github.com/ember-decorators/ember-decorators …
@rwjblue is on the core team. The core project is just more conservative -
2/2: about adopting features in-flux. Babel decorators and fields are a much earlier draft in ways that mattered.
-
And again, I'm really just talking about how the communities reacted. Ember community took heat for hanging back but I think it was right.
-
How have class fields changed in their path to stage 3?
-
Some obvious ones: - they defineProperty instead of set (matters for setters on the proto) - x; produces undefined vs. a hole
-
both of these can easily affect what happens when you subclass an object in pretty common ways.
-
So if I do this.x=2 in base ctor, & extend, & in sub class do a x = 3 field, latter will defineProperty on proto & be shadowed by base x?
- 8 more replies
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.