For me, lazy.nvim doesn't pull the latest commits automatically. I have to <leader>-L and SHIFT-U it. And I don't do it often exactly because if there's an issue with the plugins I hope it's caught by others and addressed before I update mine.
the nr of times now people have been owned by rogue plugins via editors is rising each day...
Now I use vimplug though
git submodule updateAnd, also, I was young, and that made me feel good :D
(There's sort of an issue in that I'd prefer to get it in neovim/lua, but that's not the point here.)
I update my plugins when I want/need to.
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.
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.