WebAssembly - the Final Frontier
summary
Claim: WebAssembly runs compiled C/C++ in browsers at about 1.2–1.3× native speed with much more predictable performance than JavaScript. Tooling uses Emscripten + LLVM toolchain to recompile existing engines, games and libraries, and demos include Unity recompiled to wasm, a Mandelbrot/zoom demo and a webcam shader showing roughly 10× speedup over JS for pixel filters. Browser support is Chrome Firefox Safari (Edge lagging) and instantiation uses fetch → WebAssembly.instantiate.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:10What is WebAssembly
- 1:36JavaScript to native plugins
- 4:52WebAssembly birth and browsers
- 5:54Browsers bet on WebAssembly
- 7:19WebAssembly vs JavaScript
- 9:06WebAssembly with Unity
- 10:13Performance vs JavaScript
- 11:38WebAssembly speed and predictability
- 13:27WebAssembly syntax
- 15:53Running WebAssembly in JS
- 17:41WebAssembly modules
- 18:49WebAssembly Fiddle
- 19:10Hand-written vs compiled
- 20:34C/C++ to WebAssembly
- 22:02C/C++ functions to JS
- 23:05WebAssembly data types
- 24:34Pitfalls and performance considerations
- 26:07WebAssembly future
- 27:09WebAssembly shaders demo
- 28:58Q&A
related talks
16mWhy WebAssembly
35mWebAssembly: now web is a new compiler target architecture
42mWebAssembly? Web and Assembler? WTF!
53mWebAssembly – To the browser and beyond!
44mWebAssembly
42mWebAssembly: A New Compilation Target for the Web
52mWebAssembly: Taking Your C++ and Going Places
25mFast future with WebAssembly