JavaScript Engines: How Do They Even?
summary
Explains why modern JavaScript is fast: V8 uses a baseline compiler (Ignition) and an optimizing compiler (Turbofan) with speculative inlined optimizations that produce a measured 100x speedup since 2000. Shows concrete techniques: inline caches and hidden‑class (map) shape checks, deoptimization fallback when assumptions break, and how to inspect bytecode and optimizations with Chrome/Node flags like --print-bytecode to see what the engine actually generates.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:04JavaScript engines importance
- 3:14Engine competition
- 4:40How compilers work
- 6:28Just-in-time compilation in JavaScript engines
- 8:16Baseline and optimizing compilers
- 10:48Compiler pipeline
- 11:09Optimizing addition
- 18:12Optimizing object access
- 23:18Optimization impact
- 24:00Writing optimized code
- 25:10Q&A
related talks
25mJavaScript engines how do they even?
21mDemystifying Javascript Engines
33mJavaScript: The V8 Engine optimization tips (...)
23mJavaScript Engines: The Good Parts™
17mDemystifying (JavaScript) engines
31mJavaScript Compilation Techniques or "Wasn't JavaScript supposed to be slow?"
26mJavaScript VMs 101
22mHigh Performance JS in V8