The Web's Next Transformation
summary
Argument: the web shifts to a PESPA architecture that shares routing, data fetching, rendering and mutation code between client and server to remove duplication, cut client JS, avoid waterfall loads and eliminate heavyweight application state. Concrete proof: Remix implements this pattern, the repo and Epic web.dev examples show routes with server-only loaders and progressive enhancement, and a real app achieves a 100 performance score on an authenticated page after Shopify acquires Remix.
AI-written summary · about
chapters (5)
- 0:00Start
- 2:02Web Architectures
- 2:37Follow the code
- 7:44Progressively Enhanced Multi-Page Apps (PEMPA)
- 9:38Single Page Apps (SPA)
related talks
29mKeynote: Kent C. Dodds - The Web's Next Transition
20mRemixing How We Give
41mProgressive Web
47mFrontend Architectures: The Next Generations
13mReact Remixed
22mBringing Back Progressive Enhancement
24mServing content on the web: from PHP to RSC—and beyond
41mRemix, the hottest JavaScript framework as of today
