On Responsiven
summary
Claims that UI latency becomes noticeable between 25–100 ms and clearly frustrating past 1 second; demonstrates a frozen canvas image-edit flow versus a responsive version using web workers (worker pool model from Gears cited) and shows off Bespin as an example of richer web tools. Notes modern JS engines are orders of magnitude faster and Chrome’s generational GC reduces long pauses; promises an open memory profiler and reports the web-worker approach actually keeps the UI interactive while heavy work runs.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:15Visual appeal in UX
- 3:22Interface responsiveness in UX
- 5:27Interaction design principles
- 7:37UI latency impact
- 9:19GUI architecture bottleneck
- 11:04Threading evolution in web
- 12:50Web Workers solution
- 13:53Benefits and limitations of Web Workers
- 14:56Performance beyond threading
- 15:39JS engine advancements
- 17:01Garbage collection impact
- 18:03Future of web apps
- 19:06Conclusion & Q&A
related talks
27mSaving the Web, 16ms at a Time
01h 03mSpeed up your Web Application
33mSaving the Web 16 Milliseconds at a Time
25mBetting on the web: Ensuring fine-tuned performance for dynamic web apps
37m"Psychology of Performance"
34mOptimizing Performance in Large-Scale React & Node.js Applications
18mThe need for speed - Single-page apps, Optimistic UIs, Reactivity
39mPerformance Beyond Page Load