What are the dangers of JavaScript

What are the dangers of not blocking JavaScript? What are some worst case scenarios that could happen? Is it worth to bother to have NoScript?

dumbass crypto miners and ad trackers, mainly. The chances of you getting hit with a a leet 0day are pretty much nil, despite what the whack-job lapers on here will say; nobody will waste that on a random image board user. You should still block it though because it makes sites faster and the whole principal of "my computer my rules".

>>3963 annoying <script> alert("scripts") </script> arnt worth it

Use uMatrix instead, it's better. You'll be amazed when you see the amount of proprietary javascript being run on most websites to track you.

I do it mostly to neuter various tracker scripts. My default policy is to only run first party js. It's also nice to avoid the misc. ad fraud and spam popups that most pirate streaming sites will try to hit you with. A lot of the fear surrounding javascript has traditionally been about XSS attacks, which are no longer viable on modern browsers. For privacy issues, just blocking javascript isn't really enough. You have to be careful with pretty much anything served by a 3rd party (frames, cookies, even images). That's why something like umatrix is nice. Lets you maintain whatever kind of default configuration you want, and manually change it per-site. Helps a lot if, for instance, you want to be able to use a google or facebook account when visiting their site directly, but you don't want to load their tracking beacons on other sites. You can even whitelist specific frames - very helpful for blocking google analytics trackers while still allowing captcha to function.

Javascript can be used to greatly increase the reliability of browser/plugin exploits, and many exploit packs make use of them. Google "heap spray".