3 ms·

This is how I see it. You need to be a nextjs expert to produce a nextjs website. Astro you just need to understand basic concepts and can produce a website. I

This is how I see it. You need to be a nextjs expert to produce a nextjs website. Astro you just need to understand basic concepts and can produce a website. I tried nextjs, and the complexity for a SPA was off the charts. Switched to Astro and never looked back.

ericmcer 2y ago
NextJS isn't ideal if you just want a SPA, just stick any frontend router in if you want that. If you aren't using it for SSR/SSG then you probably don't need it. If you are writing a really dynamic app with a few thousand users you probably don't need it. It is crazy good for blending dynamic/static pages together, preloading data for page responsiveness and making dependency management less of a nightmare. Things like e-commerce are where it really shines because it can blend thousands of cached SSG product pages with dynamic elements and data in a relatively straightforward way. I would not recommend it for any project where you are going to have fairly few static pages and relatively few users, it isn't worth the complexity.
ervine 2y ago
You can't even become a next.js expert because it is constantly changing. Even the devs involved don't have their heads around what they've built, considering responses in github issues.
- bastardoperator 2y ago
  I completely agree with this sentiment. I will say this, vercel was easy to use and v0 is pretty cool too. I can appreciate what they're doing, I just don't have time to become a nextjs expert.
- jokethrowaway 2y ago
  Both vercel and next keep breaking APIs. I just blank out stopped touching anything coming from there. I still have a client on next + vercel/ai and it's a constant shitshow of broken updates. It's not an environment you can be productive with. I moved to solid from now on: they don't have as much money but applications built years ago still work today

ericmcer 2y ago

NextJS isn't ideal if you just want a SPA, just stick any frontend router in if you want that. If you aren't using it for SSR/SSG then you probably don't need it. If you are writing a really dynamic app with a few thousand users you probably don't need it. It is crazy good for blending dynamic/static pages together, preloading data for page responsiveness and making dependency management less of a nightmare. Things like e-commerce are where it really shines because it can blend thousands of cached SSG product pages with dynamic elements and data in a relatively straightforward way. I would not recommend it for any project where you are going to have fairly few static pages and relatively few users, it isn't worth the complexity.

ervine 2y ago

You can't even become a next.js expert because it is constantly changing. Even the devs involved don't have their heads around what they've built, considering responses in github issues.

bastardoperator 2y ago
I completely agree with this sentiment. I will say this, vercel was easy to use and v0 is pretty cool too. I can appreciate what they're doing, I just don't have time to become a nextjs expert.
jokethrowaway 2y ago
Both vercel and next keep breaking APIs. I just blank out stopped touching anything coming from there. I still have a client on next + vercel/ai and it's a constant shitshow of broken updates. It's not an environment you can be productive with. I moved to solid from now on: they don't have as much money but applications built years ago still work today