Yes, I mostly do. Simply, for a random website the drawbacks of giving Javascript access to it outweigh the benefits for me. (Small probabilities of a website f

Yes, I mostly do. Simply, for a random website the drawbacks of giving Javascript access to it outweigh the benefits for me. (Small probabilities of a website fingerprinting me, infringing my privacy or executing a browser exploit add up, and there also is a small philosophical component to this of preference of minimalism.) When I trust the site or it is just too more useful for me with Javascript than without, though, I enable Javascript for it specifically. I look forward to browsers which defend against violation of user privacy more intelligently than just rejecting all Javascript, for example, marking some information secret so that everything computed from it can be displayed and saved, but not sent back to the net - if an attempt is made, it is stopped and either error is shown or error is returned, but other threads of code are not affected. For example, for an editor web app, the file that is loaded into the app is marked secret so it can be edited and saved locally, but cannot leave the browser outwards; or for a page that contacts multiple servers, info from each will be marked as secret for it, so every server can get back its own info but cannot get info of other ones (can also configure which site can additionally get info from which). Can use typing here to guarantee correctness.