Re:Update on HTML5 Video for Netflix
by kibwen on Wednesday March 22, 2017 @05:05PM
(#13934952)
Mozilla did fight back, but nobody in the OSS community at large bothered to care about EME until the writing was already on the wall. I remember being at the Mozilla Summit 2013 discussing Mozilla's alternative proposals, but even by then the prevailing mood was that of imminent despair at the inevitable.
[ Parent
| on HN ]
out of curiosity, what alternative proposals were offered?
AFAIR the alternative with the most promise involved implementing a new video codec in JS (heavily leveraging the GPU and the then-nascent asm.js) with first-class support for digital watermarking, then convincing studios that per-user watermarking was more effective than DRM. You can see the difficulty of Mozilla's position: it wasn't enough to come up with an alternative to EME, they had to come up with an alternative to DRM altogether. A tough sell, to say the least, and basically DOA because Chrome and IE were shipping EME for use with Netflix in 2012.