From the perspective of web standards to concerns about increasing complexity, Kent C. Dodds shares his opinions on why he won't use Next.js.

Kevin

FaunaDB

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

The author explains why they won't use Next.js and instead recommend and teach Remix as a better tool for creating excellent user experiences. They discuss the importance of focusing on standard web platform APIs, concerns about Next.js's deployment options, the perceived lack of collaboration between React and Next.js teams, and their preference for stability and simplicity in a framework.

Why I Won't Use Next.js

Tldr; he won’t use next.js because he’s been invested in remix for a few years and he likes it a lot. However, his website, the one that makes him money, is built with next.js.

And Kent may never use NextJS at all because Remix is his product. Right now, for Remix, to get more users for their solution is to market their product in front of the most popular competitor, and Nextjs, being the most popular, is the one to be compared. Try to compare with other less popular solutions, but they will not, as they need our attention (NextJs User Base) 🙏

Kent C. Dodds Don’t Mention Remix Challenge: Impossible
I can’t help but feel like the post is trying to steer the community and his followers. His new venture is selling Remix courses. It’s hard to not see this as using his influence to stir up controversy and shift the mindset over to “don’t learn that, learn Remix.” Read the last few paragraphs of this, it reads like a sales pitch. I feel like a true teacher would keep an open mind and try to be unbiased, so they can give their students the best knowledge at that time. Not so they can be set on one thing and reject the rest. It is not a balanced take, it reeks of evangelism.
Next.js/Vercel has flaws, I’m not defending it, but he only vaguely mentions some things and drops a few nitpicky examples of others. I don’t think the post reveals anything new. It makes me think he saw the Next.js community unhappy after Next.js 13 and wanted to get in on it.

The response from Lee Robinson (Verceil) is interesting too: <a href="https://leerob.io/blog/using-nextjs" target="_blank" rel="noopener nofollow">https://leerob.io/blog/using-nextjs</a>.