The post-Jamstack world and the rise of Hybrid Frameworks
summary
Claims that the web is “in jeopardy” get backed by specifics: an example pushes first meaningful paint from 14s to 2.9s simply by removing third‑party scripts; static generation is static by default in Nextjs but pages can convert to server‑rendered or edge serverless functions to keep features without killing perf; field analytics report real device metrics rather than synthetic Lighthouse; deployment and CDN automation already power more than 11 of the top 100 and 75 of the Alexa top 1000.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:40Web is in jeopardy
- 2:16What is the web
- 3:03The web is mobile
- 4:04Average device for the web
- 5:32Three major cohorts of the web
- 7:04Building for the tail
- 8:05Performance matters
- 8:44The web in jeopardy
- 10:55Nexjs
- 15:13Feedback loop
- 15:39Focus on reality
- 15:59Oversimplified model
- 18:54Performance
- 19:10Scroll performance
- 19:33Web fonts
- 21:33The solution
- 22:20A practical path
- 25:38Analytics
- 28:50Caching
- 29:48Nextjs
- 30:24Outro
related talks
27mThe Post Jamstack World & the Rise of Hybrid Frameworks
44mJAMstack: Web Apps at Ludicrous Speed
19mA Skeptic’s Intro To The Jamstack
21mDante’s Inferno of Fullstack Development (A Brief History)
42mTo Truly Understand Jamstack, Forget the JAM
50mComposable decoupled frontends: the Jamstack and beyond
30mRise of the Jamstack — Mathias Biilmann
12mCMS and JAMstack: A Tale of Innovation in Web Development