If you can't use HTML5 DRM with Netflix your other options are either Silver light or a native app and Haiku has neither.
I'd say HTML5 DRM is the far lesser evil in this case.
If you can't use HTML5 DRM with Netflix your other options are either Silver light or a native app and Haiku has neither.
I'd say HTML5 DRM is the far lesser evil in this case.
IMHO If anything EME is more evil than the other options in that it standardizes (and this way implicitely mandates) a special plugin interface for DRM purposes only.
Users still have to install plugins, and now browser vendors get the blame if things fail (since the user will be hard pressed to identify plugin issues in "that website doesn't work").
I fail to see where it's the W3C's, browser vendors' or web users' responsibility to make the DRM vendors' lifes easier. And that's all EME does.
For one, because they'll fail in the most hilarious ways (and each one separately), so there will be backdoors, or at least a good laugh or two. But also because it drives up the cost of DRM, hopefully making it less attractive.
Should DRM manage to get hold even despite such problems and Amazon notices that they can reduce the price of their media package by 1$/month if they drop the DRM, the resulting massacre will be great to watch.
Completely disagree. HTML5 DRM is non-interoptable but disguised as interoptable through its HTML form. That makes it much, much worse.