Hm I did not follow that closely though I recall some discussion. Trying to see if there was anything we missed or can do now.
-
-
Replying to @mixonic
based on the notes I read I think it was discussed at core meetings
1 reply 0 retweets 0 likes -
Replying to @ClimbingNarc @mixonic
It was indeed! The nut of the issue is that it was very unreliable before, and impossible to implement in any 1/
1 reply 0 retweets 0 likes -
way without significant performance costs in production (bad compromise because already very unreliable!) 2/2
1 reply 0 retweets 0 likes -
The current status is described in the linked issue.pic.twitter.com/YbvNaAixS9
1 reply 0 retweets 0 likes -
we're still very open to making changes if real-world scenarios depending on a reliable subset are reported
2 replies 0 retweets 0 likes -
Replying to @wycats @ClimbingNarc
fwiw,
@mixonic, I definitely think this should have been mentioned in the blog post (no intent to sweep under the rug).2 replies 0 retweets 0 likes -
Replying to @wycats
The post was pending in PR for a few days, sorry you missed it. Please feel free to update, file is here: https://github.com/emberjs/website/blob/master/source/blog/2016-11-30-ember-2-10-released.md …
1 reply 0 retweets 1 like -
Replying to @wycats
it wasn’t missed, this was a specific decision that was discussed during multiple core team calls
1 reply 0 retweets 0 likes
it was easy to miss the fact that it wasn't included in the blog post.
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.