The state of WebAssembly
summary
Argues WebAssembly gives near-native performance for number‑heavy code, with smaller binaries and streaming compilation that reduces load time; demonstrates toolchains: AssemblyScript and Emscripten for TypeScript/C/C++, and Rust via cargo producing wasm modules; cautions that crossing the JS–Wasm boundary hurts throughput and that only numeric types are cheap to share because of the shared linear memory model; previews proposals (interface types, SIMD, WASI, GC) and when to pick Wasm versus plain JavaScript.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:20Languages are built for a purpose. Choose & Use them wisely...
- 0:40The state of WebAssembly
- 2:13JavaScript is weird
- 5:07So what is the problem?
- 8:44What WebAssembly provides?
- 9:44Linear Memory Model
- 10:38Shared Array Buffer
- 14:06Streaming compilation
- 14:37What languages can do wasm?
- 18:06Interface types
- 19:02Single Instruction Multiple Data
- 20:43WASI WebAssembly System Interface
