Exactly. I update if I want a new feature or bug fix, but other than that I love the predictability of knowing nothing has changed, and when it does, exactly what changed. Being able to `git diff` and see what's new is wonderful
How many plugins do you use? I probably have at least 70–80. Tracking what’s changed would be a job in itself, so I just update all plugins regularly, the same way I update IntelliJ IDEA, Homebrew, or Linux packages. If a package breaks often, then I (and most other people) simply stop using it.
> I probably have at least 70–80. Tracking what’s changed would be a job in itself, so I just update all plugins regularly
You and me have completely the opposite approach. You install everything you can get your hands on, I regularly prune my unused plugins to avoid bloat. I don't track what's changed: if I'm happy with a 10 year old version of a plugin, I don't see why I should update it.
> If a package breaks often, then I (and most other people) simply stop using it.
Unless there's a specific error message, how do you even know which package is responsible for the breakage? Ie a new visual glitch starts happening out of nowhere.
> You install everything you can get your hands on
Nah, I install what I find useful - sometimes I know exactly what I want and search for a specific plugin; other times, I just stumble upon something useful. Every now and then, I remove plugins I haven't used in a long time, but since most of them are lazily loaded, it's not like they get in the way.
> Unless there's a specific error message, how do you even know which package is responsible for the breakage?
If I recall correctly, there were one or two plugins I removed because they broke something, and in both cases, it was obvious which one was the culprit.
I have had at least two cases where it wasn't obvious which plugin was introducing the weird behaviour. I turned all plugins off and then gradually turned them on to find out. One of those was vimwiki.
