Why I won't use Next.js anymore 😡

I understand the concerns raised in the article but i am not agree with some point

=> While it’s true that Next.js has introduced new features like Server Actions, these are aimed at enhancing the capabilities of the framework. The learning curve might be steeper, but it’s a trade-off for more powerful features. The documentation is comprehensive and is continually updated to help developers navigate these complexities.

=> Transitioning from page router to app router was a significant change. However, it’s important to note that changes in major versions of any software can lead to breaking changes. It’s part of the software evolution process. Learning about Server Actions is indeed required, but it’s a one-time effort that can unlock more powerful functionalities.

=> Next.js does have some limitations, like the 1Mb request body limit. However, these limits are often set for good reasons, such as preventing Denial of Service (DoS) attacks. For use-cases that require larger payloads, alternatives like using a separate API server or storing the data in a cloud storage and sending the URL in the request could be considered.

=>Comparing Next.js with a simple Express server might not be fair. They serve different purposes. Next.js provides a full-fledged framework for building server-rendered React applications, while Express is a minimalistic web application framework for Node.js

at last i want to said that remember, every technology has its pros and cons. The key is to choose the right tool for the job based on the specific requirements of the project. ☃️

This is exactly what I went through few days ago. I was trying to setup simple prisma+mongodb logger in NextJS but could not even start mongo connection in server action. Similar setup in Page Router was so easy.

i feel it's still a choice, with 'use client' directive one can easily skip server-side rendering plus server actions are not mandatory as such

Good points Royal Jain! That's why I switched to Remix: what a first-class DX ⭐️

Once you get some of that sweet sweet routing, prefetch, hot module reload, and hot data reload DX you won't go back 👌

Speaking of first-class DX, I’m building an amazing UI library for React and I'm looking for React devs, disatisfied with the current state of UI tools, excited for this type of product, and who enjoy giving feedback on mockups and product ideas (here's the landing page: verveui.pro). Twitter link on profile :)

Interesting article. Have you tried Django? One thing I like about Django is it has a clean architecture. You basically can build "modules" called apps and share them across projects.

Using Python is also a breeze, with no weird types (even though Python is strongly typed).

The thing about Django is it's been around since 2005 or thereabout, but has maintained its core feature set and does not break backward compatibility (If you don't count the python 2 vs 3 saga, but still even that wasn't too bad.).

Sure there are lots of new features, deprecations, and so on but there hasn't been a monumental shift every year/few months like with NextJs.

Skills I learned 5-10 years ago are still very useful in Django 5 today because the framework largely works the same.

This doesn't mean that they don't innovate, they have also had to keep up with the FE world, SPA's, and so on but yet again somehow have managed these transitions very smoothly.

Django comes with most of what you need for most projects, so you are not as dependent on third-party libraries or services.

Django is Python-based, so naturally all the libraries you get with Python are available including machine-learning libraries like Pandas, Pytorch, and so forth.

Finally for the frontend, you can still use React but also there is HTMX and "Django Unicorn" that can get you quite a bit of mileage without the complexity of the whole TypeScript ecosystem.

I must say that next.js is complex, although I have just started using it.🙃

I faced a similar issue in App dir, I tried to setup a simple CMS setup with React Query and SSR but it didn't worked, wasted two days figuring out issues then eventually shifted to pages dir.

I've decided to move away from Next.js due to its steep learning curve and complex setup. While it offers server-side rendering and routing benefits, alternatives like Create React App provide simpler solutions without sacrificing performance. Additionally, maintaining compatibility with Next.js updates can be cumbersome. Simplifying my development stack allows for faster iterations and smoother workflows.

I agree on the struggle of working with Next.Js to accomplish simple things, which if we go back to the basics of just serving things from the server will do the same thing.

Some applications might need this complexity tho to accomplish FE heavy computations, etc.

But for most of the websites that I See today, they also tend to go in the FE frameworks when it might not be needed so they end up complicating their life