Sometimes I've a feeling that some people really like it complicated. Today it is no mysterium to mount a remote machine via SSH and edit all the files using atom/sublime/vs code/... so mostly no need for a terminal editor on a remote server.
And have you ever tried to use a terminal (editor) on remote over a connection with high latency? Awful.
1. VS Code doesn't support SSH/SCP/SFTP natively, and Windows/Mac support for sshfs is non-existent/bad. Not to mention it breaks down in tons of cases, especially low latency or dropped connections. And even in Linux, depending on where you mount to, you can basically hork your system to the point where it requires a reboot.
2. Gotta agree with easytiger. I work all the time from 3G tether connection. Mosh makes it a breeze.
I should of course have elaborated on his ludicrous assertion that a tty over ssh has worse latency than an rdp gui or such but his sentence was so self evidently nonsensical and his tone so needlessly aggressive and self assured that I didn't.
It was not an attack and I resent the framing of it as such.
Sublime has an SFTP/FTP plugin that makes it trivial to edit files over SSH. Since you are running ST on your local machine and only using SSH to save/read the file it actually works better over a flaky connection (like on a plane) than SSH+vi.
I've never understood this argument where you limit yourself to something that will work in the worst case scenario. For programming projects as well, the only time I'm using SSH directly is to troubleshoot rare server issues. Besides this, server admin should be automated/scripted so I'm not doing complicated edits over SSH.
