Serving content on the web: from PHP to RSC—and beyond
summary
A concrete claim: server rendering plus client-run loaders kill the server/client impedance mismatch by sending initial HTML then handing control to a client SPA; evidence: a real Spotify for Artists profile with a dozen distinct endpoints and interactive SVG visualizations, built and running. Tools actually used and compared: PHP + jQuery, SPAs, Next, Remix, React Server Components, and React Query with 15 million weekly downloads. Newer frameworks offer isomorphic loaders; they work but force careful parallel fetching to avoid slow cross‑internet waterfalls.
AI-written summary · about
chapters (12)
- 0:00Web framework evolution
- 3:10Interactive web experiences
- 5:38PHP limits
- 8:07SPA trade-offs
- 10:36Client-side fetching cost
- 12:04Meta frameworks evolution
- 15:36React Server Components
- 16:40React Query data management
- 18:25Isomorphic loaders
- 20:51Isomorphic loading pitfalls
- 22:17Streaming data UX
- 23:00Key takeaways
related talks
22mServing content on the web: from PHP to RSC—and beyond
42mServer-side Rendering of JavaScript in PHP
46mRethinking Server-Side Rendering in Modern PHP Applications
40mIntegrating React.js into a PHP application
58mUnderstand the Next Phase of Web Development
10mUniversal Apps: Architecture for the Modern Web
04mA few things to know about SSR
48mReact Server Components: A New Way to Build Fast and Interactive Web Apps