Yes, and he wouldn't endorse WebAssembly either (which is just a different, and even worse avenue towards DRM).
Whereas EME is more, trust this native code please, and give it all the access it asks for?
WA makes sense as what it is intended to do: give a memory efficient alternative to JavaScript in circumstances that warrant it.
If this has to happen, let's make it work in a way that doesn't let the stupidest ideas survive. Using WA still requires JS to interact with the user. Which is far better than the monstrosities that JS is being forced to perform at the moment.
Some simple, relatively sane things that WA can do, but JS is a bad choice for:
* Client-side encryption/decryption
* Socket management