Running interpreted languages in WebAssembly
summary
Projects build PHP, Python, Ruby runtimes as WebAssembly modules with automation, upstream patches and tests; examples include a CLI/CGI uuid tool and image generation via GD. Binaries range from a 5 MB lean PHP to a fuller ~13 MB PHP image; a referenced Python-linked image format is ~40 MB link one and runtime images drop to <7 MB versus ~1 GB Docker equivalents. ModuAsm (Apache) and a Wasm worker server host Drupal and WordPress and largely work with SQLite.
AI-written summary · about
chapters (9)
- 0:00Introduction to Watson Labs
- 0:45Why use Wasm for languages
- 3:02Language runtimes project
- 5:47Runtimes, libraries, and tools
- 8:46Technical demo and examples
- 15:56Project philosophy and process
- 18:59Community and contributions
- 23:13Future goals and roadmaps
- 27:05Q&A session
related talks
24mHow Small Can You Go? Customizing Interpreted Languages for Wasm Environments
27mDocker and WebAssembly: Better Together
29mWhat is Web Assembly and Why Should you Care?
27mHow WebAssembly is changing the Web and what it means for you
53mWebAssembly
42mWebAssembly beyond the browser
38mWebAssembly beyond the browser
53mWASM Wonders Decoding WebAssembly's Inner Workings