> If I'm reading the EME spec correctly, then EME plugins can be installable by the end user in the same way that Netscape plugins are today.
They can be, but neither the browser vendors nor the content providers have to allow them to be, and the EME spec doesn't standardise any equivalent of NPAPI that standardises the interface between them and the browser. Browser vendors can (and it appears will in some cases, e.g. Internet Explorer) only support EME modules supplied by them and compiled into the browser binary; this is anticipated by the spec.
Google's DRM plugin is currently available for both Firefox and Chrome through the standard Netscape plugin API, but is not bundled with either browser.
If I'm reading the EME spec correctly, then EME plugins can be installable by the end user in the same way that Netscape plugins are today. Assuming the browser chooses to implement the plugin system, both Firefox and Chromium ought to be able to use DRM plugins from the system. Any non-proprietary DRM solution would not be able to stop even casual piracy. The casual pirate will search for [download netflix movie], click the first link, install a browser extension, and get a one-step piracy button right in their browser.That's what content companies are terrified of, and any DRM system that can't stop this sort of pirate will not be accepted.
We have not seen a victory for free formats in music. The majority of music online is still distributed wrapped in layers of digital restrictions (e.g. Pandora, Spotify) or in patent-encumbered formats (e.g. iTunes, Google Play, Amazon).