Multicore JavaScript: Past, Present and Future
summary
JavaScript today already has the basics—promises, async/await, Workers, SharedArrayBuffer and Atomics—but common code still serializes large objects, loses identity, and rarely uses Atomics in practice; multi-core phones with eight cores expose that performance is often left on the table. Proposals aim at real fixes: module blocks to transfer code ergononically, shared disjoint heaps for fast transferable heaps, and structs for safe concurrent objects; WebAssembly threading and vasm GC promise tighter integration and higher-performance multi‑core use.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:14JavaScript’s origins and design
- 5:01Concurrency models compared
- 9:34Web-like vs thread-like
- 12:24Trade-offs of models
- 19:12TC39’s multi-core dilemma
- 20:37Phase one building blocks
- 22:26Phase two ergonomics gaps
- 25:15Module blocks and heaps
- 27:47Thread pain points and Structs
- 29:33Future experiments and tools
- 31:19Conclusion
related talks
33mAsync patterns to scale your multicore JavaScript elegantly.
30mThe future of Javascript
47mECMAScript: latest and upcoming features
24mShared Memory & Parallel Programming with JavaScript
25mECMAScript of the Future: ES2017 & Beyond
40mKeep Betting On JavaScript
40mJavascript and the Polyglot Web
33mParallelism experiments in JavaScript