What problems do React Server Components solve?

Frontend First

Contenuto fornito da Frontend First, Sam Selikoff, and Ryan Toronto. Tutti i contenuti dei podcast, inclusi episodi, grafica e descrizioni dei podcast, vengono caricati e forniti direttamente da Frontend First, Sam Selikoff, and Ryan Toronto o dal partner della piattaforma podcast. Se ritieni che qualcuno stia utilizzando la tua opera protetta da copyright senza la tua autorizzazione, puoi seguire la procedura descritta qui https://it.player.fm/legal.

1+ y ago 51:05

MP3•Pagina principale dell'episodio

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:

196 episodi

#Technology #Web #Ember #Software #Development #Design #Web Development #Tech #Software Development #Frontend #Ryan Toronto #Sam Selikoff #JavaScript #Emberjs