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.
-
-
Replying to @wycats
2: We didn't think we could deliver a good experience for Ember devs without class fields and decorators,
1 reply 1 retweet 10 likes -
Replying to @wycats
3: and have been working hard to land those features in JavaScript via TC39. Fields just made it to Stage 3. Decorators close behind.
2 replies 0 retweets 20 likes -
Replying to @wycats
4: Now that there's a clear path to a good developer experience, we're starting to plan the transition:https://github.com/emberjs/rfcs/pull/240 …
2 replies 1 retweet 14 likes -
Replying to @wycats
fwiw, React only removed React.createClass from core in React 16 alpha, React 16 proper isn't even released yet. so timeline seems similar
1 reply 0 retweets 0 likes -
Replying to @notbrent
The main difference is how the communities reacted (no pun intended). Ember's community got thrashed for being "behind the curve" ;)
2 replies 0 retweets 2 likes -
But as someone who was literally working on fleshing out the ES2015 class model in TC39, I didn't think they were ready.
1 reply 0 retweets 2 likes -
I want to point out it wasn’t React team who pushed createClass out but the community. Community adopted ES6 classes a year before FB.
2 replies 0 retweets 10 likes -
I think it's an artifact of React community still being driven by early adopters at tha stage. Our docs used createClass, ppl said outdated.
3 replies 0 retweets 4 likes
Right. I'm saying ppl said the same about Ember and we pushed back because of limitations.
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.