Would you please clarify what problems are you referring at? Some Java-in-the-browser problems that seem orthogonal to the minutia of the language running in the browser:<p>* Language-based security model. Hopefully not an issue, browsers have been pretty good at sticking with same origin policy and not trying to mix code from different providers in the same address space.<p>* sun.misc.unsafe. As long as the APIs available to WebAssembly are the same as the Javascript APIs, not an issue.<p>* Slow startup times. For a decent loader &#x2F; JIT infrastructure this is not an issue regardless of the language. In other words, an implementation detail and not a systemic issue.<p>* AWT &#x2F; Java2D. There is a chance non-DOM widget toolkits will make a comeback, but that&#x27;s less of a WebAssembly issue and more of a Canvas issue. Canvas has been around for a while, but most people still use the DOM.