Why I Don’t Use Next.js for my Web Development Projects
Next.js is a popular framework for building React applications with server-side rendering and other benefits. However, there are some reasons why I choose not to use Next.js for my web development projects.
Complexity
Next.js introduces a level of complexity that may not be necessary for all projects. It adds layers of abstraction and might make it harder for beginners to understand the underlying concepts of web development. I prefer to stick to the basics of HTML, CSS, and vanilla JavaScript for simpler projects.
Performance
While Next.js offers server-side rendering, it may not always result in better performance compared to client-side rendering. In some cases, the added server-side rendering can actually slow down the website due to increased server load and caching issues.
Flexibility
Next.js comes with predefined folder structures and conventions, which can be limiting for developers who want more flexibility in organizing their code. I prefer to have full control and flexibility in structuring my projects according to the specific needs and requirements.
Learning Curve
For beginner developers, Next.js may have a steep learning curve, especially if they are not yet familiar with React or server-side rendering concepts. I believe in using tools and technologies that are easy to learn, maintain, and scale as the project grows.
Conclusion
While Next.js is a powerful framework with many benefits, it may not always be the best choice for every web development project. I believe in keeping things simple, flexible, and performance-optimized, which is why I choose not to use Next.js for my projects.
Trick question: Use Svelte
Yes. NextJS is the worst. Stick to PHP.
its magic.
he should make links) )))
I will sub you with all of my google/youtube accounts
When nextjs introduced serverless functions it got bad. When it removed data mutation it became worthless. But the web stamdards suck too so I don't know if Remix is a good alternative.
I like nextjs but im not happy about its current state. I love its potential. The "use client" drives me crazy and i have the feeling it shoudlnt be so complicated.
Im considering switching to Remix, after NextJs transferred to a PHP
Feels good using blazor lmao nothing of this bullshit
Nah svelte is better
The main issue I have with Vercel is that most of my customers use Azure or AWS by default. It'll be quite a process to suggest anything else.
I mentioned this to the Vercel people at Web Directions Summit in Sydney last month. I'd really love to use them, but without them being available via AWS/Azure marketplace or something like that, I have to pretend they don't exist for most projects, which makes me wonder about nextJS also.
No, Vercel is not literally burning money. You mean figuratively.
1:52 he got you covered, there is a huge link on the header
Guys, turn on the news, Vercel declared war on Remix.
Next on top of react on top of node, on top of vanilla JavaScript?!?! AGGHHHHHHHHH!!!!!
Next.js's monkey patching of fetch() breaks using the mock API framework Mock Service Worker. Stop the monkey patching,!
anyone coming here for TJ comment on cookies: 38:42
37:40 Thats It bois.. Kent wins. Theres too much magic and It is really really annoying.
Regarding self-hosting of Next, my biggest struggles definitely come from handling of environment variables especially when working with containers. The conditions in which Next variables are compile time vs non compile time in conjunction with trying to have a single image running across Test, Staging and Prod definitely left a sour taste for me.
The further blurring of the lines between server and client code adds to this where I really do struggle recommending the framework to people without adding caveats
He got a reply to that article from Nextjs