I know the prevailing attitude here is anti-DRM at all costs, but I think this argument hits some incredibly good points. Basically there are only a few options

I know the prevailing attitude here is anti-DRM at all costs, but I think this argument hits some incredibly good points. Basically there are only a few options for delivering available to companies like Netflix: 1. Write native apps 2. Use HTML with a plug-in 3. Integrate DRM into HTML 4. Don't use DRM at all I don't think that option 4 is realistic in the near term, as much as we'd like. Maybe one day we can get there like with music. I do think that TV and Movies are a much different market, where rental is more attractive than purchase, so it might not be totally viable. That leaves native apps, plugins, and DRM support in HTML. Can anyone who thinks the web model is the best way to deliver content and apps reasonably argue that DRM in HTML _isn't_ the best of those? For more fringe platforms, a standard like EME is the only hope for support from mainstream contest providers. Without something like EME you're at the mercy of the providers cost / benefit analysis: are there enough paying users on your platform to justify the costs of supporting it. With EME you're at the mercy of the platforms cost / benefit analysis: are there enough users of all the content providers to justify supporting EME. That is more likely to be true. Yes, there are problems with supporting fully open systems, but those were there anyway, without EME. If you choose to only run OSS without hardware DRM you might have trouble watching Netflix. My guess is that that's ok with you on principle.