React Server Components Change Everything

This is worse than PHP. Because in PHP, it was assumed that html was served by the backend. Here, it’s a separate server just for React Server Components. I never understood why do we need to keep separate our UI and back. It’s just adds up I/O cycles.

It's so funny watching all you frontend developers realizing your mistake and going full circle full stack again lol

So, Future of React is… Svelte?! Finally!!!

Hmmm and then you need to run a local server to be able to debug your server components, you need a more powerful machine for that. Then your code base is divided, you have potentially dumber FE stuff, this FE on server stuff and then the BE stuff, logic all over the place. Then the server needs to be extra powerful since it's going to process a bunch of stuff that was divided to each client before. Debugging? So much fun, does it run locally? Or on the server?
Then the next version of react will say "hey guys! Remember all that old server components? Well now you better do them on the client! It fres server resources and you dont need to run a local server to develop! How innovative we are!"

Thanks!

How would you perform CRUD functions in NextJS?

No error management on the right?

Welcome to 90th. We came back to PHP now. This is not a way guys, I'm telling you now.

which font is that ?

Sorry I’m disappointed with that video: it’s all about NextJS or basic React?

Not really sure how it changes everything as this is the way web apps were built since forever using PHP/Java/Perl etc

Came here for the php comments 😅

Your head moves way too much

So it's just SSR? like what PHP has been doing for the last 25 years?

COding is dead, AI is taking over!

I really love next js , ho w routes work how eaasy to write code , but maaaan why doesn't support websocket

Love the idea but come on let's be honest, the use client directive is so annoying. I'll wait for the ecosystem to find better ideas to jump into it

Every UI should be on the frontend

The new server side components are the old smarty templates.
LoL

I had a taste of angular.. couldn't achieve my goals with it... then moved to react to try my luck: ended up at the same dead end... so VanillaJS all the time.. 💪

react and other frameworks are good (just like type script) for big tech companies.. where the people are coming and going, so these frameworks can provide a standardise way to have each 'engineer' replaceable overnight..

Coming from sveltekit and nuxt and not being able to in nextjs to put a button with on click on a server page was infuriating. It should be able to defer these illegal things until the page has loaded or be able to mark the button for only rendering after server portion has loaded without giving you an error. Basically any dynamic component using these properties force you to make everything use client, it’s unfortunate.

Your overview is full of optimism. Truly. Aggressive caching and the necessity to rid hooks completely bewilder me.

Did you guys try it? Is it me or it's really slow, and your website ends up showing skeletons for seconds? Am I doing something wrong?
Do you find your vercel snappy? I don't honestly, hopeful to get some replies

Basically what we have with svelte.js

ReactServerComponents - a feature that exists exclusively in the React-Vercel world.

so react is returning to the OG way and letting go of all of the things it created slowly😅😅

I am curious about state management now

How could this be a React feature if React apps used to be compiled into JS files and served by separate webservers like Apache or NginX?

How does it change "Everything"?? What is the point of this title? Can you explain? It changes NOTHING! You still need to fetch data from frontend. Server components has its place but not needed everywhere.

front end guys rly do run in circles.

Angular: you were supposed to replace me, not become me

how to use redux in NextJs ? I want to clear my doubts can you make video on it ? client/server/redux how it works for big project?

Great video, what about the subscriptions? how to use them

Your videos are always entertaining,to the point and useful. Thanks

will it replace rtk queries ?

Should not be combining await and .then within an async function. My 2 cents.

React only attractive to ppl with ADHD or repetitive compulsive disorder. ITgey rewrite their apps once every year n good luck to the companies giving u such time n resources.

Really easy to understand, thank you so much

Instead of this we should use react query
it does all this things beautifully and it also provides us data for loading error
we should just make use of react-query on top of fetch in our react application

React literally has no future at this stage honestly

I always use async await.

How do we put on click event on each todo in a server component then?

NUXT also handles server side very well

the people from 200x using just Server Sites.
the people from 201x using just Client Sites.
the people from 202x using both.

That's how i use to work

Just Amazing! Thanks !!

Five years ago, I chatted with Dan about async component. He said won’t do it and it is not react way. Now they understand what I was talking about async component.

No interaction isn't the only downside of the approach, it's the deal breaker. I don't remember last time a had to just display some data