In many ways, GraphQL has been the pinnacle of data fetching in frontend applications since its inception. Yet it seems like every year we come up with new methods to send our data to the browser. Even React Server Components are rumored to have come about as an attempt to answer this question. Let's look critically at why this question got asked in the first place, and why we are still asking it.

[0:00] Starting Soon...
[2:00] Preamble
[10:00] Why Are We Talking About GraphQL?
[20:00] GraphQL's Allure & Ryan's History
[36:00] The Normalized, ClientSide Cache
[44:00] The Gap Between Promise & Reality
[53:00] Why Not Just Use a Query Cache?
[59:00] tRPC's Benefits & Limitations
[1:08:45] Why Not Just Use a Page Cache?
[1:16:00] RSC's & The Single Server Tree
[1:23:45] Stateful Backends & Interactivity
[1:32:45] What Value Do Server Components Bring?
[1:46:15] A New Authoring Experience
[1:51:15] Updating The SolidStart Notes Demo
[2:00:15] Single Flight Mutations
[2:10:30] How Is This Different? (Excalidraw!)
[2:19:15] Reduced Bundle Sizes
[2:26:45] Finding The Sweet Spot
[2:32:30] Optimistic Updates
[2:49:45] Conclusion: Improving UX & DX Together
[3:07:30] This Week in JavaScript: Solid News
[3:13:00] TWiJ: Link & Form vs. Composability
[3:24:00] TWiJ: Web Components & React
[3:30:15] TWiJ: Leptos Islands Demo
[3:39:15] TWiJ: OpenSauced & bobaekang
[3:48:45] TWiJ: Ryan Florence & Sunil Pai
[3:51:45] TWiJ: Signals & Server Components
[4:01:45] Conclusion: The Other Side of the Slope

Thanks @zombiefacesupreme for the timestamps.