[zIndex9999]

Remix v3 isn’t just a new direction, it’s a full reboot. They’ve scrapped React, forked Preact, teased their own UI library, and are positioning themselves as a zero-dependency, fully self-owned framework. It’s not evolution, it’s erasure.

Let’s not forget how Remix got here. It gained traction primarily by merging into the React Router repo, inheriting 11M dependents and a decade of credibility it didn’t earn. From there, it became a thin abstraction over React Router before going dark entirely with the now-famous “taking a nap” announcement.

Now it’s back. Not with stability, not with iteration, but with a declaration, “We’re doing our own thing.” No React. No compatibility. A fresh stack, built from scratch.

Why? That’s the real question.

Shopify reportedly acquired Remix for ~$40M. Maybe this is them pushing for something big and new to justify the investment. Or maybe it’s the founders wanting full-stack ownership and long-term lock-in. Or maybe, with the pressure off post-acquisition, this is just Rich People™ messing around with legacy projects instead of supporting their users.

The leaked version of this pivot was even more aggressive, it openly criticized React and dubbed the shift a “Declaration of Independence.” The blog post toned that down, but the core direction hasn’t changed. It’s still a move away from the ecosystem that gave them a user base, toward something inward-looking and self-defined.

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. One is legacy support mode, the other is vaporware until proven otherwise.

Meanwhile, others in the space are embracing the now. They’re solving the hard problems of 2025 head-on. They’re building with the current stack, improving developer experience, shipping usable features, and making the future better, not by erasing the past, but by working with it.

This isn’t thoughtful evolution, it’s a hard reset with unclear motives, launched by a team with less to lose than their users.

Trust is easy to lose in devtools. This is how you lose it.

[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.

[dbbk]

No AI slop please

[faefox]

Slop detected

[cAtte_]

probably not, there's a few comma splices in there