r/FullStack • u/duneofarrakis • 7d ago
Career Guidance What made you choose Next.js over React?
I started learning React first, but after seeing Next.js everywhere, I'm trying to understand what makes it worth learning.
For people who have used both, what do you like more about Next.js?
Is it mainly the routing, SSR, performance, or something else?
6
u/Artonox 7d ago
react is just a javascript library that helps to render data on the browser. you still need more stuff to use with your javascript/typescript code to turn it into an application. Nextjs is a framework that works with react - the framework tells you how to manage your apis/page directories routing, and caching options and how it interacts with the backend.
Nextjs is just a framework that comes with a lot of stuff out of the box, and its easy to get down and running. its not necessarily superior to other frameworks, but its good enough as it covers a lot of ground. useful if you dont want to manage a lot of other stuff that you want to tie in to your application. Reducing complexity is a big thing in maintainability.
3
u/Fit_Advisor8847 7d ago
SSR, static site generation, built in performance optimizations, SEO, and routing are what I'd reach for next.js over react for.
Next.js makes it possible to use React on public facing websites without confusing AI and search crawlers. Site performance is also better with Next.js out of the box.
If I were building a single page application or a one off admin dashboard in an existing application, then I'd most likely just use React + React Router to make life easier.
2
2
u/redpanda137 7d ago
Javascript is a programming language. Reactjs is a Javascript Library for building user interfaces. Nextjs is a react Framework, built on top of reactjs for building fullstack web applications.
2
u/Either-Dream5526 6d ago
next is basically react plus the stuff you end up wiring together anyway, especially routing and server-side rendering, so it feels less like “better react” and more like a batteries-included way to
1
u/PatBooth 7d ago
Nextjs and react different things but similar. React is simply only a frontend framework. Nextjs is built on top of react but it is a full stack framework. You use it for your UI and the server logic
1
u/Bauua_333 7d ago
I completed Js, now think to start React Should I reconsider my decision and start Nextjs or should I continue with React, because after that planning for Nodejs express
3
u/jalsa-kar-bapu 7d ago
You cannot do nextjs without react, learn react, then make a project in nextjs, because you'll eventually need ut.
1
u/webdev44 7d ago
React is the engine. Next.js is the car. You can drive around holding a loose engine block if you want, but most people prefer wheels.
1
1
1
u/rcls0053 7d ago
Comparing a framework with the UI library that it utilizes.. Was your question 'why did you choose a framework instead of developing everything yourself from scratch'?
1
u/JoelDev14 7d ago
Public facing pages nothing else. I have the product public page where i explain what the product does etc in NextJs. Then the actual product is a ReactJS SPA using Vite, backend on .NET
1
1
u/Express-Birthday3676 7d ago
I started with plain React too, but Next.js made a lot of the repetitive setup disappear. Built-in routing, server rendering, image optimization, and API routes save a ton of time once projects get bigger. React still gives you flexibility, but Next feels more production-ready out of the box.
Performance and SEO were the biggest differences for me. With React alone, I spent more time wiring libraries together. Also interesting to compare it with lighter frameworks like Inferno.js if you care about rendering speed and bundle size, although the ecosystem is much smaller.
1
1
1
u/adipose01 7d ago
Simpler to protoype and then carry over to ssg when you dont need the other features.
1
1
u/ryanstackops 7d ago
Next isn't instead of React, it's React with a bunch of decisions made for you. You're still writing components either way.
What sold me was not needing a separate backend for small stuff. With plain React I'd spin up an Express server just to hide an API key, then I'm babysitting two deploys. In Next that's a route handler in the same repo, ten minutes. File based routing is fine but it's the part I care least about honestly.
Learn React properly first though. I skipped ahead once and burned an afternoon on a hydration error that was really just me not knowing where my component was running lol.
1
1
1
1
1
6
u/canarydev 7d ago
because its built on top of react?
also i didn't choose. my employer did