<story><title>WebAssembly for the Java Geek</title><url>https://www.javaadvent.com/2022/12/webassembly-for-the-java-geek.html</url></story><parent_chain></parent_chain><comment><author>kaba0</author><text>While it is an informative article, I fail to be convinced that wasm is somehow superior (even for its current role).&lt;p&gt;Validation is faster due to it being structured, but stackmaps make it fast for class files as well. It is lower level, but is that really a good thing? It is quite trivial to just assign a huge ‘long’ array to some jvm byte code for the same result, and while I will look at the linked GC proposal, because haven’t been kept up-to-date on that, I think having a good GC is the single most important thing, as that is much harder to do than just providing a linear array. Which will in turn decimate the implementations (or at least mark a toy vs prod ready divide).&lt;p&gt;Also, will that structured nature not make it a less than great compilation target? This means that certain, more niche languages will have to use ugly (and slow) hacks to get implemented. And it being lowish level it is much harder to optimize it well (in that you express the exact semantics).</text></comment>
<story><title>WebAssembly for the Java Geek</title><url>https://www.javaadvent.com/2022/12/webassembly-for-the-java-geek.html</url></story><parent_chain></parent_chain><comment><author>bullen</author><text>I&amp;#x27;m considering building a Java compatible VM that only has static memory allocation to avoid GC.&lt;p&gt;Why hasn&amp;#x27;t this been done by anyone yet?&lt;p&gt;Also confused why this does not have a binary windows release yet: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;bytecodealliance&amp;#x2F;wasm-micro-runtime&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;bytecodealliance&amp;#x2F;wasm-micro-runtime&lt;/a&gt;&lt;p&gt;Edit: Epsilon is not the answer here you can stop mentioning that.</text></comment>