WebAssembly
summary
Claims that any language can compile to a portable binary and run everywhere, demonstrated with clang→WASM in-browser compiling C/C++ to a ~6KB module and an 18KB GL helper, jq and Mono recompiled to run in the browser, and Python 3.7.4 as WASM engine running and manipulating the DOM. A Sudoku demo mixes OpenCV+TensorFlow with a Rust solver. Runtime ecosystem specifics include WASI for portable syscalls, Wasmtime/Lucet/WAMR runtimes, wapm package installs, and explicit sandboxed file/network permission checks.
AI-written summary · about
chapters (9)
- 0:00Introduction to WebAssembly
- 1:20WebAssembly's impact on tech
- 8:48WebAssembly MVP features
- 13:20Why WebAssembly matters
- 21:39Real-world WebAssembly demos
- 30:56Beyond MVP: WAI and portability
- 41:00WebAssembly package manager
- 48:28Edge computing with WebAssembly
- 51:27Future of WebAssembly
related talks
35mWebAssembly: now web is a new compiler target architecture
01h 42mWebAssembly: Writing Once and Running Everywhere NG
29mWhat is Web Assembly and Why Should you Care?
28mWebAssembly: Of Portability, and Performance
34mWebAssembly: Everywhere All at Once
42mWebAssembly: A New Compilation Target for the Web
35mWebAssembly beyond the browser
44mWebAssembly