I've never had NoScript incompatibilites that lasted more than a day, so far, and none recently. It only became an issue because Mozilla switched to a fast release schedule, and some plug-in writers were caught unawares. (Remember that it's the plugin writer who says "compatible with version x" or not, they need to say so in the plugin definition. The plugin might be just fine, with only the version number a problem.)
So, I say stick with NoScript, but be aware of what it's doing. It will block ALL scripts by default, for safety, so you need to tell it to allow them. It has an option in settings for "temporarily allow top level domains by default", and I have it set to "base 2nd-level domains":
- This allows scripts to run from the server that you went to, but blocks all 3rd-party domains. This avoids most problems while providing a very good level of security.
- But note that certain sites use their own "3rd-party" domains e.g Google Gmail requires that you allow gstatic.com, before it will work properly. The BBC website requires bbcimg.co.uk before video will work.
I don't know if I can put it more simply than that. NoScript is a great tool, but it's not magic. It needs a little help from you to cope with all the weird things that all those different websites do.