Most of the negatives mentioned (fragility, bugs, plugins breaking often) are specific to neovim.
It's one of the reasons why I am and will always keep using vim instead of neovim.
Vim is a much more mature ecosystem, less chasing the newest "plugin du jour", my vimrc is stable, based on a few dozen plugins which are feature complete and rock solid stable.
I was about to make a very similar comment. I won't say I'll never switch to neovim, for a lot depends on future vim/neovim development, and unexpected things happen.
But I do agree that vim's stability is priceless. It's been years without any need for major changes in my vimrc, and without any trouble with the plugins I use.
I'm sympathetic with the author, though. Whenever you need to change, finding an alternative that "just works" always makes things easier and you can quickly get back to being productive. I'm not so sure that I wouldn't go down a similar path if the vim ecosystem collapsed.
Do you mind sharing that list of plugins you use? I have never used plugins with vim/neovim and only used them vanilla up to this point but interested in checking out the plugin ecosystem.
Echoing the other replies here that idk what breakages this refers to. I switched since I liked lua better than vimscript (after writing a ton of vimscript). I don't use many plugins; the few I use haven't broken. Only encountered a single (non-serious) nvim bug that wasn't also a vim bug in many years of use.
neovim is what happens when the javascript kids decide to "improve" one of the best editors ever created. The entire Lua ecosystem standing on 50 unstable plugins that provide the entire kitchen sink, yet do not even have a 1.0 version is nightmarish.
Follow any guide and either everything breaks, or you get an hodgepodge of automagic popups, stuff that autodownloads, flash messages and useless features that are completely antithetical to the slim, minimal philosophy of vim.
At least the original vim is still around, and the js kids are allergic to parens so there's an alternative.
When I was looking for an editor that supported true color themes, neovim supported them, vim didn't. That decided what I was going to use. Stability is good, but if you need a feature that's not there - stability isn't helping.
There are no Lua kids, i.e newbie programmers that start their career from Lua. The neovim Lua kids were JS kids all along, and brought their philosophy of churn over.
I am not a JS dev, and still prefer nvim. If you’re careful with plugin choices, you can get nice QoL features and still be stable. I can’t think of a time when I’ve had nvim crash.
You’re correct that random guides are generally garbage, but by reading plugin docs (gasp), you can generally get stuff working without much fuss.
