Unbundling the Future Web Runtime
summary
Predicts native ES modules and WebAssembly landing in 2017 with Edge Insider already shipping parts and dynamic import at stage 3, claims that a modular execution model uses a browser module registry keyed by URL so each module executes once, and shows a working compatibility layer that converts modules to system.register format via SystemJS to run today. Demonstrates concrete build optimizations — inlining, module merging, tree shaking and wasm pruning — and outputs hashed module folders for production.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:02Dynamic Import
- 3:06WebAssembly
- 4:35Build Tools
- 7:06isomorphic modular runtime
- 7:32why modules in the browser
- 7:52benefits of using native module loader
- 8:41optimizations
- 10:24output
- 12:51optimization techniques
- 14:49module graph
- 15:24conclusion
related talks
46mES Modules: The next revolution?
37mApproaching the JavaScript Singularity
14mMore WebAssembly in your JavaScript
14mWebAssembly becoming the biggest platform
44mWebAssembly: the browser is now a real virtual machine
33mWebAssembly's Post-MVP Future
17mA case for Web Assembly
28mPast, Present, and Future