On: Next.js 14

[garganzol]

Where are people dissatisfied with Next migrating?

[BoorishBears → garganzol]

If you're down with the paradigm of Next.js App Router, Remix is just a strictly better version.

If you're not you stick with pages router and get ready to fork as soon as they drop it. (Just don't ask when that will be https://www.reddit.com/r/reactjs/comments/156m504/comment/jt...)

_

Edit since I got rate limited: DevRel at Vercel replied to this trying to spin Remix not supporting RSC as a differentiator.

It doesn't support RSC because you guys managed to ship a flawed standard under the React brand and they rejected it.

It's the value proposition of RSC without the broken standard (and better performance)

Your reply is like saying an EV isn't environmentally friendly because it doesn't support E85 gasoline and yours does.

[leerob → BoorishBears]

Remix is like the Next.js Pages Router + a helper similar to Server Actions. It does not support Server Components (what the App Router uses) and they're exploring using RSC in the future. So definitely different.

For example, `getServerSideProps` in Next.js is the same as a `loader` in Remix.

[pcthrowaway → garganzol]

Astro probably, if they want to keep using React components.

Otherwise they might also be looking at Nuxt, Sveltekit or Solidstart, but if they're switching top-level frameworks they may as well use Astro because they can mix and match React/Vue/Svelte/Solid

[Spixel_ → garganzol]

We migrated to Remix a few months ago, never going back.

[simantel → garganzol]

Remix is the only real alternative I've heard about that isn't itself Next-based.