I'm not interested in having heatmaps, timers and other metrics recorded simply because I want to read the news.
Not to mention that I also like to save pages for offline reading, and I expect them to re-render normally, and not trigger background GETS and POSTS and then fail to load.
I'd also like the <a href> tag to behave as I expect it should, and not be intercepted, and changed after I click on it, but before the desired page loads.
Oh, right, and I'd also like my history stack to stay relatively private, but you know that's really asking a lot isn't it: https://developer.mozilla.org/en-US/docs/DOM/Manipulating_th...
Meh, whatever. I guess we should just accept the prevailing wind, and learn to cope with its ramifications, no? Is all this so inevitable?
Tools/Edit > Options/Preferences > Content > click "Enable JavaScript" > OK
Disable it for 30 seconds, while you're using any particular page, and then switch it right back on. No whitelists or blacklists to comb through. Just refresh the page and it takes effect.
Downloading an add-on or an extension is annoying and creates hassle with every upgrade. It's not automatically readily available on every computer you use. In controlled environments with shared machines, desktop support techs don't install add-ons by default, and might actively prevent you from installing them.
Adjusting a global setting that's within easy reach is not an extreme response.
If they relegate that setting to about:config that's probably going to alter the broader user perception about what JavaScript actually represents. It kind of pisses me off. I'll probably stop using Firefox because of it.