WebAssembly and the Future of the JVM Ecosystem
summary
WebAssembly runs inside the JVM today: QuickJs4J packs QuickJS as a single ~800 KB jar used by Microcks for JavaScript dispatchers; SQLite4J runs SQLite compiled to Wasm; protoc is compiled to Wasm and translated to bytecode producing a 1.3 MB library that cuts ~90 MB of cross‑platform binaries. A JVM Wasm runtime (Chicory → Endive) translates Wasm to Java bytecode, hits a JVM method‑size limit (≈8 KB), and optionally uses Cranelift via Panama to emit native code for comparable performance.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:50WebAssembly basics
- 8:14Why WebAssembly on JVM
- 14:43Running JavaScript on JVM
- 23:12Policy engine with OPA
- 27:48Protobuf compilation with WASM
- 32:28Code highlighting with tree-sitter
- 37:46Other WebAssembly use cases
- 38:08Chicory deep dive
- 44:07Cranelift on JVM
- 46:36Endive announcement
- 48:03Future of WebAssembly
related talks
44mWebAssembly and the Future of the JVM Ecosystem
31mThe Future of Write Once, Run Anywhere: From Java to WebAssembly
28mWeb Assembly for Java Developers
43mJava and WebAssembly
28mJavy: Creating a toolchain for running JavaScript on WebAssembly
53mWebAssembly
50mWeb Assembly
38mWebAssembly for the backend