Java and WebAssembly
summary
Demonstrations show zero‑install Java running in the browser: a full SnapCode IDE and playgrounds compile and run client‑side with a ~15 MB runtime and ~1 s launch. Toolchains tested include CheerpJ (full JVM in browser), TeaVM (AOT compile with aggressive dead‑code elimination) and GraalWasm/Graal WebImage. Server use is possible but brittle: calling Wasm from Java (Chickory, Graal) or compiling Java to Wasm for Fermion/Akamai works, but requires manual glue for pointers/strings, 20–30 s transpile iterations, and WASI/version compatibility fixes.
AI-written summary · about
chapters (12)
- 0:00Java and WebAssembly intro
- 1:03What is WebAssembly
- 3:31Why WebAssembly over Java
- 8:01WebAssembly tooling overview
- 10:10Java in browser with WASM tools
- 15:17Benefits and challenges
- 20:47SnapCode IDE demo
- 26:03Java calling WASM server
- 28:54Calling WASM from Java demo
- 35:42Compiling Java to WASM
- 39:02Summary and future
- 41:49Q&A
related talks
31mThe Future of Write Once, Run Anywhere: From Java to WebAssembly
28mWeb Assembly for Java Developers
44mWebAssembly and the Future of the JVM Ecosystem
50mWeb Assembly
53mWebAssembly
32mWebAssembly: birth of a virtual ISA
50mWebAssembly and the Future of the JVM Ecosystem
30mSupercharge Your Java Apps with WebAssembly