No it isn't. Example: Netflix will ask for Widevine DRM provider (and exactly that provider!). It's a proprietary closed licensed platform and your system needs to have their binary blob licensed and compiled for it. If you don't have it and didn't pay for it, you won't be able to decrypt the DRM. Of course to get your DRM blob to run, you'll also have to prove and promise to the DRM provider that you have locked out the user from their own device so they won't be able to accidentally record the video they watch.
It's impossible to make your own open implementation or compete with existing players because they built the fact that you need to negotiate with them for licensing into the standard.
I don't think that's true. It's still just a plugin so as long as implement something like the Gecko Media Plugin / CDM, you should be good, or at least no worse off than before where you had to support the Flash or Silverlight plugin.
Is there a better way to make strong DRM?
This DRM implementation would add this suffix: "and any number of third parties have chosen to allow my browser to use their proprietary decryption modules." This is the opposite of the Open Web and therefore a threat to user freedom and the integrity of the Web as a whole.
These steps are not technical but they are very significant.
Consider how you would provide this plugin to your users as the author of a new browser? You have to ask the plugin authors for permission to use it.
Then consider that you have to persuade Netflix to allow the users of your browser to use their site (without changing user agents).
Neither of these steps were required with NPAPI
There is no reason why Netflix would need to do user-agent sniffing - the EME API is built around request access to specific "Key Systems" (eg. Widevine) by well-known-name. If they do user-agent sniffing that's an entirely separate issue, and is just as much as problem in the Silverlight case.
I don't believe that's true. The plugin is freely available. You just have to write the host.
I don't think Netflix or the rights owners would care since the stream is protected equally in any browser.
That's not what's going on, though. It's an API that a DRM provider can implement. A website that gets a DRM provider it doesn't recognize will refuse to work with it.
Is a programming language a good analogy? The C++ spec says what a switch-statement should do, but nothing about how it must be implemented, right?
> New browsers face a new barrier to entry
It's not really a new barrier to entry though, is it? If I wrote a browser last year, were my chances of getting Netflix to support it better then than they are now?
What about if I wrote a new DRM scheme? With a standard interface, are the barriers to entry for me now lower?