I don't think DRM is great (hate it, actually), but I do understand why the content companies would want it. If I were a content owner I would want to use some sort of DRM system as well, even if it's easy to circumvent.
Does it really matter whether DRM is enabled in Chrome? It has to do with ease of use more than anything. I don't like it, but I don't see how not including EME is good for the end user, if the alternative is having to install a secondary app.
You should want the whole process to be as frictionless as possible, even if that means giving up "amazing code quality" or "a beautiful standard". You can have great code and a crappy app. I don't think the world needs more crappy apps with great code.
Sure they want it, if I were content owner I would probably want it too.
From my POV, DRM enabled Chrome matters. It matters, because
- it makes browsers that do not include DRM uncompetetive (especially those who have another business model or do not have bizdev capabilities of Google, Microsoft or Apple).
- it taints the standards and,
- sets the expectations or baseline for having the DRM available.
If the alternative would be to install a secondary app, things would be more obvious:
- that there is a price in developing, maintaining and supporting DRM,
- that price would have to be paid for those who wish the DRM,
- having DRM available would not be seen as automatic,
- you could not use bizdev capabilities in DRM to be able to push your browser - i.e., only Edge supports Netflix in FullHD (Chrome only in 720p). Yes, the official excuse is that Edge supports DRM X and Chrome only DRM Y, but in the end, it is only a business deal that DRM X is deemed acceptable for FHD and DRM Y is not.
I don't think DRM is great (hate it, actually), but I do understand why the content companies would want it. If I were a content owner I would want to use some sort of DRM system as well, even if it's easy to circumvent.
Does it really matter whether DRM is enabled in Chrome? It has to do with ease of use more than anything. I don't like it, but I don't see how not including EME is good for the end user, if the alternative is having to install a secondary app.
You should want the whole process to be as frictionless as possible, even if that means giving up "amazing code quality" or "a beautiful standard". You can have great code and a crappy app. I don't think the world needs more crappy apps with great code.