Next.js Is The Best React Framework
HTML-код
- Опубликовано: 15 июл 2024
- The title should summarize what this video is all about.
Next.js is pretty dang great.
0:00 Intro
0:58 Why isn't React a framework?
1:47 What would you expect from a framework?
2:16 What does Next.js provide out of the box?
3:01 My top 3 Next.js Framework features
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:15 What is Next.js missing?
11:30 Comprehensive data solution
12:30 Database Support
13:06 Authentication
14:06 Competition
14:16 create-react-app
15:21 Vite
16:03 Blitz.js
16:49 Wrap up
--
DISCORD: / discord
VOTE ON VIDEOS: votey-uppy.vercel.app/
NEWSLETTER: hswolff.com/newsletter/
PATREON: / hswolff
TWITCH: / hswolff11
TWITTER: / hswolff
SITE: hswolff.com/ 
Наука
Great video! And thank you for the kind words on Next.js 😁
Thank you! And thank you for building and continuing to develop Next.js :D
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!
Such a great overview! I’ll have to try it now!
Yes! Got one person convinced!!
Useful and Objective video! Thank you, Harry!
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.
It's really best for frontends that require SEO like a storefront. Otherwise SPAs served up with HTTP2 are still king. Any backend is good too. I prefer Elixir.
I am now looking at next.js =) I'm sold.
Yes! Convincing people one by one! haha
❤️❤️ great points 🔥🔥
Great video Harry. Thank you!
top notch content man, nice work
I agree, I am absolutely in love with Next. The last time I was so in love with a technology was React, funnily enough. 😀
Hahah! Yes! Same!
No sun outside, so I'll keep listening
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.
Lol d’oh. Completely forgot about gatsby
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
Just started teaching myself Next for work. Would love to see you do a video on NextAuth.
This very much has to happen.
@@hswolff haha, found it.
I need to do a better one
@@hswolff I'll be looking forward to it 👍
This is awesome! Just curious why you didn’t mention Gatsby as a competitor? I prefer NextJS as well but was just curious.
Gatsby is a static site generator (does not provide server side rendering).
I probably should have, I legit just forgot.
All these features are available for the client js? or you need to have a node server?
Is it monday yet?
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
only if you need state management! it's something you can add if you need it, but otherwise not needed! next.js is basically a react app with a few things included by default
Just started using nextjs. But now I wana try blitz
@@internet4543 ok
@@internet4543 why not ?
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.
Micro front ends is such a loaded term for me. What do you mean specifically? Are you using multiple FE frameworks? Are you federating ownership of the app? What does that mean for you?
Depending on what you're doing then Next.js may have more opinions than are helpful, for sure.
@@hswolff thank you for the response. I completely agree that micro front ends can be a loaded term and super confusing to many. In my current project that I work on, we utilize SingleSPA as the front end orchestration framework with SystemJS for dynamic import and import map polyfills.
In terms of actual applications, we choose to unify the entire platform using only React for all micro apps. However, moving from monolithic apps in the platform to federated apps has been cumbersome.
We can now use Webpack 5 and module federation, however, I have not yet found an instance where the Vercel team has advertised using module federation or singlespa-like frameworks for micro FEs. Currently, as you mentioned, NextJS does utilize Webpack 5 under the hood tor the build process, so maybe you can tap into it 🤷🏻♂️
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...
Learn React first 100%, next js is just a topping to that that will make your life easier.
@@joseandkris Thank you!
It's miles ahead of everyone else
👀
I prefer Gatsby if I don't need server side rendering.
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.
Great note! Fully agreed!
A framework for a framework!
Lol no React is a library
-Framework of a framework??
-No. Framework of a library
Where are you
Nextjs vs Astro?
Saying nextjs is the best react framework is quite a vague and bold statement because software development is about context. You don't take any type of app and use nextjs to build.
It's very good, But I am annoyed with your FREE!
Blitz > Nextjs
Go on! Why??
Blitz is based on NextJS. Of course Blitz would be better, considering it's just nextjs with a bunch of extra features tacked on.
But I'd argue that Blitz is not a front-end framework at all.... It's a full-stack framework...
So I don't think it's completely relevant.
@@hswolff Blitz is just Next.js with some additional features to use it fully as a backend framework.
It has automatic backend communication, so that you can use the backend in the frontend, and it will automatically convert it to API calls for you. It also has form management, and a few other features.
But end of the day, Blitz is just Next.js, so you point that Nextjs is the best react framework still stands.
Though, I'd be curious about your thoughts on Redwood.
@@MarisaClardy Non it doesn't necessarily mean it's going to be better, it depends if the extra features are good enough and they don't break nextjs' stuff. + I read their goal is to become a fork of nextjs and not just be based on it so who knows if they'll stay in the right path after their project become more and more different than nextJs
GATSBY is king. Sorry!
the great gatsby?!
Does it include any scaffold command for quickly creating pages and views?
Answer is no
Does it include any form builders?
Answer is probably no again
Does is include any database and ORM
Answer is still no
Does include any patterns like MVC or a folder structure?
Maybe
So how is this a framework then?
This framework is not going to make my life any easier and I hate to say it, I just have hard time getting excited about react.js in general. I have lived through that nightmare one too many times throughout my career and I don't want to do that anymore
@@guled669 lol so don't use it. 🤷🏾♂️
@@neneodonkor I really don't use it for any of mine passion projects nor do I ever reach out for it when I'm building something for a friend. However at work I have to use it. I think the problem here is that's the only job available as front end developer these day are centered around react.js. I much rather go back and write Vanilla js than using react.js if that was possibility.
Use blitz.js for that if you want all that. It's based on Next.js, but gives you all that stuff.
Next.js is hands down the best minimal framework for React, imo. Beats the socks off of Gatsby.
Though, you mention you don't even like react, so why bother leaving a comment?
(Also, FYI: You don't need all those things you mention to be a framework, because it depends on how kitchen-sink you want to be)
@@MarisaClardy I feel like you certainly going need some kind form builders with validators, if you're going to build a real web application and not just todo-app and you also need some kind folder structure for puttings things especially when working with a team. Problem with a lot of these frontend framework is like they don't care at all about the backend or providing deeper integration.
...and I know these words sometimes are just semantics but whatta hell is a minimal framework and how is that different from library?