That being said DRM by default in browsers (through EME) is probably the end of the "open web" - or at the very least the end of a "clean open web", meaning that everything will need to be hacked and cracked to make it work. Want to copy text or an image from a website? You'll have to find the crack for that website. Not to mention that doing that will be soon declared illegal (if it's not already from the moment DRM is applied to something).
Minification and obfuscation have often been enough so far but the slope we're sliding down is pretty steep and if TBL wants us at the bottom a lot of people are just going to follow suit. As someone who's finally embracing that development is increasingly being pushed to the web over native devices, I'm likely to be looking for yet another career shift (first from IT to software dev) before its all said and done. I do not look forward to debugging DRM when I already loathe minified JavaScript. Tooling is already abysmally slow in spite of Chrome's excellent dev tools (unmatched by any other browser or plugin IMO).
While I do understand the concept of protecting IP, this measure is inherently flawed right out of the gate. I'd honestly rather keep archaic Flash and not-so-archaic Silverlight around because at least their tooling is decent. I can't wait another 10+ years for this to catch up because everyone is foolishly starting from 0, not building on their successes (however much or little you define).
I thought another article pointed blocking the command out in the spec but I could be totally wrong there. Even so, nothing is stopping anyone from building a dumb front end and placing the entirety of the logic in the DRM container. Netflix isn't an argument in countries where it doesn't apply, like much of the world. View source and the actual openness of the web would be that argument, however. If its a concoction made up by what the EFF believes this fight would go versus an actual result of the fight as it stands, then I sadly fell for it pretty hard. Its not a difficult leap to make but I'm definitely more interested in facts over opinion based on someone's failing attempt at predicting the future.
A browser that is 100% compliant with all W3C specs (and nothing non-standard) will not be able to play a single Netflix video, because that requires (deliberately non-standardized) Netflix DRM Extension (CDM) to be licensed and baked into the browser.
It's the same way PS2 piracy was so rampant. You only needed to install a simple mod chip into your PS2, and since all of the DRM relied on that, you could now run every game with no additional work. It created something of a golden age for gaming piracy and the PS2 actually remains popular today in certain regions because of it.
So standardizing DRM into the browser is a huge boon for pirates, and a problem waiting to happen for everyone else. The stupidity is sometimes mind-blowing.