I'm not sure it's an elephant. I work in this space and I think the EME path has been a fairly elegant solution for a lot of what was preventing us from being

I'm not sure it's an elephant. I work in this space and I think the EME path has been a fairly elegant solution for a lot of what was preventing us from being able to use HTML5 video, including DRM but also live streaming and its ilk with HLS/Dash and being able to quickly implement new codecs and transports. Having to fall back to a flash player was never ideal. If you want to make an argument that DRM is bad, or, maybe more relevant, ineffective I'm not sure I'd argue with you. However I think the solution we have in place has made the video ecosystem in the browser better and did it quickly. The issue here is about commercial use of a product and while we can blame Google as the owners of Widevine this really doesn't have anything to do with Chrome - outside of the fact that the author was able to quickly create his own browser based on open source components upon which Chrome was based.