But that being said, the people behind Go do a survey once a year where they ask about what editors people use https://go.dev/blog/survey2020-results
> VS Code remains the most preferred editor (41%), with GoLand a strong second (35%). Together these editors made up 76% of responses, and other preferences did not continue to decrease as they had in previous years.
Vim is at 14%
I can’t speak for them but I wanted an editor that I wouldn’t outgrow, was extensible and programmable—Vim does not disappoint.
The composability of Vim is its killer feature IMHO regardless of what’s new and shinny.
I see lots of complaints about VSCode being an Electron app and while its performance has improved a great deal over the years, it can bog down with large files, etc.
And even though I’ve been using Vim (now mostly Neovim), for 10+ years, I continue to learn about features that have been around forever but I didn’t need or care about until just recently.
One of the articles that got me started down this rabbit hole is the famous (in certain circles) "Your problem with Vim is that you don't grok vi.” essay that’s a response to a question on Stack Overflow [1].
I think it's good to be familiar with a console based text editor for those times when you just can't have a GUI editor. I end up in the console so much that I ultimately just decided to emulate vim wherever possible to keep things consistent, and I've gotten much better with vim over the years as a result. I don't think there's anything wrong with using a certain text editor though, just use whatever works for you.
I do need to code in VSCode sometimes when it's work related though.
vim for shell scripts and configuring servers, firewall, nginx.conf, etc.
`set -o vi` for my shell.
MacVim or GVim to export code snippets for my blog using Syntax -> Convert to HTML