WebAssembly started as a way to run C++ in the browser. Today it's reshaping what "web app" means — and most of the change has been so gradual that many developers haven't noticed how far it's gone.

The Short Version of What WASM Is

WebAssembly is a binary instruction format with a stack-based virtual machine. Browsers compile it to machine code ahead of time, so execution is close to native speed. Crucially, it's:

Language-agnostic — C, C++, Rust, Go, Zig, and even Python or C# compile to it
Sandboxed — it runs in the same security containment as JavaScript
Interoperable — it calls into JavaScript and browser APIs seamlessly

It's not a JavaScript replacement. It's a second compile target that handles what JavaScript was never designed for.

Desktop-Class Apps in the Browser

The flagship examples are everywhere now:

Figma — its design engine is C++ compiled to WASM; the app famously became near-instant to load after the port
Photoshop on the web — the full desktop codebase running in the browser
Google Earth — a native C++ engine delivered as a web page
AutoCAD — 30 years of desktop code running without a plugin

These aren't demos. They're the same battle-tested codebases that ran on desktop, delivered with a URL instead of an installer.

New Languages Enter the Ecosystem

Before WASM, the browser spoke one language. Now:

Rust has become the darling of web tooling — SWC (a Babel alternative), Turbopack, and Ruff (a Python linter) are all Rust compiled to WASM or native
SQLite runs in the browser via WASM, enabling offline-first apps with real SQL
FFmpeg compiles to WASM, meaning full video transcoding client-side
libvips, zlib, and countless C libraries now power in-browser file tools

The consequence: a developer who writes systems code can ship to the largest platform in the world — the browser — with minimal changes.

The Tooling Has Caught Up

Early WASM required manual memory plumbing. The ecosystem now includes:

WASI — a system interface making WASM portable outside browsers too
wasm-bindgen / wasm-pack — first-class Rust-to-web tooling
Component Model — a standard for composing WASM modules across languages
Emscripten — mature C/C++ toolchain powering ports of enormous codebases

And critically, the platform grew alongside the tooling: threads via SharedArrayBuffer, SIMD instructions, and bulk memory operations all landed in the spec.

What This Means for Everyday Apps

You don't need to port Photoshop to benefit. The practical wins show up in ordinary apps:

File tools that never upload — compression, conversion, and PDF processing running locally
Games and simulations — physics and rendering loops that JavaScript can't sustain
Cryptographic operations — constant-time implementations from vetted C libraries
Offline-first software — once the WASM module is cached, the app works without a network

The Trajectory

The pattern to watch: capabilities move from "impossible in a browser" to "a library you import." Video editing, 3D modeling, local AI inference — each starts as a research project and ends as an npm package.

The browser is becoming the most portable runtime ever created. WebAssembly is the reason.

Command Palette