Back to the Vueture: Stuck in the Event Loop
summary
Builds a tiny DeLorean UI to time-travel a clock and experiments with $nextTick, Promises, requestAnimationFrame, setImmediate/setTimeout and DevTools paint flashing to observe render boundaries. Shows that $nextTick callbacks run in the flush queue, that flushes coalesce per component so multiple nextTicks can get merged, and that nextTick runs after the next DOM update but not necessarily after paint. Finds setImmediate or nested RAF forces separate renders, uploads a logger to reproduce the ordering.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:52music = coding = confusing
- 3:11Temporal experiment
- 4:28The UI
- 5:28Back to $nextTick
- 13:58Back to the Source Code
- 20:28What we can extrapolate
- 24:38Ways to mitigate trash brain
- 28:29nextTick
related talks
34mJavaScript's Secret Life Between the Ticks
15mJavascript Flow Control
21mFurther Adventures of the Event Loop
31mThe Event Loop Fairytale
12mnextTick Down to Business
44mLeveraging the Event Loop for Blazing-Fast Apps!
41mThe Eventloop in JavaScript - How does it work?
27mWhat the heck is the event loop anyway?