You should know this before choosing Next.js
eduardoboucas.com
You should know this before choosing Next.js
1–10 of 147 posts
Re: You should know this before choosing Next.js
#2I 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 cost of complexity in your codebase.
Anything else?
Re: You should know this before choosing Next.js
#3Not to mention the absolute worst dev build time that’s had an open PR with a lot of complaints for years and not addressed.
Re: You should know this before choosing Next.js
#4Nice to see someone willing to stick their head above the trench wall. I worked on a "Vercel clone" for a year. After that experience I'd also warn friends to stay clear of Next.js. That said, we don't owe Vercel anything and if they want to ship a framework that's essentially a dongle for their service, they're perfectly entitled to do that.
Re: You should know this before choosing Next.js
#5[deleted]
Re: You should know this before choosing Next.js
#6I was under the impression that Next.js was the successor to React? Is that not the case?
Re: You should know this before choosing Next.js
#7I have been building a completely open-source platform for hosting your own complex web applications.
And I just recently open-sourced the JS framework. It loads modules on-demand as you need them. It’s supposed to be an all-in-one alternative to React+Redux, Angular etc.
Feedback would be welcome. I do want to start promoting it but it’s still early days.
EDIT: why so many downvotes, and no feedback at all? Just curious. Do the downvoters wish I not share my code with open source MIT license with others? They want people to hear only about existing encumbents?
Re: You should know this before choosing Next.js
#8I was under the impression that Next.js was the successor to React? Is that not the case?
Not really. Next.js is still React. It's more like a wrapper/sidecar/framework around React that brings in some opinions on how to build apps and provides some niceties if you buy in.
Re: You should know this before choosing Next.js
#9I was under the impression that Next.js was the successor to React? Is that not the case?
Next.js is a framework built on the React UI library.
Similar to SvelteKit, that's built on Svelte, and Nuxt that's built on Vue.
Re: You should know this before choosing Next.js
#10I was under the impression that Next.js was the successor to React? Is that not the case?
No, React is purely a library for rendering HTML elements on a screen. NextJS uses React for that, but it's more comprehensive. E.g. it provides routing out of the box, and server-side/client-side rendering bits, and it can run your code as a web application.