I use vim key bindings on IntelliJ
Ask HN: How many people actually use Vim?
11–14 of 14 posts
Re: Ask HN: How many people actually use Vim?
#12I use vim for almost all my development. I'm using vim ranging from small projects (10M lines). I never experienced vim to hinder me understanding large projects, nor does it slow me down. There are no features in VSCode (or equivalent) that I'm missing in vim. Actually it's the opposite: the learning curve is steep, but when I was comfortable enough with all the vim key bindings and features, development actually got faster and better using vim compared to using VSCode equivalents. It forces me to think more before I start coding.
I do need to code in VSCode sometimes when it's work related though.
Re: Ask HN: How many people actually use Vim?
#13I use vim or vim emulation everywhere. I really miss it when I don't have it. I have not tried emacs yet because I'm just not ready to take on a new tool right now and I have a decent vimrc going that I really like. I've heard good things though.
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.
Re: Ask HN: How many people actually use Vim?
#14What continues to happen is when the next big thing in text editing shows up--Textmate, Sublime, BBEdit, and now VS Code, there are lots of those users who become disillusioned (for all kinds of reasons) and end up on Vim.
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].