I built a project using Next.js and had a frustrating experience. Although I get its value, it feels like mastering it requires a significant time investment to really understand the 'Next.js way'. Just recently, I created another app as a straightforward SPA with some pre-rendered pages for SEO, and it felt much quicker and smoother. My sensitive data isn't exposed on the client side since I set up a simple proxy with my hosting provider. To me, Next.js seems like an overkill solution. Am I overlooking something important?
5 Answers
Honestly, many of us are finding Next.js more trouble than it's worth nowadays. If your SPA runs better and gives you a simpler development experience, go with that! Next.js can be overcomplicated for plenty of applications. You're not missing out on anything crucial by skipping it.
Right? All these 'magical' features come with their own headaches like hydration issues, which can drive costs up for mid-sized companies. Keeping things simple is often the best route.
I switched from React to Svelte and have never been happier. Seriously, if you're looking for something new to try, Svelte is worth exploring!
I've not given Svelte much of a chance yet. What's your take on when it shines best?
I want to give Svelte a shot, but most job offers still require React experience unfortunately.
I’m transitioning away from Next.js for a more straightforward architecture using the Tanstack router. Next.js has just cost me too much time in development.
I'm really curious about the Tanstack router! What's drawing you away from Next.js for it?
If you look at Next.js, it seems like a heavy fit for many projects when other simple solutions can work.
Astro has been gaining a lot of traction for content-heavy sites. It might be worth checking out if you need something that's less bulky while still being effective.
Interesting! What unique benefits does Astro offer for sites focused on content?
Next.js was great at one point, but I've come to believe it's more suited for monolithic applications, which, while convenient, adds layers of complexity. If all you need is basic functionality, sticking to simpler frameworks can save a lot of headaches.
I agree! Keeping the backend separate from the front end has made a world of difference for our projects.
It's true! If you don't need serverside rendering, I find React Router fits the bill just fine.
I get it! I prefer using Vue or Svelte over React due to their simplicity. React and Next.js just pack a lot of complexity that feels unnecessary sometimes.