asmble

> "JVM requires almost all your stack to be rewritten for it." This applies no more to the JVM than to Wasmer. There exists WASM to JVM bytecode transpilers [0]. [0] - https://github.com/cretz/asmble

> At best you'll get a Rust'ish WASM, Python'ish WASM, PHP'ish WASM, etc I agree with the latter two due to runtime uniqueness, but not so sure it holds for Rust. Since C FFI has become the defacto WASM standard (with higher level interop coming as the article suggests), some low-overhead langs like Rust can be reasonably used elsewhere via WASM (though in most cases, you'd use them as native libs if you had the option). Essentially it comes down to two things: How much of the WASM conformance is language-specific at compile time (e.g. for Go, stack resumption is manually built causing bloated WASM), and how much overhead does WASM interop cause at runtime (e.g. can it use the string interface type instead of converting to what it considers a string in local memory and what are the tradeoffs of each approach). If your language has a low W