Re:On Encrypted Media Extensions (EME) in HTML5
by azakai on Wednesday March 01, 2017 @11:10PM
(#13771338)
We still have incompatible and proprietary DRM implementations.
EME only standardizes the interface between them and the browser. The DRM itself is completely unspecified here - that's the problem.
Re:On Encrypted Media Extensions (EME) in HTML5
by AndyMcConachie on Thursday March 02, 2017 @08:41AM
(#13773902)
Still better than nothing.
Re:On Encrypted Media Extensions (EME) in HTML5
by aanm1988 on Thursday March 02, 2017 @06:41AM
(#13773378)
I think option 2 is more accurately "google ignores them and does what they want, other browsers follow or get left behind".
Yay, we gave control of huge swaths of the internet to one ad company.
1) The W3C allows EME to be standardized and we hopefully end up with a predictable standard.
2) The W3C not allow EME to be standardized and we end up with incompatible, proprietary and bug ridden DRM implementations.
People who think there was some other option are delduding themselves. The W3C made the right decision.