JavaScript in WebAssembly? Why and How
summary
Claims JavaScript can run inside WebAssembly as a self-contained microservice runtime rather than a browser plugin. Uses QuickJS compiled to WebAssembly plus Rust host APIs to implement networking (non-blocking sockets), ES6/CommonJS support via Rollup, and TensorFlow inference bindings. Demos include React 18 streaming SSR and an image-recognition “hot dog” model and they work. Tradeoffs: QuickJS is roughly 3x slower than V8 but a WebAssembly image is ~10 MB versus ~1 GB for V8 in a container, and heavy paths move to Rust to regain performance.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:23Javascript in Webassembly
- 1:07When Web Assembly Was Invented
- 5:45Smart Contracts
- 18:03A Rust Api That Allows Rust Developers To Write Javascript Apis
- 21:38Fetch Api
- 22:22Extension That Interact with Tensorflow
- 28:17Quickjs versus V8
- 32:44Spider Monkey
related talks
30mRunning JavaScript, Python, and Ruby in WebAssembly
30mWhy Should You Consider JavaScript on WebAssembly?
22mWebAssembly beyond the browser
01h 42mWebAssembly: Writing Once and Running Everywhere NG
20mWeb Assembly: The Future of JS and a Multi-Language Web
16mWhy WebAssembly
30mWhy Should You Consider JavaScript on WebAssembly?
34mPractical Polyglot WebAssembly
