I’d love to see that happen, but I don’t think Mr. Ankarström adequately explains what should be done with all of the JS currently in the wild. We can’t just nuke it all from orbit, as much as I would like to stick it to the adtech industry as a whole (especially Google and Facebook) by doing so.
I’d honestly settle for browsers handling JS the way they do cookies. Let me decide whether to allow all JS, allow only self-hosted JS, or disable JS entirely — and let me blacklist/whitelist particular domains.
Is that so fucking hard?
It must be really fucking hard, because even Mozilla — whose PR is all about how they alone care about users — hasn’t done so. They don’t even implement the option but hide it in about:config so that only people who know what they’re doing mess with it.
Why? Maybe the developers think that ad-blocking extensions are good enough. However, they aren’t.
Most websites are defective because most web developers don’t get the fundamental principle of progressive enhancement:
- Use clean, semantic HTML5 to deliver core functionality.
- Implement all client/server communication using HTML5 forms and HTTP GET and POST operations.
- Use just enough CSS to make the page look good.
- Check browser capabilities after the basic page has rendered and offer enhanced functionality using JS to clients with current equipment and fast connections.
It shouldn’t be that hard to grasp. I manage it, and I’m just some long-haired metalhead who rants about the internet when he should be writing.