For full text search please use the '?' prefix. e.g. ? Onboarding

Remix

Pros

  • built on the Web Fetch API instead of Node.js. This enables Remix to run in any Node.js server like Vercel, Netlify, Architect, etc. as well as non-Node.js environments like Cloudflare Workers and Deno Deploy.
  • Remix’s “loaders” are particularly powerful, allowing the server to gather all necessary data for a route before it’s rendered. This differs from Next.js, where an application might load the JavaScript first, then realize it needs to fetch additional data via APIs, potentially slowing down initial load times. By using Remix’s loaders, OpenAI ensures that the initial page load is faster and smoother, as all required data is pre-fetched and delivered in a single step.

Issues

What About Server-Side Rendering and SEO?

Given the popularity of server-side rendering for SEO and performance reasons, some might wonder why OpenAI chose to move away from Next.js’s SSR features. The answer is simple: ChatGPT doesn’t require the typical SEO benefits that come with SSR. Since the application is primarily a tool rather than a content-driven website, SEO is less of a concern. Instead, OpenAI focuses on fast, smooth client-side interactions, which Remix handles efficiently.

Resources

References

https://medium.com/@lbq999/why-openai-moved-from-next-js-to-remix-a-closer-look-114732b28eb9