Why ChatGPT Shifted From Next.js To Remix: Some Theories

The frontend development community was all abuzz this week about OpenAI shifting off Next.js to Remix. We summarize the best analysis.

Sep 14th, 2024 8:05am by Loraine Lawson

Featued image for: Why ChatGPT Shifted From Next.js To Remix: Some Theories

Image by Diana Gonçalves Osterfeld.

The frontend development community was all abuzz about OpenAI shifting off Next.js to Remix. We’re not sure who broke the news but numerous sources confirmed it with the source code.

There’s no shortage of opinions on YouTube, LinkedIn and Medium, not to mention other social media discussions, about the shift.

But those looking for insights might want to read Alex Anderson’s post, “Oops, I accidentally made our website faster by switching to Remix,” which coincidentally published Sept. 3.

Anderson is a senior software engineer with digital agency Echobind. The company didn’t so much decide to leave Next.js as it decided to shift hosting off Vercel to Railway for cost and convenience.

“This presented us with a small problem: Next.js,” Anderson wrote. “It pairs wonderfully with Vercel, but requires a bit more setup and infrastructure to run well when self-hosted.”

Anderson’s team decided to try Remix. He found the migration was not as hard as he’d anticipated, although there were a few Next.js conveniences that he had to work around with Remix. However, when it was all said and done, he found he’d improved the site’s performance substantially.

A screenshot of Echobind's site performance on Next.js versus Remix. It shows Remix improved site scores across the board;

Echobind’s site performance on Next.js versus Remix. Screenshot Echobind’s blog.