Mmmm....okay, but the parent comment I was responding to does have a point in that there are some benefits to blocking Javascript above and beyond just trying to deal with tracking. Like, if you're on a laptop, there are sites that will burn a lot of CPU time -- and hence battery life -- doing nothing useful. Or, on an older machine, it can speed up page loading.

My issue is just that unless you're going to turn it on yourself on a site-by-site basis, killing off Javascript breaks too much of the Web today. It was a viable option to just have on back when there was a meaningful portion of the world that didn't have Javascript available and web developers designed pages to deal reasonably with its absence and you were willing to deal with flipping it off on specific sites to deal with the occasional breakage...but today, it's a huge portion of the Web that doesn't work without Javascript.