I've gone hog-wild for VS Code, but I've used vi(m) since the 1990s and it's still in my fingers.
The primary reason I would use vi over code these days is when I'm editing code on a remote host I haven't mounted, which I sometimes do from my mobile devices, although as a Perl guy, perltidy uses perl, which I don't have installed in Windows, so, when I want formatted code (and I'm not using Remote-WSL), I use vi in WSL to tidy it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've gone hog-wild for VS Code, but I've used vi(m) since the 1990s and it's still in my fingers.
The primary reason I would use
vi
overcode
these days is when I'm editing code on a remote host I haven't mounted, which I sometimes do from my mobile devices, although as a Perl guy,perltidy
usesperl
, which I don't have installed in Windows, so, when I want formatted code (and I'm not usingRemote-WSL
), I usevi
in WSL to tidy it.