[jfasi]

I used to work at a company that gave our two machines: a beefy desktop with lots of RAM, many cores, two GPUs, a fast disk, etc., and a mid-range Apple laptop. For consistency reasons, my main development environment ended up being a tmux session running on the desktop, and I would ssh in to the machine from the laptop.

The latency hovered around 100ms (it's not great), but it went up and down throughout the day and as I moved in and out of the office. Honestly, it isn't so bad. I find after years of working like this I keep enough of a mental model of what I've typed that I'm not bothered by even the "we're done here" setting.

[jhayward]

While we're doing asides: In days gone by I worked with a person who was regularly 2 or more full window switches ahead of Emacs. Meaning, they could type a switch window command and using their memory of the code and point there type a search/delete/change, switch to a 2nd window, do the same, etc all before the 1st window rendered.

Of course this was on slow computers so it was not so much a feat of speed but rather how much of the full code they were holding in their head at any time.

[rsynnott]

Was the desktop thousands of miles away? I’d expect under an ms from the network for this sort of setup. Maybe ~2ms if it was WiFi.

Unless it was 2.4Ghz, I suppose; all bets are off then.

[nfoz]

Have you considered mosh? https://mosh.org/