Myles Borins - Keynote
summary
History of JavaScript standards and how Node actually inherits V8 lead to concrete fixes and tradeoffs: Node updates V8 mid-release to get ES features; util.promisify and low‑level promise optimizations reduce allocations and in some measurements async/await outperform callbacks; post‑mortem tooling breaks because promises change unwinding; TC39 needs two engine implementations and about eight months minimum to standardize a feature; an ABI‑stable layer, N‑API, ships experimental in Node 8 to let native modules survive V8 changes.
AI-written summary · about
chapters (8)
- 0:00Start
- 6:24THE V8 ENGINE
- 9:07WE NEEDED BETTER PROMISE SUPPORT
- 10:48BUT WE DON'T HAVE A BETTER SOLUTION
- 12:30REGARDING CALLBACKS
- 21:14ONE STAGE PER MEETING
- 25:41JAVASCRIPT'S MONSTER
- 26:27USED BY NODE AND NATIVE MODULE AUTHORS








