WebAssembly Development: Real Pitfalls and Examples
summary
Covers using WebAssembly for commercial browser development, describing tools and techniques used to port a large C++ application into the browser. Explains how to pass objects between JavaScript and Wasm, practical problems encountered and their solutions, what Wasm can and cannot do, how to view C++ code in the browser debugger, and performance comparisons between Wasm and JavaScript.
AI-written summary · about
chapters (38)
- 0:00WebAssembly intro
- 1:22P2P video delivery
- 3:11Ditching plugins
- 4:56Porting to browser
- 5:16Dependencies & architecture
- 7:01Browser sandbox limits
- 8:26WebAssembly output files
- 9:30Bundling issues
- 10:32Single file optimization
- 11:36callMain infinite loops
- 14:08C++ JS binding
- 15:56Emscripten binding
- 19:54Build errors
- 22:06Memory allocation
- 24:14Dependency injection
- 25:41Async memory leaks
- 27:47Memory copy optimization
- 29:12Hosting limits Russia
- 30:14Porting benefits
- 31:42Suitability & languages
- 33:10Real-world examples
- 36:44Client monetization
- 38:32Node.js WebAssembly
- 39:59Large projects
- 41:47Team recommendations
- 44:17Debugging workflow
- 45:43Source maps
- 47:12Debug limits future
- 48:17Performance measurements
- 49:20JS performance
- 50:44Error dashboard
- 51:46Debugging docs
- 52:09WebAssembly security
- 53:17Threads & multithreading
- 54:19Unity data exchange
- 55:44Cross-browser compat
- 56:27WebAssembly networking
- 57:31App size optimization
related talks
52mWebAssembly vs JavaScript
52mWebAssembly: Taking Your C++ and Going Places
35mWebAssembly: now web is a new compiler target architecture
26mWebAssembly as cross-platform architecture?!
35mWebAssembly as Cross-Platform Architecture
25mWebAssembly: Binary in Plain English
21mHelp me WebAssembly, you're my only hope!
42mWebAssembly? Web and Assembler? WTF!