WebAssembly Fundamentals

WebAssembly (Wasm) is a compact binary instruction format that runs inside web browsers and other host environments at near-native speed. Developers write code in languages such as C, C++, Rust, or Go, compile it to a WebAssembly module, and load that module alongside ordinary JavaScript. It exists to run computation-heavy tasks, such as image processing, physics simulation, or a ported native application, in places JavaScript alone runs too slowly.

itWeb development

Don't Panic - WebAssembly Fundamentals

WebAssembly, usually shortened to Wasm, is a compact binary format that runs compiled code inside a browser at close to native speed. It did not turn up to replace JavaScript. It sits next to it, as a sandboxed guest that JavaScript loads, sets up, and calls into whenever the job is too heavy for JavaScript to do comfortably alone.

Before Wasm, that job belonged to asm.js: a strict, typeable subset of JavaScript that browsers could optimize aggressively, invented specifically to prove a browser could run cross-compiled C code fast. It worked. It was also still JavaScript text, which a browser had to parse before running, which is the slow part this format exists to skip.

Here is the shape everything else hangs off. A compiler turns C, C++, Rust, or Go into a module, which is compiled bytecode and nothing more. Instantiating that module pairs it with its own memory and its own table of function references, producing an instance that can actually run. One module, instantiated twice, gives you two instances that share nothing. And almost everything expensive or unsafe in this course traces back to one fact: a module only exchanges plain numbers with its host for free. A string has to be copied into its memory by hand. An object generally can't cross at all without help.

The surprise, if you have heard of WebAssembly secondhand, is where the speed actually comes from. Figma's engineers reported a 3x load-time win moving from asm.js to Wasm, and the honest reason was parsing roughly 20x faster and the browser caching the translated native code, not faster arithmetic. If your mental model is "Wasm makes my loops run faster," that's the wrong lever half the time; the real one is how fast the thing loads and starts.

The other outdated bit, if what you know is a few years stale: "Wasm is for C, C++, and Rust" stopped being the whole truth in 2023, when Chrome shipped WasmGC, letting the host's own garbage collector manage memory for languages like Java and Kotlin. Before that, those compilers had to bring their own collector, badly.

For the honest mechanics of module, instance, memory, and the boundary, read the intro. For a fast conceptual map with the compile-versus-instantiate distinction laid out side by side, the slides. For the actual commands, wasmtime, wat2wasm, emcc, and what each does, the cheatsheet and the practice reference. None of it requires a pager. Most of it does require remembering that the boundary is where the bodies are buried.

Don't Panic - WebAssembly Fundamentals

Relevant careers