A podcast about modern UI development on the web. Hosted by Sam Selikoff and Ryan Toronto.
Lessons learned from implementing RSC: Part 1
Ryan shares how building his own RSC implementation from scratch helped him better understand React’s new paradigm. He and Sam talk about how a client React app can fetch an RSC Payload from a server endpoint to update the UI, how an RSC server renders and bundles Client code that’s part of a Server Component tree, and how a client-side Router can be used to fetch new RSC trees based on the URL.
Should a navigation and a refresh show the same page?
Ryan and Sam talk about how to invalidate Next.js’ client-side cache when a different session makes changes to backend data, and ultimately discuss whether clicking a link to a URL vs. hitting refresh on that same URL should render the same page if no backend data has changed.
Tim Neutkens on the Next.js App Router
Tim joins Sam to talk about his work on the new app router in Next.js 13. He explains how the app router leverages Server Components and React’s new cache API to bring a new level of composability to server-side code, how Server Actions are being designed to enable partial revalidation in a single round trip to the server, and how to think about UI updates as a result of server-side state changes.
Understanding prop passing from RSC to Client Components
Sam and Ryan discuss how TypeScript helped them understand the mechanics of how props get passed from Server Components to Client Components, and how to properly type client component props if the prop starts out as a rich data type on the server. They also clarify some points from last episode’s discussion about the RSC payload.
Server-side rendering vs. Server Components
Reusable pending UI for forms with Server Actions
Real World Development Discussion
What I enjoy about this podcast is that Ryan and Sam talk about the pitfalls and successes of not just Ember, but web development in general. Nothing is perfect and as developers, we all encounter rough edges and it’s refreshing to hear their discussions and thoughts.
One of the hosts is really rude
I think it is Sam. I only listened to one episode where they are chatting about server components. I really felt sorry for Ryan. Every time when Ryan wanted to say something he got interrupted by Sam who never used server components. As an listener, I was really hoping I could hear Ryan’s understanding on the server components because it is him who played with server components, but Sam kept interrupting Ryan and talking about his understanding based on his guess.It’s so annoying that I couldn’t really learn anything from this kind of chat.
One of my goto podcasts
Sam and Ryan do a fantasitc job unpacking the nuances and challenges of building real applications using Ember. I listen to every one of these and look forward to the next.