[hu3]

> They claim to still be maintaining React Router. But it’s the same team now split across two projects. That means both will slow down.

I agree with your sentiment.

But how complext is react routing if it needs an entire dedicated team?

[zIndex9999]

Routing in any language or system is famously regarded as the "easiest" thing to build as a toy, but the hardest thing to get right at scale. Everyone and their dog has built some kind of "router" for themselves, but very few can do it to the extent that it works for more than just them, their company, or a select few externally. Props to the React Router team for being able to do it on a global scale. But for them to effectively move on as if they're "done" and that there's no more polish or innovation to happen on React Router is asinine. A great example: Ryan/mj ignored for a long time (and still resent) TypeScript. Tanstack comes along and launches actual complete typescript support to it's router like 3 years ago, which then triggers Remix users to demand something from their overlords. They eventually give in and add some hacky code-generation and watered down href utility and confidently say they are finally type-safe.

They likely won't touch it again (just like Next hasn't touched their IDE type safe plugin in a year).

They're simply purist craftsmen. They'll keep chasing "perfection" over practicality at any cost other than financial security.