> I tried very hard to get used to Vim. I just feel compared to something like Visual Studio Code it's still very clunky. This just means you failed to get use

> I tried very hard to get used to Vim. I just feel compared to something like Visual Studio Code it's still very clunky. This just means you failed to get used to Vim. Has nothing to do with it being "clunky". I use Vim for many cases, and other IDEs for when I'm forced to use them, such as Android studio (IntelliJ) for Android, XCode for iOS, and certain languages where it's hard to remember the syntax, so I think I'm qualified to answer, coming from a user of all of these editors. For dealing with API-heavy frameworks I think IDE is good. But even then I prefer to have some sort of Vim plugin integrated into the editor so I can take advantage of shortcuts from both the IDE itself and the Vim scheme. One benefit with Vim is that it's become almost a standard that you can find vim plugin in any IDE (Except for recent changes in XCode) so you can just expect to jump on to any editor and be immediately productive, without having to learn each editor command. You don't have that for Sublime or Atom. Sure some editors have similar commands for dealing with similar features, but not always. It's an "editing scheme", not just a single editor. This is why it's much more efficient in the grand scheme of things than any other editors exactly because of that, in my opinion. Editors will come and go, but editing schemes are forever.