But it helps when running untrusted code, or code that has to be separated (like what you would use containers for)

You’re missing the point. It’s about containerization.

To quote a Docker cofounder:

> If WASM+WASI existed in 2008, we wouldn't have needed to created Docker. That's how important it is. Webassembly on the server is the future of computing. A standardized system interface was the missing link. Let's hope WASI is up to the task!

[1] https://twitter.com/solomonstre/status/1111004913222324225?s...

I’m not. You’re making a different argument for why webassembly is relevant than the post to which I originally responded.

You DO need webassembly to run C++ on the server AND client(browser) side.

(unless you want to use some hacky c++ to js transpiler)

Can you provide an example of a situation where it would make sense for both client and server to use the same build?

Typically client and server play different roles and require different builds anyway.

The point isn’t to run client code in the server and server code on the client.

The point is to allow JavaScript to be able to use excellent C++/Rust code in a sandboxed environment when it makes sense.

Embedding SQLite is a perfect example.

> The point is to allow JavaScript to be able to use excellent C++/Rust code in a sandboxed environment when it makes sense.

That seems useful for the client side but you don’t need webassembly to do that on the server-side. E.g. https://github.com/mapbox/node-sqlite3