What problems do React Server Components solve?

Frontend First

Sam and Ryan share their learnings from working with Server Components in earnest over the past week. They talk about how Server Components can simplify client components by passing them props, why it makes sense for a component that can run everywhere to be a Server Component by default, whether RSC is causing unnecessary churn in the ecosystem, and how to think about choosing Server Components vs. client components for a given task.

Topics include:

  • 0:00 - Intro
  • 0:48 - Lessons learned from building a D3 chart as a React Server Component
  • 22:04 - Are Server Components causing unnecessary churn in the JavaScript ecosystem?
  • 32:14 - Do Server Components replace Client Components?
  • 40:13 - Ryan’s thoughts on rewriting some client-side data fetching code with Server Components

Links:

Please note that Dev Shows isn’t affiliated with the featured podcasts. Each podcast’s content (logo and other images, audio, and text) is property of the show itself. Their content is retrieved from the show’s RSS feed and may contain the occasional error, such as an MP3 audio URL that doesn't work. And, of course, any opinions expressed, or product endorsements made, by a show’s host(s) or guest(s) are theirs alone.

All other content is © 2020–21 Dev Shows.

Made by Bruce.
I’m a freelance developer available for hire.

Audio Player

-
--:--
--:--