What is React Server Components? (Don't Worry About It!)

[@mustafaalfar7936]

Regarding SEO, when React send the SS components not in html format, so can Google crawlers still serve the content?

[@BobbyBundlez]

no. you need something like prerender.io this is why SEO is so SHIT with react

[@DedicatedManagers]

At 5:58 you say the server can render client components but not the other way around. But at another point, I think you say that the server can’t have either state or useEffect type stuff. So how can a server component render a client component if the client component has one of those things in it?

[@zomakaja]

Reminds me of Phoenix LiveView

[@rundtmeg]

Gatsby Apps and Webpages will get benefits from it also. SSR components would be a better term actually.

[@yudhiesh1997]

Need more videos on React and Typescript!

[@damiansutton80]

Sorry mate. I have to strongly disagree about this not being important to people that only use React on the client side. If you have a massive client side React that is not performing due to the need to download and parse massive amounts of JavaScript before you can get a meaningful first render, React Server Components could be a great option to vastly improve the performance of your website and especially your first meaningful render.

[@hswolff]

Definitely true - but! That means you’re using react on the server! But good to raise awareness for the client only react apps that are hurting.

[@DanAbramov8]

Well, I'd say lots of people don't use React on the server _because_ it didn't solve this problem adequately before (you still had to download all JS) and because it was hard/annoying to wire up data fetching. So arguably some people who have client-only apps would still be interested in Server Components!

[@hswolff]

Absolutely! I think crossing that hurdle to standing up a node server to solve for this is a high point of friction. I’d bet adoption for server components will sky rocket when/if it becomes available for other server runtimes.

[@DanAbramov8]

What kind of runtimes do you have in mind?

[@DanAbramov8]

Btw, another use case is static site generation. E.g. imagine you could get a statically generated React blog by writing a component that just maps over the filesystem.

[@runonce]

Finally some alternative to solve client waterfall

[@Aresky]

Great content!

[@cauebahia]

Thanks for this video!

[@hswolff]

My pleasure!

[@kumarvishalben]

Noob : why not just use database from frontend and skip the backend. React Team : Yes 😂

[@BobbyBundlez]

lmfao

[@MegaRelja]

There is the same thing in Java Servlets. There is nothing new, they are just reinventing the wheel...

[@TheSldsnake]

Yes but i think the frontend dev miss 10 years and only view js frameworks

[@DanAbramov8]

Not really, there's quite a bit of difference. Server Components tree can be refetched _without_ losing Client state inside of it (such as focus, scroll position, inputs, and other things). This makes it pretty different from traditional server approaches. Also, you can reuse the same components between Client and Server, depending on the use case. This is also different from traditional server-only approaches.

[@MegaRelja]

@@DanAbramov8 Thanks for the clarification!

[@jean-bricerougeot6761]

How can you answer the "Should you care ?" question without knowing what it is ? May be you can start by telling us what is, so that we can use our own critical thinking to decide whether we should care or not !? ^^ Thanks

[@hswolff]

You’re welcome!

[@archmad]

goodbye graphql