undefined | Better HN

0 pointspaxys2y ago0 comments

SSH used to work perfectly fine over 28.8 kbps modems. You don't really need a stellar connection for remote coding. If your internet is capable enough for a video call it can run a hundred remote IDEs side by side.

0 comments

mh-2y ago

>SSH used to work perfectly fine over 28.8 kbps modems.

I can't agree with "perfectly fine" here. Not unless you enabled local echo in your terminal emulator. The keyboard latency, especially for typo correction, was maddening. I still remember what a staggering QoL improvement it was the first time I used a low-latency connection to a server.

vbezhenar2y ago

That's why vi is so handy over bad links: with rich command set you minimize number of key presses to achieve the target goal.

dehrmann2y ago

It doesn't work perfectly fine over in-flight wifi.

withinboredom2y ago

SSH falls apart with packet loss. In a plane, you usually have a ton of packet loss.

traceroute662y ago

> It doesn't work perfectly fine over in-flight wifi.

I would hazard a guess that the main problem with in-flight wifi is that it is going to DPI'd beyond recognition.

So you're never going to know what is "real" packet loss and what is the DPI saying "computer says no".

The Sandvine/Procera[1] system that many (most ?) airlines use is an ML-based DPI that looks at absolutely everything in an effort to correlate obfuscated traffic to the actual flow. IIRC they claim 98% accuracy.

[1] https://www.sandvine.com/

j / k navigate · click thread line to collapse