I can kinda see what they mean (albeit it's somewhat of a stretch). WASM "embeds" modules within the JS runtime, in a similar way that traditional FFI "embeds"

I can kinda see what they mean (albeit it's somewhat of a stretch). WASM "embeds" modules within the JS runtime, in a similar way that traditional FFI "embeds" native bindings compiled separately & externally. It's still quite different insofar as the VM is a part of the runtime, but there are vague parallels. For me though, the practical problems related to runtime env that one encounters with traditional ffi bindings calling dynamically linked native libraries are rarely present with a WASM library, as the support within the runtime is explicit (the only real exception here is architecture, which is always an issue regardless).