Another recent standard that deserves consideration is WebAssembly, as it provides web developers a closer-to-the-metal language with which they can better obfuscate their code.
Sure it can be combined with canvas to obfuscate away website data as a form of DRM, but you could do that already. Heck this is not dissimilar to the concept of a Single-Page WebApp.
At the sametime I don’t think it’ll be all that useful, as the applications I’ve seen mentioned for them are better suited to native applications. Web pages are near-universally I/O bound. Or if websites want to use it for decoding videos, why don’t they just distribute it in a format the browser natively understands? This is not a chore for Odysseus, GNOME Web, and other WebKitGTK based-browsers. As such I predict that WebAssembly will not take off.
In summary, I don’t think WebAssembly is a major threat to end-users or complication to browser engines. As such I won’t be blocking it. But I do think it’s a worthless standard that will not get any serious use.