Web applets are terrible because<p><pre><code>  - The JVM takes forever to spin up  
  - The JVM tries to do too much with tons of class libraries  
  - The JVM is insecure  
  - The JVM is proprietary. While there are open source
    implementations, it is still tethered to Sun and now
    Oracle. They call the shots on the features and have
    sued both Google and Microsoft for implementing their
    own versions.
</code></pre>
Similar arguments can be made against Flash.<p>We shouldn&#x27;t expect WebAssembly to have the same pitfalls, since<p><pre><code>  - WebAssembly does not take forever to spin up  
  - WebAssembly doesn&#x27;t try to do too much. There is no huge
    standard library. For now it doesn&#x27;t even include a GC.  
  - WebAssembly isn&#x27;t insecure. Why would it be? I assume
    applet exploits are a product of the large standard 
    library (more attack vectors) and privilege escalation
    (certain exploits let you break out of its security
    settings to gain control). All of this seems like it&#x27;s
    because web applets are monkeypatched on top of the 
    existing JVM.  
  - WebAssembly isn&#x27;t proprietary.</code></pre>