Loopage
summary
Argues that single-threaded event loops beat threads for reliability and efficiency, citing node.js implements a non‑blocking event loop and showing how callbacks avoid mutual‑exclusion races and deadlocks. Demonstrates hazards of threads with a tiny example where interleaved writes make an array vanish — race conditions delete data. Notes missing JavaScript tail calls, recommends iteration via setTimeout(0) or workers for long tasks, praises server‑side JS + yui3 and warns HTML5 increases XSS risk.
AI-written summary · about
chapters (42)
- 0:00Introduction
- 1:32Loops
- 2:48Loop primitives
- 4:25Event loop
- 6:21Code breaking
- 8:02The first compiler
- 9:35Open source
- 10:55Fortran
- 11:22Readblocking
- 11:59Timesharing
- 12:56IO
- 14:14Text editors
- 14:37Macintosh
- 15:43HyperCard
- 17:25JavaScript
- 19:34Threading
- 20:27JavaScript programs
- 22:38Mutual exclusion
- 24:29deadlock
- 25:45cons of threading
- 27:36pros and cons
- 28:55iteration and workers
- 30:09remote procedure call
- 32:11security
- 32:40crosssite scripting
- 33:28misinterpretation of HTML
- 34:01page templates
- 34:48serverside JavaScript
- 35:07netscape
- 35:56nojs
- 39:04Protocols
- 39:50HTTP
- 40:25Database
- 42:16Elco Server
- 43:05Stupid Argument
- 44:25Grace Hopper
- 45:23Show of Hands
- 45:58The Only Web Standard
- 49:12Demo
- 50:32Continuation Passing
- 54:16HTML5 Crosssite scripting hazard
- 57:28Microsoft
related talks
31mI Play the JavaScript
41mOrchestrating the Web Audio API
42mBeating Threads - live coding with real time
29m25 years of embracing the weird
27mBreaking Down JavaScript Complexities With Generative Art
01h 05mWhy You Should Write Code That You Should Never Write
01h 13mWeb: The good parts
21mPeople, The Good Parts