THE FUTURE OF WEBASSEMBLY FOR SCALA
summary
Shows practical routes: bytecode-to-wasm via TVM and LLVM-based builds with Scala Native produce runnable modules but hit library and runtime gaps. A proof-of-concept compiles in about eight hours and runs cats‑effect examples, albeit slower; typical wasm runtime overhead is ~2–3× vs native, cold start compares: JVM ~300ms, native ~10ms, wasm ~20–40ms. Major blockers are missing WASI exception handling and GC/callback support, incomplete standard‑library bindings, larger Scala Native wasm (~800KB) vs TVM output (~100–120KB).
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:07What WebAssembly is
- 8:14Building modules in other languages
- 12:25WebAssembly in Scala Native and TVM
- 19:26Performance comparison
- 22:01Scala limitations
- 23:28Future use cases
- 27:02Security and ecosystem
- 28:50Closing remarks
related talks
39mCompiling Scala js to WebAssembly
44mWebAssembly: the browser is now a real virtual machine
22mThe state of WebAssembly
31mThe Future of Write Once, Run Anywhere: From Java to WebAssembly
51mScala.js and WebAssembly, a tale of the dangers of the sea
41mDemystifying WebAssembly, Through the Eyes of A Beginner
17mImplementing and Evaluating a High-Level Language with WasmGC and the Wasm (…)
44mWebAssembly and the Future of the JVM Ecosystem