3 ms·
Along with the other responses, the JVM imposes its own object model on any language implemented on top of it. WebAssembly does not, so it is vastly simpler and
by Rusky 9y ago
Along with the other responses, the JVM imposes its own object model on any language implemented on top of it. WebAssembly does not, so it is vastly simpler and more flexible.
For example, you had to rewrite your apps to run as Java applets. You do not have to rewrite things to run on WebAssembly- all the existing C, C++, etc. code is compatible, up to the platform API.
- dikaiosune 9y agoThis is of course assuming that the WASM GC proposal doesn't require a specific object model to get host GC interop.
- Rusky 9y agoSo far it doesn't look like it will: https://github.com/WebAssembly/gc/blob/master/proposals/gc/Overview.md https://github.com/WebAssembly/gc/blob/master/proposals/gc/O... But either way, I'd still take "use this object model for host GC interop" over "use this object model or leave the platform."