[kylehotchkiss]

To me, Remix seemed like a very lightweight reimagining of what Next excelled at (server side react with nice frontend integration). It was exciting to see how quickly it handled dynamic renders when running from a Cloudflare worker. But now that Next 13 has layouts/server components, I prefer Next.js' approach due to all the other performance work they've done with images, fonts, css, etc.

One thing about Remix that always confused me was the very close ties to react router. It seemed like a distinct and unrelated concept to me, and the continued association seemed like a distraction from Remix's potential to be a stronger competitor to NextJS in the long run

[yilugurlu]

Ryan, the co-founder of Remix said this [1]

> Remix is really just React Router + SSR.

[1] https://twitter.com/ryanflorence/status/1586835847583653889

[valtism]

If you want to have server-side data fetching across nested components, tying the frontend to the router is the simplest way to make that happen.

[qudat]

> One thing about Remix that always confused me was the very close ties to react router. It seemed like a distinct and unrelated concept to me, and the continued association seemed like a distraction from Remix's potential to be a stronger competitor to NextJS in the long run

Nextjs also has its own routing lib so I'm not sure why you think it's so weird that react router was involved.