@AdamRackis Very hard to lay odds, but backed by Babel, Microsoft, and @wycats so looking good in principle.
-
-
Replying to @BrendanEich
@BrendanEich@AdamRackis They're also a key part of Angular 2.0 and Aurelia, and (once they get to stage 2) a crucial part of Ember 2.x.1 reply 0 retweets 5 likes -
Replying to @wycats
@wycats Curious why their being a part of Ember 2.0 depends on promotion to stage 2?@BrendanEich2 replies 0 retweets 0 likes -
Replying to @AdamRackis
@adamrackis@wycats@brendaneich people can already use them via community add-on. But before they won't be part of the official story ..1 reply 0 retweets 1 like -
Replying to @stefanpenner
@adamrackis@wycats@brendaneich until the are also part of JS's official story. In addition, tools like jshint not supporting early ...2 replies 0 retweets 0 likes -
Replying to @stefanpenner
@adamrackis@wycats@brendaneich (pre stage 2 features) hurts developers common work-flow.1 reply 0 retweets 0 likes -
Replying to @stefanpenner
@stefanpenner Sure, but he singled out Ember as needing promotion to S 2 to be a part of it. Ember just more cautious?@wycats@BrendanEich2 replies 0 retweets 0 likes -
Replying to @AdamRackis
@AdamRackis@stefanpenner@wycats can speak for himself, but he's on TC39 so avoiding conflict of interest; also note canary vs. stable.1 reply 0 retweets 1 like -
Replying to @BrendanEich
@BrendanEich@stefanpenner@wycats Cool - thanks all!1 reply 0 retweets 1 like -
Replying to @AdamRackis
@AdamRackis@BrendanEich@stefanpenner Exactly. We don't want to create ecosystem lockin to features that didn't make it.2 replies 0 retweets 1 like
@AdamRackis @BrendanEich @stefanpenner We start playing w/ features at Stage 1 (esp via addons), only ask apps to make bets w/ us at stage 2
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.