he/him 
Spent the last 2 hours researching and picking a CSS-in-JS and routing library for React. It really shouldn't be this hard.
Show this thread
-
-
https://reacttraining.com/blog/reach-react-router-future/ … Sorry, I’ll stop trying new things and making them available to people for free.
-
How did my tweet imply that you shouldn't make new things or that I'm ungrateful? Thanks for the blog post link. Including it in the docs or GitHub could help others from making the same mistake.
- 8 more replies
New conversation -
-
-
https://reacttraining.com/blog/reach-react-router-future/ … And I completely agree, it's too hard to choose and not clear what anvil will fall on you in the future for the wrong choice(s).
-
I think the word is Reach is dead
- 5 more replies
New conversation -
-
-
Whenever i'm faced with this decision i usually end up using React Router, mostly because its older and it'll be easier to get support if i'm facing a blocker
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Depends. Go with router first
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Reach because of accessibility.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
React router, but you should really just use Vue
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Reach router is going to be merged with React Router. But I absolutely concur.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.