I was under the impression that Next.js was the successor to React? Is that not the case?
> I was under the impression that Next.js was the successor to React? Is that not the case?
You should probably read the article before posting.
You should know this before choosing Next.js
11–20 of 147 posts
Re: You should know this before choosing Next.js
#12I was using next.js when they switched from the pages router to app router. I ended up just abandoning the project, the app router experience was that bad, and haven't really been keen on picking up next.js since then.
It's always seemed clear that Vercel has been, at best, OSS-ish. Trying to play both sides of claiming to be open source but also (somewhat sneakily) building a walled garden to lock users into their hosting platform.
Re: You should know this before choosing Next.js
#13Stay away from anything that has to do with Vercel
Re: You should know this before choosing Next.js
#14The single reason I switched from next.js was because it was taking me 6-7 seconds on a small project to see changes I made appear in the browser during development (on an M1 Max Macbook pro with 64gb of ram). This is when using the app router, where every change requires a compilation step.
I now just use a React SPA with Vite.
Re: You should know this before choosing Next.js
#15I was under the impression that Next.js was the successor to React? Is that not the case?
[deleted]
Re: You should know this before choosing Next.js
#16I warn everyone away from next.js. Unsurprisingly V0 has a real shot at massively increasing its adoption because people don’t know any better. What are some salient counter points for choosing next.js? I see a lot of new devs not want to have to think about deployment and management of systems so that is one aspect. If you only know react I guess getting SSR without having to learn something else is a win at the cos…
There is such an exaggeration about the need/utility of SSR. Google is dead for new projects, if one is optimizing their stack based on the easiness for Google to crawl it, I think they are making a terrible architectural decision for no return. Deploying a React/JavaScript app is much easier without Next.JS.
Re: You should know this before choosing Next.js
#17Stay away from anything that has to do with Vercel
And influencers CEO, Vercel being the main one.
Re: You should know this before choosing Next.js
#18I was under the impression that Next.js was the successor to React? Is that not the case?
Kind of. Vercel found a way to destroy React to its own benefit and profit.
Re: You should know this before choosing Next.js
#19Next is a fantastic choice if you really have the problems that it solves well (SSR and backend proxying). If you don't, it's a huge bloated mess, and you should just stick with a traditional SPA.
Re: You should know this before choosing Next.js
#20Funny how everything goes through a cycle of it's amazing, it's terrible, it's boring