2: We didn't think we could deliver a good experience for Ember devs without class fields and decorators,
-
-
-
3: and have been working hard to land those features in JavaScript via TC39. Fields just made it to Stage 3. Decorators close behind.
-
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 …
-
5: But as an Ember developer myself, I have appreciated the stability of a working, featureful object model while ES2015 classes fleshed out
-
6: Not everyone remembers, but ES2015 intentionally shipped what we called "max-min" classes. We got consensus for what everyone knew
-
7: was a too-limited feature set as an incremental step that we could build on in future versions. It saddened me at the time, but I knew
-
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.
-
9/9: I'm enthusiastic about what we can build on top of a fleshed out class model, and happy (but exhausted) for having held out until now.
- 16 more replies
New conversation -
-
-
Probably more indicative of ember showing it'd age than a sound decision though right?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.