3 ms·

> For example, tomorrow Google can implement a DRM that would require a plugin that works on Windows, Android (with Google Play Services) or Mac, but not on Lin

by SXX 8y ago

> For example, tomorrow Google can implement a DRM that would require a plugin that works on Windows, Android (with Google Play Services) or Mac, but not on Linux I was reading your comment and wasn't sure if it's well hidden sarcasm or you are seriously don't know this already happened: https://news.ycombinator.com/item?id=19553941 https://news.ycombinator.com/item?id=19553941 Basically you cannot watch high resolutions streams on Linux already even in Google Chrome because of DRM Google among others helped to push into HTML specification.

Teknoman117 8y ago
But what was the alternative before? Remember none of us could watch Netflix on Linux because they built the whole thing on Silverlight.
- SXX 8y ago
  It's not really about alternatives. Before no one pretended that proprietary blob is some part of the web - everyone knew it for what it is: ugly black-box plugin. And any engineer knew how easily is it to bypass said DRM. Problem with what Google among others did is that they was actually in position to push against making something like that part of the web specification. Yet they went all in and what worse become gatekeeper for new web browsers to implement Widevine DRM. Same way Google might push for more open Android ecosystem, but it's not their interests so they did the opposite. And with all Chrome-exclusive features and AMP it's pretty much the same thing happening.