That is one of the appeals of rust for me. I want one language that I can flip from

- Native

- Web

- Distributed

- ML

- Service

programming without having to switch toolchains. Rust is surprisingly close to achieving this.

This is indeed an interesting point. I've worked with C/C++ and every single project or experience had some peculiarity: the platform, the compiler, some version limitation, etc.

For that I see it as a matter of tooling more than the language design: wasm is nicely integrated into cargo and is maintained far better than other choices. You can also compile C/C++ to WASM if you want (and the language semantics definitely allows for it, since it doesn't have a garbage collector), but you just really don't want to deal with CMake while doing so.

garbage collector isn't a limiting factor for wasm.

my main issue with wasm is no standard interopt for primitive types. thankfully some sort of FFI is in the works from my understanding.

In theory yes, but in practice managed languages need native GC support because garbage collectors in WASM code are quite slow. There's a proposal in the works: https://github.com/WebAssembly/gc/blob/main/proposals/gc/Ove...