I couldn't care less about Netflix, I never intended to use their services and never will, but this really is bad news for the web.
Netflix on the web with a plugin was fine for me: people wanting to watch Netflix on their standards-compliant browser would need to install a proprietary plugin to do so, and would have done it (at least a great number would have, I guess). It was their choice to do so (the other one being not to watch Netflix in a browser, and yes it _is_ a choice).
The difference (and it's big to me) was that it had _no_ impact on people not wanting to watch Netflix in their browser. These people did not have this proprietary code running in their browser and all the potential security issues coming with it.
IMO the browsers should (and I don't actually know if they do or not atm, this is a thing I need to check soon) at the very least let people opt in or out of this. Of course if they opt out they wouldn't be able to use services like Netflix.
And here comes the browser plugins world again... So much for killing flash (which was and still is a _great_ platform for small to medium web games).
People are just tying themselves in knots to act like the status quo is a disaster.
I suppose that viewpoint admits that obstinance on the part of Firefox was not going to get Netflix to offer their service without DRM.
edit: not really sure how I messed up the original comment, which was an incoherent mess.
I understand the argument about this making it harder to develop new browsers and so on, but eschewing EME probably wasn't going to prevent that from happening, it would just happen in flash or other closed code.
Yes. The bit where this is an "open standard" to implement completely closed, non-standard plugins, which cannot be implemented by reading the spec.
With this "open standard" any browser or OS not blessed by Hollywood can't have a full web experience.
And I take great issues with that.