[brozaman]

>>With VSCode, you type the name of any programming language in the extension search, click "Install", and you have a world-class development environment

> Very minor feature. It is not usefull unless you are constantly hunting for new languages.

The big advantage isn't just installing but keeping them up to date without any actual effort. I used to know vimscript, used to understand how the vim package managers I used works and all. With VSCode I don't even know in which language are extenssions written.

I work mostly on golang, and now the environment is certainly more stable, but I remember that in order to have go extensions working on vim I used to have to be updating manually the extensions pretty much every release and it was some effort. Now I update the golang version and things just work.

[hnfong]

I do agree the Vim plugin ecosystem (and vimscript) sort of sucks. That said, I've been using Vim for 20+ years and generally only mess with my config and plugins once every 2-3 years at most. Since the thing is just supposed to edit text, why would I feel compelled to update them, much less try to figure out what language they're written in?

[Beltalowda]

> I work mostly on golang, and now the environment is certainly more stable, but I remember that in order to have go extensions working on vim I used to have to be updating manually the extensions pretty much every release and it was some effort. Now I update the golang version and things just work.

Most of that is because the Go ecosystem moved ahead. Five years ago something like vim-go would depend on maybe 15 different binaries that operated on the source code. Automatically updating all of that is possible, but somewhat slow and tricky (especially because there were no modules yet, so had to "go get -u" all these different binaries to check for updates).

Now, it's basically just gopls. You don't even need vim-go any more; just Vim + $any_lsp + gopls gives a very similar experience.