WebAssembly and the Web in TypeScript
summary
Describes using AssemblyScript plus a small loader and an npx project generator to compile TypeScript to WebAssembly, load it via fetch, and wire up imports/exports with JavaScript. Shows a pixel renderer that writes into shared linear memory and uses ImageData to draw to canvas (around 360 FPS on 500×500 and a 100k-sprite benchmark). Covers concrete limitations: no closures or full GC (until recent changes), manual memory and string/object transport, and the need to rework large existing TypeScript apps to fit WASM constraints.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:33What is WebAssembly
- 4:45WebAssembly benefits
- 7:12Getting started with AssemblyScript
- 11:54AssemblyScript project structure
- 13:22AssemblyScript types and memory
- 16:54Memory and rendering
- 19:51WebAssembly in practice
- 23:00Example: rabbit animation
- 27:35AssemblyScript limitations
- 30:24When to use WebAssembly
- 33:15AssemblyScript pitfalls
- 36:11Q&A
related talks
29mAssemblyScript: TypeScript on Steroids Thanks to WebAssembly?
22mThe state of WebAssembly
44mWebAssembly: the browser is now a real virtual machine
32mWebAssembly for Front End Devs
25mWebAssembly: Binary in Plain English
27mHow WebAssembly is changing the Web and what it means for you
16mWhy WebAssembly
52mWebAssembly vs JavaScript