4 ms·
There are things that vim does better. There are things that VS Code does better. There are things that Visual Studio does better. You can memorize all sorts of
by dhmiller 6y ago
There are things that vim does better. There are things that VS Code does better. There are things that Visual Studio does better. You can memorize all sorts of things about your particular editor of choice and you will be more efficient and effective in that editor.
If I wanted to cherry pick examples of what vim does better, I could start all of them with, "first ssh into a random server."
What makes vim great is that it has a tremendous number of features and is available nearly everywhere. Can VS Code do that?
- imtringued 6y agosshing into a server invalidates all the time you spent on customizing your local vim.
- alwillis 6y agoIf you’re on your machine, you can do all of your stuff because you can edit files remotely from within Vim using SSH as the transport: http://usevim.com/2012/03/16/editing-remote-files http://usevim.com/2012/03/16/editing-remote-files If you’re on a new machine, you can grab your dotfile repo from wherever you keep it—like GitHub for example—and you’ve got your complete config, since there just text files. Takes 5 minutes. But even plain vanilla Vim is more than enough for many tasks on a new Unix/Linux box.
- bjoli 6y agoNot if you use Emacs/evil. Tramp invalidates most of the "well, vim is available on all my remote servers, whereas Emacs never is". I just remote into a server from within Emacs. Evil is also the best and most complete vim experience outside of vim.
- snorlaxle 6y agoVS Code can (sort of) do that: https://github.com/cdr/sshcode https://github.com/cdr/sshcode