noscript also has "forbid", "temporarily allow", and "allow" settings for blocking domains
NoScript blocks Javascript/Flash/etc. based either on a list you import, or on a case-by-case basis. I use it as a security measure, blocking potentially harmful content by default and enabling it only if I need it for the site to function.
Privacy Badger is not designed for security so much as it is for protection against non-consensual tracking. It observes which third-parties store high-entropy cookies on your device. If it sees a third-party domain doing so across three different first-party websites, it automatically blocks requests for any content to that third-party from your browser.
So I'd say the big differences are Privacy Badger is set-and-forget, while NoScript isn't; Privacy Badger protects against different tracking (including pixel tags); NoScript protects against some first-party tracking (if you don't allow JS on a first-party domain) and security dangers.
Full disclosure: I work for EFF which makes Privacy Badger.
I prefer noscript.
Also, Privacy Badger recently transitioned from beta to 1.0, so if you last tried it more than a month or so ago, I recommend giving it another shot. And if you find bugs, please report them!
Full disclosure: I work at EFF, which makes Privacy Badger.
You can add something like Tab Cookies or Self Destructing Cookies. You can also add something like uMatrix to the mix.
If you really want to go far, add a "User-Agent Switcher" type extension.
I wouldn't add more than this though, it starts to be overkill. Also do note: I used to use noscript and it works well, but going from 0 JS on a domain to all JS on a domain isn't ideal. If you want ultimate security, add noscript as well but maintain the others so that when you whitelist a url you can still expect to be safe.