Remix 3 made the kind of announcement that stops a scroll: the team — the same people behind React Router — is stepping away from React and betting harder than ever on the web platform itself. It is a deliberate provocation, and it says something about where frontend is heading.
Betting on the platform, not the framework
The argument is that browsers have quietly absorbed much of what we used to need frameworks for — fetch, streams, form handling, navigation, view transitions. Lean on those primitives and you ship less JavaScript, fewer abstractions, and code that ages with the platform instead of against it.
Why this matters beyond Remix
Whether or not Remix 3 is the framework you reach for, the underlying move is the real story: the industry is rediscovering the web platform. Signals, server components and 'do more with the browser' are all pulling in the same direction — less framework ceremony, more standards.
Our take
We're pragmatic about frameworks — the right tool depends on the product. But we like this direction. Apps built close to the platform tend to be faster, smaller and cheaper to keep alive years later. It's the same reason we build mobile fully native: fewer layers between your idea and the device.
