Hacker News new | ask | show | jobs
by exdsq 1602 days ago
If you target a WASM VM you’re not tied into Rust itself which seems appealing from a risk standpoint
2 comments

How so? Your source code is still in Rust so seems like you'd still be tied to it.
The source code is in Rust. But the compilation target is WASM instruction set.
Why does that matter with respect to being less tied to rust? Yes, it compiles to WASM but your engineers still have to write rust in order to make changes to the software. I mean I suppose they could edit the WASM directly since it's technically human readable, but if you're doing that why bother with rust at all?
In terms of platform support - if you target a VM you don’t have to worry about moving from Rust because another language might not support that runtime. Now any language that can work on a WASM VM is okay. Also, if the app isn’t monolithic it means supporting services can be in other languages than Rust too.
ELF, COFF, Mach-O, etc. objects can already be linked together regardless of the compiler producing them.