3 ms·
If you fire up an editor on the remote machine, there is going to be typing lag, unless your Linux machine is in your local network. You can ameliorate this wit
by Scarbutt 8y ago
If you fire up an editor on the remote machine, there is going to be typing lag, unless your Linux machine is in your local network. You can ameliorate this with software such as Mosh, but that comes with its own disadvantages (losing scrollback buffers).
No typing lag for me on remote machines (< 70ms). I don't use mosh but the scrollback issue can be solved with tmux which is a must for remote dev.
If you edit locally but save the files to the remote system, you have to worry about getting disconnected or your machine shutting off and losing changes.
Again, learn what tmux is.
- copperx 8y agoYes, tmux can reduce the pain significantly. But what if you're using anything graphical for development? VS Code, Jetbrains IDEs? I guess you can use X forwarding. But what a pain. And if you're creating a webapp, you still want to see how it looks on a web browser. But you make some fair points. I will try to use tmux for remote development for a few days.
- Scarbutt 8y agoOh yes, this setup works smoothly only if you use a console editor like vim or emacs IMO, some IDEs/editors let you edit remote config files but I don't like that flow. * And if you're creating a webapp, you still want to see how it looks on a web browser.* You know the browser is a networked application right? just like you use your local ssh client to connect to the remote ssh server, you use your local web browser to connect to your remote web server.