3 ms·
> Java and its JVM WASM shares more ideas with CIL than the JVM, especially when we have a look at the WASM proposals in progress. CIL and Pascal P-Code in con
by Rochus 5y ago
> Java and its JVM
WASM shares more ideas with CIL than the JVM, especially when we have a look at the WASM proposals in progress. CIL and Pascal P-Code in contrast to JVM support e.g. value objects which supports applications with less dynamic memory management; JVM requires a dynamic allocation for each fly speck and thus powerful compacting collectors to cope with it. In WASM the memory management strategy is up to the application.
> The fact that browsers support WebAssembly natively
I was referring to the "elsewhere" case, where WASM seems to flourish, not the browser. And the social factor is definitely important, but I'm more interested what WASM is supposed to deliver we don't already have on a technical level.
- hkalbasi 5y ago> WASM shares more ideas with CIL than the JVM [..] In WASM the memory management strategy is up to the application. That level of difference doesn't matter. The point is that WASM is a portable and sandboxed target (like JVM) which is (or will be) faster, more secure (e.g. capability based security in WASI) and with more language support (strictly more when optional GC becomes a thing) and other differences are implementation details.
- pjmlp 5y ago"Everything Old is New Again: Binary Security of WebAssembly" https://www.usenix.org/conference/usenixsecurity20/presentation/lehmann https://www.usenix.org/conference/usenixsecurity20/presentat... "WebAssembly Troubles" http://troubles.md/wasm-is-not-a-stack-machine/ http://troubles.md/wasm-is-not-a-stack-machine/