Tom Occhino on the future of React

Frontend First

Contenido proporcionado por Frontend First, Sam Selikoff, and Ryan Toronto. Todo el contenido del podcast, incluidos episodios, gráficos y descripciones de podcast, lo carga y proporciona directamente Frontend First, Sam Selikoff, and Ryan Toronto o su socio de plataforma de podcast. Si cree que alguien está utilizando su trabajo protegido por derechos de autor sin su permiso, puede seguir el proceso descrito aquí https://es.player.fm/legal.

1y ago 1:00:27

MP3•Episodio en casa

Tom Occhino, Chief Product Officer at Vercel and former Engineering Director at Facebook, joins Sam to talk about the pivotal moments in React's history. He talks about how React popularized the ideas of declarative rendering and unidirectional data flow, how GraphQL furthered React's goal of co-locating all the concerns of a particular piece of UI, the problems that GraphQL led to at Facebook and how Relay solved them, and how Suspense, Server Components, and PPR are the generalized spiritual successors to the stack used at Facebook.

Timestamps:

0:00 - Intro
2:53 - Declarative rendering as React's legacy
8:12 - How GraphQL enabled complex components to be fully self-contained
20:12 - How React's goal has always been to co-locate all the concerns of a particular piece of UI
22:58 - The problem with co-locating GraphQL with components, and how Relay solved it
26:28 - How RSC is the generalized spiritual successor to BigPipe and GraphQL
34:46 - What PPR is, and how it and Suspense fit into this story
55:55 - The general paradigm shift of getting static code to the device as soon as possible

Links:

201 episodios

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