[DannyBee]

Errr, your link points to documentation about DRM in the linux kernel, which isn't the same DRM you are talking about.

What all the docs in that link are talking about is the Direct Rendering Manager.

Every single ChromeOS machine also has a developer switch, which will let you put whatever you want on the machine.

[contingencies]

Oh OK, I didn't actually read those I was just posting the likely link that popped up on a search. Feel free to do your own research then.

'Developer mode' that disables consumption of things you have paid for on a machine that has virtually no storage? Sounds great. Why do you seem to support them?

[DannyBee]

I did my own research, and i don't see the issue?

Yes, developer mode erases the machine for security reasons.

I don't see to support them, I do support them on this (I actually am not a fan of chromeos in general), because it is still a huge step forward over almost all available newer "locked" machines available.

Your solution is what exactly?

It seems they've done the best pragmatic thing they can do here. It enables DRM and content for those who want it. Those who don't, can still do what they want with the machine. If you want to have your cake and eat it to, yell at netflix/et al. It's not like Google has an real leverage here. They've tried for years to get anywhere with other strategies.

[contingencies]

Oh, for security reasons! Whose security? Let's be honest here: the content owners. It's classic DRM: you buy the device and it works for someone else. My solution is to strive to avoid buying, supporting or discussing DRM-crippled devices except to reveal their true nature to the wider community. "Don't be evil!". Puh-lease. Anyone know what Google spends on PR? I'm sure it's either hidden or shocking.