You can actually look at what wasm is currently being used for beyond its connection to the JS ecosystem. It's a really exciting space. For example, there's a

You can actually look at what wasm is currently being used for beyond its connection to the JS ecosystem. It's a really exciting space. For example, there's a project called Oak (https://github.com/project-oak/oak https://github.com/project-oak/oak) that basically allows your private information to be processed by servers without revealing them to the servers. It uses a bunch of technologies and wasm is a center piece for allowing a safe form of code execution. For another example, check out Mozilla's post about securing Firefox with wasm (https://hacks.mozilla.org/2020/02/securing-firefox-with-webassembly/ https://hacks.mozilla.org/2020/02/securing-firefox-with-weba...). Again, here we compile C/C++ code with unknown memory safety properties into wasm and then compile that to native code. The benefit of doing it over directly compiling C/C++ to native code is that any memory safety issue is strictly sandboxed to be within the wasm module. You can't have one library's memory safety bug trampling over another library's memory.