Is NextJS the future of React?
HTML-код
- Опубликовано: 13 сен 2024
- A new Next JS version is out. And it brings some radical changes that seem to embody the direction React is moving in. What does that mean for us developers?
In this video, we are going to take a look at React: what it was intended to do and the shortcomings of that initial vision.
Then we’ll look at how the Next JS team tried to solve those issues and produced some new difficulties. And we will look at how the React team has been working hand in hand with NextJS to solve those shortcomings.
And how Next JS’s latest version embodies React’s vision for the future.
And above all, we will be looking at what that means for us developers.
-------
Want to go into further depth? Head to kodaps.dev/
This is beautiful. I tried out the NextJs13 and its new features like the loading ui, app directory, and the use hook. It's preety neat but crashes sometimes.
Because it's still in beta version.
Hopefully version 13.3 that has just come out should be a bit more stable , they say the app directory router is getting closer to being ready
Don’t run into hype train without understanding your requirements for your project. NextJS will be great for a e-commerce project where you have most of the data stored on your server but if your app has complex routing and many third party intergration where server side cannot possibly render without user interaction it will be a nightmare for you. We are currently migrating to React from next JS while few other projects we have with next JS works perfectly. It depends on your app requirement
I agree wholeheartedly :)
What about Solid JS?
could you be more specific about "complex routing" and "many third party integration". thanks!
Why back to React? UX? What happened then with the SEO?
There are some use cases (customer area, dashboard, …) where the page is behind auth and there is no need for SEO where having logic client side makes some sense :)
Thank you for your amazing explanations! I am a backend engineer, looking to understand the right frontend tools for my startup's product. Your explanations cover architectural depth and how it impacts dev/user experience. Keep up the great work!
Hi I'm glad you found the video instructive :)
Fantastic video. Thanks for covering the history of both react and next and where they are going.
I’m glad you liked it :)
People say NextJS is php but nextJS is way more convinent. Worst case senerio you can develop it like a react app but you can now easily build a full stack app with backend and api stuff more streamlined. It's really cool for solo developers and saves us a lot of time.
Great video! Very excited to be using this in the future!
MAN I LOVE HE WAY YOU EXPLAIN !!!!! thanks for your video !!!!!!!
best video on react & nextjs
you can start at around 2:30 unless you really don't know how websites work (in which case, surely it's unlikely that you'd be watching this?). Some useful fundamental stuff afterwards, for somebody like me who has zero knowledge of Next.js. Thank you.
@4:35 - 4:50 is exactly why I find react / nextjs has a steep learning curve as well (it is often presented as easy to learn)
the intial getServerSideProps was an initial mind shift, and now it is obsolete. The API moves too fast to ever master, and frankly seems like there is no long term vision. I'd add that for those new developers just being onboarded, it is blurring the lines around the network boundary (front / back) and making debugging harder
This is incredible, thank you, I just wanted to know the difference between learning Express VS Next ? For the client side, Im going to use React, so is it better to use Next ?
It kind of depends how much server side logic you will need. If you're using React generally speaking I would recommend Next, unless the main focus is something very specifically server side like building an API for external (third-party) use. Hope that helps :)
@@KodapsAcademy Thank you so much for this & getting back to me so quickly, much appreciated, This makes sense, I am already using Spring Boot Java/Kotlin for API's so I guess I can use that for the API's and use Next for React.
For a b2b SAAS product that is being developed from scratch, do you advise using Angular or Next.js or Qwik? We would like a reliable frontend architecture where developers are high productive for next 5+ years. Appreciate your advice.
Hi, it depends on how much structure your dev lead can impose. If I were starting a B2B SaaS product I personally would go for NextJS, for the ideas I would want to implement. The alternative for me would be an Angular frontend and a NestJS backend. Of course that will also depend on the exact requirements of what you would like to build.
thanks for the explanation
if in your app real time communication happening using websocket where SSR is not required then in this case next js is use full?
if some one want to go with react what is the best build tools to start like parcel /vite?
great pacing and delivery
Thank you very much :)
What did you mean by saying php and RoR have done same in the past?
What I've never understood about SSR: is that it improves wait time. But rendering and computing still has to happen whether server or client. I imagine there is a slightly noticable wait improvement but nothing huge and the user will see a white screen instead of some content. So I don't see it as a huge benefit but I do love static rendered Websites if they are small. Can someone tell me what I may be misunderstanding? Never tried NextJS.
The rendered content can be cached server side so it doesn’t need to be recalculated
It can be a huge difference, depending on your app. You're correct that the server still has to render it (although that is often mitigated with prerendering), but what you have to realize is that the server is already running. Before react runs on the client the browser has to download the page, parse any styles/css, load & parse the JavaScript, THEN it can render. All the while the client is staring at a blank screen. The actual rendering part is typically pretty short (~1-300ms maybe), it's the time between page load and the browser being ready to run react that SSR skips, and that's what can make such a noticeable improvement
I just do server side generating every 5 minutes for dynamic apps that aren't realtime, works wonders for me
@@KodapsAcademy Great advantage! I didn't think about that. Im curious if thats default or a common feature.
@@mlmFormula Thank you, very detailed and insightful!
As a beginner what should we learn react js of nextjs
You need to know a bit of React to learn Next JS, so I would start with React :)
@@KodapsAcademy Thnaks sir
a lot of informations in thisvideo . thank you
I’m glad to be of service :)
Should I always just use Nextjs for my next project without considering using ReactJs?
If you're coding a website that needs SEO, yes. If you're doing something that doesn't need any SEO, don't bother. In between, it depends on your use case. If your purpose is to learn, go for Next JS.
that closing statement was hard
I’m not sure I understand what you mean :) how was it hard ?
@@KodapsAcademy I mean it was really cool😂
Helpful video, thank you!
Glad to be of service :)
Amazing video thanks!
Hey, I'm glad you liked it :)
Good explanation, thank you
My pleasure :)
Pls I want to go into tech (a cs student actually) but didn't know where to start....
I would recommend you start a course on free code camp (freeCodeCamp.org if memory serves) and see if you like it. (That’s how my daughter started coding :) )
Your videos would've been better if you would stop repeating your questions over and over at each point. Just go straight to the point after one question. No need to repeat the questions or issues for dramatic purposes.
Thanks for the constructive feedback :)
Too many effects. Tone it down. You are interesting, let your wisdom entertain us.
Pls I want to go into tech (a cs student actually) but didn't know where to start....
@Neche Okechukwu Hey, you can start with either web development or mobile applications. dig into how web development works like front-end, back-end, then there is mobile application which are native and cross platform, native is like you build application for only ios or android perticularly and cross platform is like you will write code once and it will work on both, at first try everything and find what suits you, and don't go with hypes like rn everyone is talking about next. go with tech which you like and you're comfetable with, sorry for bad english.
@@ExeeGamingYT I would love to but have. Always been confused on course to start with ,whether mobile or web dev.
@@Henzanno if you want to learn react then there is good channel called "Jack Herrington" you can try few videos first 😄
@@Henzanno and there is another channel called "The coding train" which has good coding Content and good way to teach 😄, but many video are based on javascript
@@ExeeGamingYT thanks alot, which are u into?