Post #4479493

2026-08-09 19:56 UTC

It’s there and it’s easy. Most people don’t use terminal text editors unless they are SSHing in a server, and they would only do that sporadically, so it makes no sense to become proficient in a complex text editor like vim or Emacs for that little use case. Sidenote: personally, I learned vim once, and used it extensively every day for two years. I stopped using it for one year and was back to square one. Now I use vscode for everything… Even when I’m using SSH, because vscode supports SSH

Replies (3)

@scrion@lemmy.world 2026-08-09 20:55

Every editor “supports” SSH, you can mount files on a remote SSH server via SSHFS.

Open ##4479492
@jaybone@lemmy.zip 2026-08-09 20:52

It’s kind of sad that many people don’t use the shell / terminal anymore, especially as part of their regular development flow. There’s so much scripting and so many shell commands you can use that will do things you just can’t do in vscode. And having an editor like vi immediately available is part of that flow. For me, vim and the shell are my primary IDE. I rarely fire up vscode. But I guess I’m getting old. Still faster than the younger devs who mainly use vscode and then struggle when they are forced to use the command line due to whatever circumstance where vscode is not available or appropriate. Kind of makes me sad. Feels like a valuable skill is being lost.

Open ##4481595
@bilb@lemmy.ml 2026-08-10 13:23

I use kate for almost everything. I can open and edit files over sftp, and it has a terminal like vscode as well. I should try vscode again, it’s been a while.

Open ##4500802