>However, by not standardizing, we lock out all sorts of non-mainstream clients form accessing content. Now that Flash is going to disappear entirely, that mean

>However, by not standardizing, we lock out all sorts of non-mainstream clients form accessing content. Now that Flash is going to disappear entirely, that means no access to all sorts of content on Linux, unless it's standardized. That is simply not true. Flash was on the way out with or with out EME, Chrome and IE was already doing it. With out EME they still would have moved forward with their implementations of Widevine and PlayReady respectively. Netflix would have still switch to it, and Chrome on Linux would have still played Netflix. EME did not result in "Content coming to Linux" and there is no guarantee it will continue. It will be up to the individual CDM makers, in this case google, if they want to continue to include the binary blob on Linux. No different than Flash. If google chooses tomorrow to remove widevine from Chrome on Linux, there goes your Netflix and any future "HTML5 EME" enabled websites Further many other "HTML5" Browsers can not play this content because the binary blob required is not there... making it non-interoperable with any true FOSS gnu/linux operating system. Firefox has to pay Adobe for a CDM Plugin under pressure from their less than idealist users... "HTML5" as a standard should mean anyone implementing the spec is able to see all content built on the spec. Sadly with the inclusion of EME sites like Netflix can claim to be "HTML5" compliant while still preventing every FOSS HTML5 browser from viewing any content. That is not a WIN for Standardization, or a WIN for interoperablity