My rule of thumb is this: Does the solution solve more problems than it creates? Taking the example of Vue.js, I found that it makes building UIs a lot easier.

My rule of thumb is this: Does the solution solve more problems than it creates? Taking the example of Vue.js, I found that it makes building UIs a lot easier. But I found that you do need to understand its caveats and its limitations (e.g. limitations in its reactivity system). On balance, it does solve more problems and those limitations are really minor and well documented. But before I embraced it, I spent some time experimenting with it, assessing the documentation, the community, ecosystem, etc... I think this is a skill onto itself that comes with experience. I remember jumping on the "cool" bandwagon many times, only to realise I was basically wasting a lot of time switching to cool new technology X. Nowadays, if I can't understand the problem something is trying to solve, it probably means I don't have that problem. Edit: added "limitations in" its reactivity system.