Is React Router 4 another non-backwards compat version? Asking for a friend who is tired of rewriting stuff all the damn time. Ok, it's me.
-
-
Replying to @trek
Old version will stay supported. New API is way better for new apps. Price of progress :-(.
5 replies 0 retweets 13 likes -
Replying to @dan_abramov @trek
[insert ember engines argument] lots of progress for everyone right away
2 replies 0 retweets 2 likes -
Lotta value in providing trivial upgrade path w/ codemods or upgrade libs like jquery and others have done.
2 replies 0 retweets 5 likes -
so using progress as a reason for breaking APIs is not something to really stand behind
3 replies 0 retweets 8 likes -
Something it’s impossible not to break them when approach is diametrically different. But I agree re: smoother upgrade path
3 replies 0 retweets 3 likes -
in my own work, if an approach is fundamentally different, that’s a cue to create a new project with a new name
6 replies 0 retweets 11 likes -
If it's vastly better but project is super popular you'd make disservice to beginners who learn the old thing
1 reply 0 retweets 2 likes -
Replying to @dan_abramov @markdalgleish and
Which I think is a good enough reason to keep the name. This is the router for all future users.
4 replies 0 retweets 7 likes
agreed. Deprecations are the way :)
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.