@zackangelo no I am not. I suspect they will want to support new es6/es7 syntax and support it out of the box.
-
-
Replying to @stefanpenner
@stefanpenner@zackangelo ES6 classes won't support extending Ember.Object's...yet. Also issue w/ CPs, observers etc https://github.com/rwjblue/ember-cli-esnext/issues/7 …1 reply 0 retweets 0 likes -
Replying to @_jayphelps
@_jayphelps@zackangelo correctly,@wycats is working on annotations for es71 reply 0 retweets 1 like -
Replying to @stefanpenner
@_jayphelps@zackangelo@wycats for our custom descriptor patterns1 reply 0 retweets 0 likes -
Replying to @stefanpenner
@stefanpenner@zackangelo@wycats +1 I've played with ember + traceur via custom $traceurRuntime.createClass runtime +@computed('key')1 reply 0 retweets 0 likes -
Replying to @_jayphelps
@_jayphelps@stefanpenner@zackangelo@Computed there's some stuff to work out re metaprogramming annotations vs metadata ones. High pri2 replies 0 retweets 2 likes -
Replying to @wycats
@wycats@_jayphelps@zackangelo@Computed ya, but actions + hooks look great :)2 replies 0 retweets 0 likes -
Replying to @stefanpenner
@stefanpenner@_jayphelps@zackangelo@Computed the exuberance about classes forgets that every framework uses obj literals beyond methods1 reply 0 retweets 1 like -
Replying to @wycats
@wycats@_jayphelps@zackangelo@computed sometime soon i want to add generator support to many of the framework invoked hooks2 replies 1 retweet 1 like -
Replying to @stefanpenner
@stefanpenner@wycats@_jayphelps@zackangelo@Computed If I
'ed this any harder, it would invert the twitterverse.2 replies 0 retweets 0 likes
@BenLesh @stefanpenner @_jayphelps @zackangelo @Computed I think step 1 is to make more "returns a promise" APIs.
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.