OSS Projects
Comparing WASM-first languages (MoonBit, AssemblyScript, Grain) with languages that added a WASM backend (Rust, C/C++, TinyGo, Kotlin/Wasm, Dart, C#, SwiftWasm). Using linear memory vs. Wasm GC, Component Model support, binary size, and maturity as axes, this article explains how to choose a WASM language in 2026.
From WASM runtimes like Wasmtime, Wasmer, WasmEdge, wazero, and WAMR, through WASI/Component Model tooling (WIT, wit-bindgen, cargo-component, jco), upper frameworks (Extism, Spin, wasmCloud, Proxy-Wasm), to GPU implementations (Dawn, wgpu) — a layer-by-layer map of who implements WASM's raw APIs, and how to choose, as of 2026.
A 2026 survey of WebAssembly, WebGL, and WebGPU — plus WASI/Component Model, Web Workers, WebCodecs, and WebNN. Rather than a simple 'JS→WASM' or 'WebGL→WebGPU' replacement, the web platform has converged on a per-layer division of roles. This article maps the current state and offers guidance on technology choice and architecture.
Comparing WASM-first languages (MoonBit, AssemblyScript, Grain) with languages that added a WASM backend (Rust, C/C++, TinyGo, Kotlin/Wasm, Dart, C#, SwiftWasm). Using linear memory vs. Wasm GC, Component Model support, binary size, and maturity as axes, this article explains how to choose a WASM language in 2026.
From WASM runtimes like Wasmtime, Wasmer, WasmEdge, wazero, and WAMR, through WASI/Component Model tooling (WIT, wit-bindgen, cargo-component, jco), upper frameworks (Extism, Spin, wasmCloud, Proxy-Wasm), to GPU implementations (Dawn, wgpu) — a layer-by-layer map of who implements WASM's raw APIs, and how to choose, as of 2026.
A 2026 survey of WebAssembly, WebGL, and WebGPU — plus WASI/Component Model, Web Workers, WebCodecs, and WebNN. Rather than a simple 'JS→WASM' or 'WebGL→WebGPU' replacement, the web platform has converged on a per-layer division of roles. This article maps the current state and offers guidance on technology choice and architecture.
