Reflecting on React Server Components

Obviously I love server components, but are they ACTUALLY ready for production? I think it's important that we talk about it.

S/O Ph4seOn3 for the awesome edit 🙏

[siobe]

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.

Super glad you didn't edit out the part where you explained Sam's tweets. Shoutout Sam and you both for this explanation, love both your channels.

[ghostlexly]

If you need:
- any third party services to connect to your app
- a public api
- a mobile app
- queues/jobs
- roles / security middleware
- complex middlewares
- anything complex
- futureproof
- animations / nice UX / framer motion

Then, you can't use server actions. This is like 99% of my projects.

[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.

[samifouad]

good video. i think 13:27 was very clear. should maybe even be its own video. just seeing the results of a simple change to the code demonstrates the new behaviour very good without any hand-wavy concepts and hard to digest explainations. 15:49 also a good moment that could get cleaned up to be a good demo of RSC.

[OybekDaniyarov]

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

[thetruth]

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.

[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.

[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

[faizanahmed]

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

[mateja]

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?

[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.

[bideshbanerjee]

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?

I think this made a lot of sense when the html is static but I’m curious how things work when there’s more dynamic components that either take in props or say some local data like for example the devicePixelRatio

[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.

[nortonice]

Can you please explain how it will impact amount of computing that will happen on the server? Because running code on a client is free for me but increasing amount of computing on the server may increase costs of running my server.

[adfasdfasdf]

at 9:43 I dont think the old SSR model is that bad. In the example, you said if you run fetch to get data, you would need to do that on both server and client. However, normally fetches are only in GSSP. Any other fetches would be in a useEffect of some sort. So I dont see any scenarios you would run fetch on server and client

[sergeik]

Good video!

Just one thing - at 9:13, Theo talks about fetch, which happens two times - on server and client. As far as I understand, it's not the case. Fetching data can only happen in useEffect, which runs only on client. Am I missing something?

[nicolasguillenc]

Quick question, is this react or next js? I think it's next js but I see that React has server components too and I am just trying to figure out where I got lost

[chrisochs]

So as someone who doesn't do front end stuff I was watching this and first thing I did was go and google react server components. Couldn't find a simple clear answer. I just wanted the basics how does it work. Not some dumbed down react for dummies answer but a clear concise technical description.

Personally I think this type of thing is easier to understand if you completely separate the framework from the flow. Explain the fundamentals first. This video still left me not really clear on what the fundamentals are.

[vishalsangole]

One thing i didn't get is that why did theo used a state in button component. Instead of passing a and b to TabOptions component (client component) he should have moved state in page, either way you are rendering client component only. I think example was wrong