>We think React Router v7 is the best way to use React and we are very optimistic about its future.

Maybe, but I stopped using React Router many major versions ago. I have never, in my entire career, seen a library change (in large, completely non-backward-compatible ways) as many times as React Router. It's like the author just decides to do things completely differently in every new version for fun.

Maybe he finally guessed right on the 7th time, but I just can't imagine building my site around a tool that changes it's entire paradigm annually.

The product doesn’t sound bad but shipping a new framework under the old name is a bad idea. Remember when AngularJs became Angular?

I’m curious what’s meant by

Designing for bundlers/compilers/typegen (and any pre-runtime static analysis) leads to poor api design that eventually pollutes the entire system

Is this in reference to React Router v7 that just shipped?

I've been a webdev for 20 years, and I didn't understand what any of that post meant.

Does this mean Remix will become a framework (with no stated benefits) that wont benefit from React ecosystem?

Let's wait for the team to announce this, instead of going for draft posts please.

this isn't official and is missing context flagged it

Great move! React is really old tech holding the web.