Yes, there is a major distribution, availability, region and device-lockdown issue to be solved. But removing all protection is just the brute-force, blanket solution that is understandably one-sided and thus unworkable.

Use JavaScript, then.

There are a lot of people in tech, and particularly in web-related tech, who are very enthusiastic, but whose admirable enthusiasm is not always matched by their realism or level of experience. Any time you challenge an idealised view that something that's being done today is inherently better than something that was done yesterday, you tend to get some resistance. This tends to go double when the reasons for the challenge are based on pragmatic concerns rather than simply trying to use the newest and shiniest tech, as in this case.

There have been many examples over the years: the old CSS-vs-table-layout debate, progressive enhancement/graceful degradation, general hostility towards any sort of plug-ins, general hostility towards DRM schemes (or charging for access to anything, for that matter), "evergreen" browsers vs. IE, A/B testing vs. just about anything else, and recently more variations involving JS or CSS frameworks than I can even count any more. And of course $deity help you if you think flat design is mostly poorly executed rubbish and the worst general trend in design and usability for a generation, because Apple, Microsoft and Google all love it so it must be good! ;-)

So whether or not it attracts some downvotes, I think it's important for someone to challenge new assumptions in these kinds of cases. That's how we figure out what really works, because it stands up to scrutiny. It's also how we shine a light on people who are "moving forward in reverse", however good their intentions or interesting their ideas, and try to steer the industry a tiny bit closer towards something more productive.