3 ms·

I tried Jetbrains remote workstations with Jetbrains space. I had a pretty reliable ~150ms connection. It sucked SO BAD. 150ms + input latency before I see a

• scottlamb 4y ago
  > 150ms + input latency before I see a response? It's a horrendous experience. Definitely, but there are ways to mitigate that: * Better design. With VS Code Remote or Google Cider, the code is stored remotely and the language server runs remotely (so there's lag before the completion pull-down appears) but the UI is local. Characters you type should appear with no round trip required. That seems like table stakes for a good remote development environment in the world the author describes. You can also imagine some prefetching of near-future likely completions [edit to clarify: e.g. prefetch the completion menus that will appear if the user starts typing any of the locals in scope, including not only the names of the locals but also their methods] so that latency is hidden too. For CLI stuff, mosh predicts the characters you type will echo and corrects if not. etc. * Closer datacenters. Typical RTT from Los Angeles to New York is ~66 ms. 150 ms is far! * Lower index of refraction. Instead of traditional fiber, hollow-core fiber or bouncing off LEO satellites like Starlink. Not going to happen universally by 2030, but it will happen some day.