5 ms·

> Option 1 is the best because playing DRM content should be Netflix's problem. By not making it a standard we'll make sure that Neflix never, ever comes to Li

> Option 1 is the best because playing DRM content should be Netflix's problem. By not making it a standard we'll make sure that Neflix never, ever comes to Linux. That guarantees that proprietary operating systems, browsers and hardware will always be prevalent. > By making it a standard it means that we'll never, ever get rid of it. <marquee> and <blink> were standards. NPAPI was a quasi-standard. Black-and-white worldviews are often accurate albeit negligently unrealistic.

jimktrains2 9y ago
> By not making it a standard we'll make sure that Neflix never, ever comes to Linux. Isn't the EME a system binary that would be specific to each platform? There's no guarantee tat they'll be a linux one for each provider.
- zamalek 9y ago
  Agreed. However, Widevine is Google's thing and it's plausible that they'd ship it with some non-free build of Chrome. Unless they're worried about trusting the OS, in which case my original argument is void.
  - jimktrains2 9y ago
    Plausible sure. anyone using any other plugin is also plausible, though much less likely. The point is since it's not standard Linux and BSD will get the shaft.
    - wbl 9y ago
      Wildvine works on Linux today.
      - jimktrains2 9y ago
        And other plugins that other providers might choose to use?
        gsnedders 9y ago
        In most browsers, they aren't actually plugins in the typical sense. As far as I'm aware, Chrome doesn't allow any other EME modules to be installed, so if a provider wants to work with Chrome they must support Widevine.
AnssiH 9y ago
> By not making it a standard we'll make sure that Neflix never, ever comes to Linux. Netflix already works on Linux, with Chrome and Firefox: https://help.netflix.com/en/node/23742 https://help.netflix.com/en/node/23742 It uses EME with closed-source CDMs bundled with the browser (Chrome) or downloaded by the browser (Firefox).
- jandrese 9y ago
  My understanding is that it's using basically what the W3C is now considering. The browser manufacturers already decided on this months ago and implemented it. Now the question is if it becomes part of the standard so there aren't annoying differences between each browser.

jimktrains2 9y ago

> By not making it a standard we'll make sure that Neflix never, ever comes to Linux. Isn't the EME a system binary that would be specific to each platform? There's no guarantee tat they'll be a linux one for each provider.

zamalek 9y ago
Agreed. However, Widevine is Google's thing and it's plausible that they'd ship it with some non-free build of Chrome. Unless they're worried about trusting the OS, in which case my original argument is void.
- jimktrains2 9y ago
  Plausible sure. anyone using any other plugin is also plausible, though much less likely. The point is since it's not standard Linux and BSD will get the shaft.
  - wbl 9y ago
    Wildvine works on Linux today.
    - jimktrains2 9y ago
      And other plugins that other providers might choose to use?
      - gsnedders 9y ago
        In most browsers, they aren't actually plugins in the typical sense. As far as I'm aware, Chrome doesn't allow any other EME modules to be installed, so if a provider wants to work with Chrome they must support Widevine.

AnssiH 9y ago

> By not making it a standard we'll make sure that Neflix never, ever comes to Linux. Netflix already works on Linux, with Chrome and Firefox: https://help.netflix.com/en/node/23742 https://help.netflix.com/en/node/23742 It uses EME with closed-source CDMs bundled with the browser (Chrome) or downloaded by the browser (Firefox).

jandrese 9y ago
My understanding is that it's using basically what the W3C is now considering. The browser manufacturers already decided on this months ago and implemented it. Now the question is if it becomes part of the standard so there aren't annoying differences between each browser.