I see your point but think it's worth a couple comments. First, blocking javascript globally is a bit different, in my mind, from blocking it by default (i.e. w

I see your point but think it's worth a couple comments. First, blocking javascript globally is a bit different, in my mind, from blocking it by default (i.e. whitelisting). Second my wording wasn't great, I more meant "try blocking javascript by default and see how you like it". I agree it's not for everyone, but in my A/B tests it's my clear favorite. Some benefits of a whitelist approach: You can set preferences to allow javascript for pages you regularly visit and trust. Meanwhile, if you're visiting an unfamiliar or unusual site, you're completely protected by default and still only one click from full functionality.