Server Components and the React paradigm
Frontend First
English - March 15, 2023 15:00 - 50 minutes - 46.5 MB - ★★★★★ - 18 ratingsTechnology technology web javascript ember ember.js software development design Homepage Download Apple Podcasts Google Podcasts Overcast Castro Pocket Casts RSS feed
Previous Episode: HTML, HTTP, and React
Next Episode: JavaScript needs a model layer
Ryan and Sam use some recent Twitter conversation to guide a discussion about the design and purpose of React Server Components. They talk about how client trees and rendered on the server today, why a server-side rendered prepass is wasteful in light of RSC, how hydration of a client tree works, why RSC are never hydrated, how RSC is a purely additive technology, how server and client components can be interleaved, how RSC can be refreshed in-place without loss of any client state, how RSC fits into the React paradigm despite having a unique syntax and set of capabilities, and other topics.
Topics include:
0:00 - Intro4:39 - How server-side rendering and hydration work today14:51 - How RSC works, and why they’re never hydrated24:48 - What is the React paradigm, and how RSC fits into it27:54 - How RSC are revalidated33:52 - Why the goal is not to eliminate Client components38:53 - What it means for Server components and Client components to compose with each otherLinks:
Dan Abramov’s RSC AMA threadIllustration of server and client trees