Mulling over ways to get rid of get/set in IE9+ in Ember...
-
-
Replying to @aaronshaf
@aaronshaf@wycats +1 for evergreen-browser-targeted fork of Ember1 reply 0 retweets 0 likes -
Replying to @producersteve
@producersteve I don't feel confident about requiring IE11 as soon as it comes out, so maybe not precisely that?@aaronshaf2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@producersteve Then how about: two most recent versions of each evergreen browser1 reply 0 retweets 0 likes -
Replying to @aaronshaf
@aaronshaf@producersteve let's see how quickly IE9 drops once IE11 is released2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@producersteve I predict that Safari will be a bigger ES6 holdup than IE.2 replies 0 retweets 0 likes -
Replying to @aaronshaf
@aaronshaf@wycats@producersteve That will depend on the target audience. Regulated enterprises may take years to get off of IE8 (yes 8).1 reply 0 retweets 0 likes
@mitchvoliver we can support oldIE with get/set for a long time @aaronshaf @producersteve
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.