Several companies are reevaluating their use of Next.js due to recent troubles, including vulnerabilities and performance issues.
Next.js, known for offering SEO benefits and a streamlined developer experience, is facing criticism for inefficiencies and slow rendering.
Companies like Northflank saw significant improvements in performance when switching from Next.js to a custom-built React SSR solution.
SEO advantages of Next.js have been overshadowed by slow render times, leading to a decline in SEO performance for some companies.
Issues with Next.js governance and constant framework changes have left developers feeling frustrated and constantly refactoring applications.
Developers have expressed concerns about Next.js's relationship with Vercel, suggesting a vendor lock-in strategy and limitations for self-hosting users.
Technical issues like slow hot module reloading and prioritizing server-side rendering over client-side efficiency have contributed to developers seeking alternatives to Next.js.
Despite criticisms, Next.js still has supporters who value its conventions, API routes, and TypeScript support for full-stack development.
For teams deeply invested in the React ecosystem, Next.js may still be a viable choice; however, for those prioritizing performance and stability, alternatives are being considered.
The industry sentiment towards Next.js seems to be shifting towards skepticism and criticism for its evolving structure and performance-related issues.