What Is WebAssembly (Colin Eberhardt)（Z-Library）

【One-Line Pitch】 A concise, historically grounded introduction to WebAssembly: what it is, why JavaScript's limits made it necessary, how modules and runtimes work, and where the technology is heading. Best for web developers, systems-minded programmers, and technical leads evaluating whether Wasm belongs in their stack. 【Book Arc】 - **Opening (~0%–10%)**: Frames the core question—why a new web runtime was needed after 25 years of JavaScript dominance—by tracing JavaScript's rapid creation, its quirks, and the plug-in era (Flash, Silverlight) that ended with the smartphone shift. - **Early (~10%–30%)**: Explains the performance problem in JavaScript execution (interpreters vs. compilers, tiered optimization, download/parse bottlenecks) and introduces asm.js as the precursor that proved a faster embedded runtime was possible; then covers WebAssembly's 2015 working-group formation and rapid browser support. - **Early–Middle (~25%–40%)**: Walks through the static structure of a Wasm module using a small C-to-Wasm example—binary `.wasm` format, textual `.wat` representation, sections, exports, the four numeric types, and linear memory—before turning to execution and the host runtime. - **Middle (~38%–55%)**: Covers host interoperability (exports, imports, shared linear memory, glue code), security (sandboxing, same-origin policy, no built-in I/O), portability, and performance characteristics, including why Wasm reaches peak speed faster than JavaScript. - **Late (~55%+)**: Moves into practical tooling and real-world use cases—CAD, PDF rendering, 3D visualization, image/video editing, games, AR/VR—and looks ahead to non-browser uses such as blockchain runtimes and serverless computing. (Excerpts do not cover the full detail of later chapters.) 【Key Takeaways】 - **WebAssembly exists because JavaScript has structural performance limits** (Opening): the book traces how JavaScript's dynamic nature, HTTP delivery, and parse/compile overhead create a bottleneck that Wasm's compact binary format and fast decoding address. - **asm.js was the crucial stepping stone** (Early): Mozilla's Emscripten and asm.js proved that a more efficient runtime could live inside the JavaScript VM, directly shaping WebAssembly's design. - **Wasm modules are compact, sectioned binaries with a readable textual form** (Early): understanding `.wasm` vs. `.wat`, exports, code sections, and the four numeric types is foundational to grasping both capabilities and constraints. - **Linear memory is the key to complex data exchange** (Middle): since Wasm's type system is numeric-only, strings, arrays, and structs live in linear memory and require glue code for the host to decode them. - **Wasm is not a JavaScript replacement** (Early–Middle): it was designed for close cooperation with JavaScript, loaded via fetch APIs and instantiated through JavaScript, with synchronous call boundaries between the two. - **Security is built into the runtime model** (Middle): sandboxing, same-origin policy, and the absence of built-in I/O mean modules can only interact with the host through imports and exports. - **Wasm targets computationally intensive workloads, not typical websites** (Middle): CAD, games, video editing, AR/VR, and scientific simulation are natural fits; social media, news portals, and form-based CRMs are explicitly not the target. - **Portability beyond the browser is a core design goal** (Middle–Late): the binary format was built for multiple OSes and instruction sets, enabling integration into a wide range of non-browser runtimes. 【Reading Tips】 - **Deep-read the module structure and linear memory sections** (roughly 25%–40%): these are the conceptual backbone; skimming them makes later discussions of tooling and limitations harder to follow. - **Skim the JavaScript history if you already know it**, but don't skip the asm.js discussion—it explains why Wasm looks the way it does. - **Pay attention to the "not a use case" list**: it's a practical filter for deciding whether Wasm is appropriate for your project. - **Treat the tooling example as a walkthrough, not a reference**: the C-to-Wasm compilation via Emscripten is illustrative; the book explicitly avoids deep instruction-set detail. - **Read the future-looking material as directional, not definitive**: the book is from 2020, so blockchain and serverless predictions should be checked against current developments. 【Coverage Limits】 This guide is based on stratified excerpts covering roughly the first half of the book in detail, with later chapters on practical applications and future directions represented only by summary-level material. Specific chapter titles, benchmarks, and later-case-study details are not fully covered in the excerpts.