I'm still learning. @ryanflorence is still learning. We're giving you the best work we've got, every time we ship something.
-
-
Replying to @mjackson
But this kind of attitude is absolutely destructive and inexcusable. It has absolutely no place in productive discussion.
3 replies 0 retweets 11 likes -
Replying to @mjackson
the tone definitely was on the snarky side, but a pro-stability position that argues for less breaking changes seems productive?
1 reply 0 retweets 5 likes -
Replying to @wycats
i don't have a problem with arguing for stability. breaking changes suck, i totally get it. but we have a decent migration strategy.
1 reply 0 retweets 2 likes -
Replying to @mjackson
I think people are looking for more of an incremental migration through deprecations (not breakage) story; any migration is :+1:
1 reply 0 retweets 0 likes -
Replying to @wycats
i understand that. let me ask you: how would you do "i was doing this wrong before, here's a much better way to do it"?
1 reply 0 retweets 1 like -
semver allows for breakage in major version bumps, so seems like a new major version is the way to go.
1 reply 0 retweets 1 like -
to be clear: what we've shown so far is only a preview of where we're going w the router. v4 isn't stable yet.
1 reply 0 retweets 0 likes -
we still have time to figure out best ways to provide backwards compat. no reason to worry yet. but people are freaking out.
4 replies 0 retweets 1 like -
we've already said we're going to have deprecations and let both versions run in tandem. our migration story is the same as ember's
2 replies 0 retweets 3 likes
you mean Ember 2.0 or Ember 2.9?
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.