In the front-end world, there's an ongoing war over performance.

Martín M.

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

This post discusses how Next.js breaks React fundamentals and provides examples of the DX (Developer Experience) issues in the current Next.js API. It argues for a better approach to framework API design that prioritizes DX while still providing good performance.

How Next.js breaks React Fundamentals (Examples)

<p>Interesting points, but keep in mind that Next.js is in some sense the “canary in the coal mine” wrt RSC. It’s the first to move forward adopting it, while other React-based framework either didn’t adopted it <em>yet</em>, claim it’s not necessary or they have a better idea (some do have).</p>
