3 ms·

I find comments like this incomprehensible. Are you using a Vim emulator in VS Code? If not, how can you possibly be more productive? People use Vim precisely b

I find comments like this incomprehensible. Are you using a Vim emulator in VS Code? If not, how can you possibly be more productive? People use Vim precisely because it offers a faster more efficient way to write code. What is it about VS Code that makes you more productive?

cylon13 6y ago
Not the parent, but I switched from vim+plugins to vscode+plugins for most development. I absolutely use the vim plugin because I can't stand to edit text without vim keybindings anymore. The reason I switched is that plugins in vim are more of a pain to configure and they are usually less maintained and polished than their vscode equivalents. For example, let's say I'm not set up to program rust at all. In vscode, I just search "rust" in extensions, grab the most popular one, and it sets itself up magically. In vim, my experience was that I would lose a few hours to configuration, and the plugin would still be a little janky. I still use vim as a plain text editor, and every once in a while I need to open a file in vim to do some serious macro editing (macros aren't perfectly supported by the plugin), but for the most part vscode+vimplugin is just nicer to use for day to day development. I should specify that my daily work languages are typescript & c#/unity on linux, but I've also been writing a fair amount of rust lately.
snarfy 6y ago
I use both. If I want to look at a single file I'll use vim. If I want to look at a group of files in a folder I'll use vscode. They are both text editors that support plugins to the point of becoming an ide, but it is far easier to make vscode work as an ide than it is vim, and that's coming from somebody that's been using vim since it's inception.
BeetleB 6y ago
There are more aspects to productivity than typing efficiency.
- TaupeRanger 6y ago
  Sure - that's why I asked. I haven't seen any explanation for why VSCode is more productive than Vim. I hear about viewing files and folders, but you can do that in Vim very easily with no friction.

cylon13 6y ago

Not the parent, but I switched from vim+plugins to vscode+plugins for most development. I absolutely use the vim plugin because I can't stand to edit text without vim keybindings anymore. The reason I switched is that plugins in vim are more of a pain to configure and they are usually less maintained and polished than their vscode equivalents. For example, let's say I'm not set up to program rust at all. In vscode, I just search "rust" in extensions, grab the most popular one, and it sets itself up magically. In vim, my experience was that I would lose a few hours to configuration, and the plugin would still be a little janky. I still use vim as a plain text editor, and every once in a while I need to open a file in vim to do some serious macro editing (macros aren't perfectly supported by the plugin), but for the most part vscode+vimplugin is just nicer to use for day to day development. I should specify that my daily work languages are typescript & c#/unity on linux, but I've also been writing a fair amount of rust lately.

snarfy 6y ago

I use both. If I want to look at a single file I'll use vim. If I want to look at a group of files in a folder I'll use vscode. They are both text editors that support plugins to the point of becoming an ide, but it is far easier to make vscode work as an ide than it is vim, and that's coming from somebody that's been using vim since it's inception.

BeetleB 6y ago

There are more aspects to productivity than typing efficiency.

TaupeRanger 6y ago
Sure - that's why I asked. I haven't seen any explanation for why VSCode is more productive than Vim. I hear about viewing files and folders, but you can do that in Vim very easily with no friction.