It's not a question of browser support, it's a question of user choice. Do I want to allow any and all websites to run random scripts on my computer?
For some people and some sites, the answer is an obvious yes. Especially when the script is an integral part of the app or site you're visiting, such as a game or a highly interactive tool.
Sometimes though, the content should be enough. There are plenty of sites out there, like blogs, that shouldn't need js to provide their primary function. For example, I don't feel that I should need to enable client side scripting to view a 140 character tweet on the twitter site.
For some people, tracking via js is the primary concern, and in their case it makes sense to disable js whenever possible, and use offline tools for everything that needs to be interactive.
In any case, this move has a solid precedent, and as others have noted there are plenty of plugins that allow granular control over js execution.
For some people and some sites, the answer is an obvious yes. Especially when the script is an integral part of the app or site you're visiting, such as a game or a highly interactive tool.
Sometimes though, the content should be enough. There are plenty of sites out there, like blogs, that shouldn't need js to provide their primary function. For example, I don't feel that I should need to enable client side scripting to view a 140 character tweet on the twitter site.
For some people, tracking via js is the primary concern, and in their case it makes sense to disable js whenever possible, and use offline tools for everything that needs to be interactive.
In any case, this move has a solid precedent, and as others have noted there are plenty of plugins that allow granular control over js execution.