Resumable JavaScript from Scratch
summary
Builds resumability with plain JavaScript: server-rendered HTML contains inline on:click attributes that name tiny handler modules, a document-level delegated listener lazy-loads the module, caches it, then runs DOM-only logic to remove or add to-do items. Claims tiny pieces download ~40ms modules and aims for target TTI <900ms by avoiding a full client bootstrap. Demonstration is a to-do list that works without requerying data. Notes Qwik as inspiration and lists practical obstacles for Angular: different code-splitting, server hooks and hydration.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:16Initial load performance
- 3:01UX key metrics
- 6:51Angular rendering issues
- 8:14Time to interactive limits
- 13:10Resumability concept
- 15:13Building resumable JS
- 21:34Demo: JS to-do list
- 23:20Resumability in Angular
- 27:39Future possibilities
- 29:01Key takeaways
- 31:10Q&A
related talks
49mQwik: Streaming JavaScript framework
48mResumability in the next generation frontend framework With O(1) loading time
32mWhat's Happening in the JavaScript Ecosystem?
26mMake it Resumable with Qwik
50mQwik: A holly grail of progressive hydration for ultimate speed
22mUnderstanding Resumability
18mResumability in the next generation frontend framework With O1 loading time
30mA Nerdy Guide To The Web Trending Concepts