Question 1

True or false: WebAssembly is a direct replacement for JavaScript and makes JavaScript obsolete.

Accepted Answer

False. WebAssembly is designed to complement JavaScript, not replace it. They often work together, with JS handling UI and WASM handling performance-critical tasks.

Question 2

True or false: WebAssembly code is human-readable text similar to assembly language or JavaScript.

Accepted Answer

False. WebAssembly uses a binary format (.wasm) for efficiency. While a text format (.wat) exists, it's not meant for typical human readability.

Question 3

True or false: WebAssembly can run in the browser and also standalone on servers via WASI.

Accepted Answer

True. WASI (WebAssembly System Interface) allows WebAssembly modules to run outside browsers, enabling server-side and edge computing uses.

Question 4

True or false: WebAssembly supports multiple programming languages like C, C++, Rust, and Go as compile targets.

Accepted Answer

True. Languages with LLVM backends or specific WASM toolchains can compile to WebAssembly, making it language-agnostic for performance.

Question 5

True or false: WebAssembly modules run at near-native speed because they are compiled to a low-level binary format.

Accepted Answer

True. The binary format is designed for fast parsing and execution, with JIT compilation or ahead-of-time compilation enabling performance close to native.

Question 6

True or false: WebAssembly can run on any device that has a JavaScript engine, including toasters and fridges.

Accepted Answer

False. WebAssembly requires a dedicated runtime or engine (like V8, SpiderMonkey, or Wasmtime). Not all JavaScript environments support WASM, especially older devices.

Question 7

True or false: WebAssembly has direct access to the DOM and can manipulate HTML elements without JavaScript.

Accepted Answer

False. WebAssembly cannot access the DOM directly. It must call JavaScript functions to interact with the page, though future proposals may change this.

Question 8

True or false: WebAssembly automatically sandboxes memory access, preventing buffer overflow attacks on the host.

Accepted Answer

True. WebAssembly enforces linear memory isolation with bounds checking, making it safer than native code for sandboxed execution in browsers.

WebAssembly Trivia Questions