Next.js Is The Best React Framework

The title should summarize what this video is all about.

0:00 Intro
0:58 Why isn't React a framework?
1:47 What would you expect from a framework?
3:13 Routing
4:25 Hybrid Rendering Strategies
5:23 Developer Experience
5:34 CSS Support
6:56 Fast Refresh
8:00 ESLint
8:21 TypeScript
9:25 No Config
10:07 Powerful Upgrades
11:30 Comprehensive data solution
12:30 Database Support
13:06 Authentication
14:06 Competition
14:16 create-react-app
15:21 Vite
16:49 Wrap up

——

[leerob]

Great video! And thank you for the kind words on Next.js 😁

[fordneild]

We use react module federation to have a multi repo front end where we inject remote components into the main app. Not saying its better or worse, but it what we got. Great video!

[runonce]

I was so into Next.js but the more I tried the more it felt like the main feature (SSR and statig pages) was not adding too much value to my projects. But now I want to give it another try! Thank you for the vid.

[vasiovasio]

Useful and Objective video! Thank you, Harry!

[DamianDemasi]

Such a great overview! I’ll have to try it now!

[konstantinospascal]

I agree, I am absolutely in love with Next. The last time I was so in love with a technology was React, funnily enough. 😀

[wolfymaster]

I am now looking at next.js =) I'm sold.

[Producdevity]

No sun outside, so I'll keep listening

[damainjoseph]

Great video! I think Gatsby is a better apples-to-apples comparison in terms of something being a react framework rather than Vite and CRA. Those two are really starter templates.

[Nephel]

Just started teaching myself Next for work. Would love to see you do a video on NextAuth.

[JohnVandivier]

blitz.js is amazing: integrates Prisma ORM with full stack SSG compliant next and will build CRUD forms via CLI, uses react-query, prettier, linting, and great lib stack ootb

[polyglotprogrammer]

This is awesome! Just curious why you didn’t mention Gatsby as a competitor? I prefer NextJS as well but was just curious.

[joseandkris]

It's miles ahead of everyone else

[fullstackrdev]

Is it necessary to use state management in Next.js? I'm kind of new to this concept. I know SSR that it serves the html in the server so how does it fit or connect to a state management? This might not be a valid question. Thanks in advance :D

[ricardodasilva]

All these features are available for the client js? or you need to have a node server?

[ZiPMo]

Just started using nextjs. But now I wana try blitz

[themarksmith]

For those who don't already know React, would you advise learning React first, and then move on to Next.js - or can newbies focus on learning Next.js straight off the bat? Forgive me if Next.js extends React, and therefore you need to know React first, so this is a silly question...

[DiegoBM]

I'd add that it doesn't provide global state management either. One could argue that it depends on the application, but if we're talking about things/opinions that you get out of the box with Next, then global state management is a big one missing, and one of the biggest pain points in React apps.

[ericzorn]

Hey, I personally will always use NextJS IF building a monolithic front end application. Currently we are focusing on building applications with micro front ends. Most all of the application orchestration in this case is handled client side and only recently has support for server side rendering. I do not believe that major frameworks for micro front end development, such as single SPA, are supporting NextJS out of the box. Therefore, the only case I can see using next in this context would be for the container application that renders all of your micro front end apps. Otherwise, I would always turn to using next one building react applications currently.

[micoberss]

-Framework of a framework??
-No. Framework of a library