One of Doppio&#x27;s explicit goals was to leverage existing resources in the browser to bring conventional programming languages to the web on top of JavaScript. Using WebAssembly would prevent Doppio from using the browser&#x27;s garbage collector; we would have to write our own. It would also prevent Doppio from mapping JVM objects onto JavaScript objects.<p>The WebAssembly standard is constantly evolving, and now contains some ambiguous statements regarding the ability to take advantage of the browser&#x27;s GC [0]. Considering WebAssembly&#x27;s current focus on C&#x2F;C++ code, I do not believe this will come to fruition anytime soon. If it does, I do not see how it would noticeably improve Doppio&#x27;s current performance, which is bottlenecked primarily by its interpreter. A contributor is working on a JIT right now to make execution faster [1].<p>Hope that clarifies!<p>[0] <a href="https:&#x2F;&#x2F;github.com&#x2F;WebAssembly&#x2F;design&#x2F;blob&#x2F;master&#x2F;GC.md" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;WebAssembly&#x2F;design&#x2F;blob&#x2F;master&#x2F;GC.md</a><p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;plasma-umass&#x2F;doppio&#x2F;pull&#x2F;443" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;plasma-umass&#x2F;doppio&#x2F;pull&#x2F;443</a>