Hacker News new | ask | show | jobs
by jmtucu 973 days ago
Biased since he was hired by Remix.
2 comments

Exactly... and Remix is the old team from React Router, who break their API every version. I understand the author's arguments against Next.js, but having just set up a hello-world in Remix and being immediately confronted with a hydration error, I don't think Remix is the path forward either.
What's funny is he calls this out in the post:

> This is also why there has effectively only been a single breaking change in 8 years of React Router.

https://twitter.com/ryanflorence/status/1715023981340967214

I do agree with it; I've had to do some huge react-router upgrades and the only one that was truly painful was v3 to v4

2 breaking changes from the 6 versions released. Also, releasing a "backwards compat layer" a year after releasing a version of a library doesn't mean the original release was not a breaking change.
Yeah but it's a very fair take.

I don't have a horse in the race. I don't use Next, Remix, or even React.