|
|
|
|
|
|
by emerongi
2646 days ago
|
|
|
I've now found a blog post[0], which seems to outline two main reasons for WASM over JVM on the web: 1. WASM is an open standard 2. WASM spec is smaller, so it's easier to integrate into the Javascript VM, which itself brings many benefits Since WASM wins on the web, I guess it makes sense for developers to want to develop one version of their code for both the web as well as native environments. Thus, WASM -> Native seems to totally make sense. [0] https://words.steveklabnik.com/is-webassembly-the-return-of-... |
|
|
So is the web, but that didn't stop anyone from extending it in incompatible ways and all implementations being subtly different enough that you still have care about which one you're running on and, oh yeah, it's also becoming dominated by a single player who steers the whole thing pretty much wherever they want it.