Artwork

Content provided by Frontend First, Sam Selikoff, and Ryan Toronto. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Frontend First, Sam Selikoff, and Ryan Toronto or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ro.player.fm/legal.
Player FM - Aplicație Podcast
Treceți offline cu aplicația Player FM !

Server Components and the React paradigm

50:45
 
Distribuie
 

Manage episode 358037931 series 1635850
Content provided by Frontend First, Sam Selikoff, and Ryan Toronto. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Frontend First, Sam Selikoff, and Ryan Toronto or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ro.player.fm/legal.

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 - Intro
  • 4:39 - How server-side rendering and hydration work today
  • 14:51 - How RSC works, and why they’re never hydrated
  • 24:48 - What is the React paradigm, and how RSC fits into it
  • 27:54 - How RSC are revalidated
  • 33:52 - Why the goal is not to eliminate Client components
  • 38:53 - What it means for Server components and Client components to compose with each other

Links:

  continue reading

185 episoade

Artwork

Server Components and the React paradigm

Frontend First

199 subscribers

published

iconDistribuie
 
Manage episode 358037931 series 1635850
Content provided by Frontend First, Sam Selikoff, and Ryan Toronto. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Frontend First, Sam Selikoff, and Ryan Toronto or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ro.player.fm/legal.

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 - Intro
  • 4:39 - How server-side rendering and hydration work today
  • 14:51 - How RSC works, and why they’re never hydrated
  • 24:48 - What is the React paradigm, and how RSC fits into it
  • 27:54 - How RSC are revalidated
  • 33:52 - Why the goal is not to eliminate Client components
  • 38:53 - What it means for Server components and Client components to compose with each other

Links:

  continue reading

185 episoade

Toate episoadele

×
 
Loading …

Bun venit la Player FM!

Player FM scanează web-ul pentru podcast-uri de înaltă calitate pentru a vă putea bucura acum. Este cea mai bună aplicație pentru podcast și funcționează pe Android, iPhone și pe web. Înscrieți-vă pentru a sincroniza abonamentele pe toate dispozitivele.

 

Ghid rapid de referință