Merging Remix and React Router

Re:Merging Remix and React Router by fish55 on Wednesday May 15, 2024 @10:19PM (#40374618)

If you've already changed your build system to Vite (a breaking change to any app started before Vite), and opted in to all current "future flags" (breaking changes), and multiple forthcoming future flags before 7.0, then you will have no breaking changes. And let's not forget its history, including the previous merge with Remix. The only lib moving even faster is Next. Both are highly focused on PR at the expense of accuracy and good faith.

[ Parent | on HN ]

Re:Merging Remix and React Router by ryandvm on Wednesday May 15, 2024 @10:23PM (#40374631)

I've been writing code for 20+ years and I did not recognize a single product you mentioned. I am so glad I got off the front end treadmill. If you need me I'll be over here writing APIs using the same stack I was using 5 years ago.

[ Parent | on HN ]

Re:Merging Remix and React Router by halfmatthalfcat on Wednesday May 15, 2024 @10:31PM (#40374657)

So brave. Thank you for your contribution.

[ Parent | on HN ]

Re:Merging Remix and React Router by drawfloat on Thursday May 16, 2024 @12:47AM (#40375264)

You don’t need to know every Astro and Remix, but not even knowing what Vite and Next are as a FEer in 2024 is not exactly something to shout about.

If you don’t need to, fine, but also understand it just sounds ignorant given their size and many years of news around them.

[ Parent | on HN ]

Re:Merging Remix and React Router by throwaway11460 on Thursday May 16, 2024 @03:46AM (#40376104)

I still use the same tools I used when I started with React 10 years ago. You don't need to get on the treadmill, you chose that.

[ Parent | on HN ]