The Truth About React Server Components

Рет қаралды 43,376

6 ай бұрын

Obviously I love server components, but are they ACTUALLY ready for production? I think it's important that we talk about it.
Check out my Twitch, Twitter, Discord more at t3.gg
S/O Ph4seOn3 for the awesome edit 🙏

Пікірлер: 143

@fnfal113

Meanwhile here I am using Laravel, life is

@siobe0

I'm confused why you think this video might do more harm than good? This is the most thorough explanation I've seen and it really helped describe the changes between RSC and gSSP.

@Hexalyse

I've been using the new app router for two months, and I still learned a ton of things in this video. Notably how to think my server and client component separation better, so that I reduce the amount of JS I send to the client.

@OybekDaniyarov

Great video, I totally agree with you. Having exercise in backend is super useful on react server components

@samifouad

good video. i think

@ghostlexly

If you need:

@theklr

A tad disappointed you avoided the bigger concern. That somehow a year later Next is still exclusive to using RSC. There’s barely been any movement in development tools with leveraging RSC and documentation is still little to none. While I do get the value of RSC and edge based applications, most missed the JAMstack era and are being thrusted into thinking about this, something next and others originally prevented. It’s returning back to the old JS fatigue days because we’re once again spending time on bike shedding instead of building code.

@NickServ

Server actions have been promoted to canary (same as server components) since this was recorded. Additionally, as of today (a day after the video was posted), Next's implementation is stable.

@pencilcheck

Theo's video has made me aware of the advances of some full stack tech without having to spent time on it. I ultimately end up didn't use most of the tech stack he recommend but a lot of them stem from his stack and recommendations. I want to get rid of react but I feel like I can't due to some UI frameworks I use for clients heavily rely on react

@craigcaski

Great breakdown thank you

@thetruth9807

This reminds me of that episode from Silicone Valley where he starts trying to break down the concept behind Pied Piper to that focus group.

@tarat.techhh

thnk u so much for this video!

@mateja176

In the RSC model, the component tree is going to be rendered to HTML up until the suspense boundary level. Then the minimum JavaScript is fetched in order to partially hydrate the HTML. Asynchronously, the now resolved components are streamed to the client in the special JSON format. Are the streamed in components simultaneously rendered and hydrated?

@faizanahmed9304

Very good video on different models. How are they different from each other. Thanks!

@bideshbanerjee5506

THEO do you have seen any article or know how RSC update the UI without reloading the page.

@puopg

Could you link to an example similar to your tab one where the content of each tab is more dynamic?

@sergeik2947 14 күн бұрын

Good video!

@henrmota

This was happening before a long time ago with PHP for example. We got to embrace more the fact that Next.js is a full-stack framework and not only a front-end framework. Server components are just like an API, you make a request it returns an immutable result. Client Components are components that are mutable and so client have to download all the machinery to support that mutability.