Audio is streamed directly from the publisher (cdn.simplecast.com) as published in their RSS feed. Play Podcasts does not host this file. Rights-holders can request removal through the copyright & takedown page.
Show Notes
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: