What problems do React Server Components solve?

Frontend First

Conteúdo fornecido por Frontend First, Sam Selikoff, and Ryan Toronto. Todo o conteúdo do podcast, incluindo episódios, gráficos e descrições de podcast, é carregado e fornecido diretamente por Frontend First, Sam Selikoff, and Ryan Toronto ou por seu parceiro de plataforma de podcast. Se você acredita que alguém está usando seu trabalho protegido por direitos autorais sem sua permissão, siga o processo descrito aqui https://pt.player.fm/legal.

1y ago 51:05

MP3•Home de episódios

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:

187 episódios

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