No, if you just need to read some text a lot of sites function with JavaScript disabled. Also, you can permanently enable sites, so often it is a one-time flip of the switch.
I think (but never really researched and enabled it) you can also have it run in whitelist mode by default, so that you can disable JS for specific sites.
...and after that first pass of enabling only what's needed to get a site to work sufficiently well, that site tends to be significantly more pleasant to use in future.
I enabled JS for just eff.org, and coveryourtracks tells me I'm still spewing 17.12 bits of fingerprint all over the internet. I suppose it'd be possible for a browser to randomly rotate stuff like user-agent through multiple common values to mitigate that.
I think (but never really researched and enabled it) you can also have it run in whitelist mode by default, so that you can disable JS for specific sites.
Best to give it a try though.