[phaedrix]

I've been using vim and neovim for over 15 years with many 10s of plugins and I can probably count on one or two hands when an update has caused problems.

Also use Arch for about as long.

It's so odd to me when someone says that updates break their vim or Arch frequently.

[satvikpendem]

There are so many threads about it on /r/neovim that people have started to ask just which plugins actually work together cohesively without breaking [0], something that is not asked about for VSCode. Just go through their "Needs Help" flair and you'll see lots of issues [1]. For me, I also use tens of plugins but inevitably something breaks at least once every couple of weeks.

[0] https://old.reddit.com/r/neovim/comments/1c9ev8n/overwhelmed...

[1] https://old.reddit.com/r/neovim/search?sort=new&restrict_sr=...

[ossusermivami]

just use lazyvim[1] and be done with it! some people takes care of the compatibility and they are probably more competent than you (i mean a newcomer who starts writing their nvim config)

[1] https://www.lazyvim.org/

[satvikpendem]

Clearly you didn't read any of the threads as it is sometimes even lazyvim that causes these incompatibilities:

https://old.reddit.com/r/neovim/comments/1dgtyzw/lazynvim_do...

https://old.reddit.com/r/neovim/comments/1dp47gi/lazyvim_own...

[SpaceNugget]

One of those threads is about lazy.nvim, not lazyvim. The other is a question about what to do after accidentally installing lazyvim with the wrong shell on windows, not about plugin updates breaking things.

[satvikpendem]

Lazyvim is powered by lazy.nvim, at some point it'll break. These are example posts, you can feel free to go through reddit for more examples but yes Neovim does routinely break more for me than VSCode ever does, which is basically never.

[ossusermivami]

it never has been my experience! i have used lazyvim distro for the last year or so and run some :Lazy update for time to time and usually i just need to close neovim and restart and it will all be working well..

I think i had an issue when they moved to conform.nvim from the deprecated language server based method but that's maybe about it (I deleted the nvim cache and it was all good after)

[Affric]

Right?

I can count the number of times my vim and arch installs has broken without my intervention on no hands.

[mynameisvlad]

Your anecdote does not somehow counter dozens of others that clearly exist across the internet. Just because it works for you does not mean it works across the board.

[Affric]

100%

Arch just shipped a beta nvidia driver as release and heaps of people have found their system broken.