Once we answer this question, we can move on to just talking about Remix, so stay tuned!Īdditionally, we shared this post with Vercel before publishing. Note that this app doesn't get to exercise everything we think is cool about Remix (like nested routes!). To really exercise Remix's design, we rewrote the example into idiomatic Remix, and even built a quick image optimization route into the app so it's 100% Remix. Rewrite - The two frameworks don't actually have a lot of API overlap and Remix can run on different infrastructure than Next.js.This is a great comparison of frameworks because everything but the framework is the same. This is deployed to Vercel just like the Next.js Demo. Minimal Port - We simply copy/pasted/tweaked the Next.js code to run on Remix instead of Next.js.

Ability to integrate with multiple providers that illustrates how the frameworks help you abstract.Initial page load is critical for ECommerce.It has a handful of real world features we liked, and seems to be the one they put the most effort into. We ported the Commerce Example from the Next.js examples page. It should also show off the features the Vercel team is most proud of. Since they wrote it, the decisions they made should reflect how they intend you to build your app. We figured the fairest way to compare the frameworks would be to take a Next.js example app that the Vercel team wrote themselves. We think Remix's abstractions lead to better application code.Next.js requires you to change your application architecture and sacrifice performance when your data scales.Next.js build times increase linearly with your data, Remix build times are nearly instant and decoupled from data.Next.js requires client side JavaScript for data mutations, Remix doesn't.Next.js encourages client side JavaScript for serving dynamic content, Remix doesn't.Remix automatically handles errors, interruptions, and race conditions, Next.js doesn't.Remix enables fast user experiences even on slow networks.Remix is faster than Next.js at serving dynamic content.Remix is as fast or faster than Next.js at serving static content.By the end, hopefully you'll consider Remix for your next project (no pun intended 😂). There is a lot of nuance in this conversation that's left un-captured in the shiny graphs and animations. We encourage you to read this entire article. They are doing great work and we respect the work they do!īut make no mistake, we think Remix has a better set of tradeoffs than Next.js. We've been friends with folks at Vercel long before Vercel was founded. If you're a fan of Remix and want to start tweeting smug reactions to this article, we kindly ask that you drop the smugness before hitting the tweet button 🤗. It appears we have to answer this question! We'd like to address it directly and without drama. Easily the biggest question we get asked is something like:

Rising tide interactive indeec