4 ms·
> when a user was typing at a remote terminal, which used to be a pretty common use case in the 80's Still is for some. I’m probably working in a terminal on a
by SoftTalker 3y ago
> when a user was typing at a remote terminal, which used to be a pretty common use case in the 80's
Still is for some. I’m probably working in a terminal on an ssh connection to a remote system for 80% of my work day.
- dgoldstein0 3y agosure, but we do so with much better networks than in the 80s. The extra overhead is not going to matter when even a bad network nowadays is measured in megabits per second per user. The 80s had no such luxury.
- SomeoneFromCA 3y agoFirst world thinking.
- CamperBob2 3y agoNot really. Buildout in less-developed areas tends to be done with newer equipment. (E.g., some areas in Africa never got a POTS network, but went straight to wireless.)
- underdeserver 3y agoIf you're working on a distributed system, most of the traffic is not going to be your SSH session though.
- adgjlsfhk1 3y agothe difference is that with kb/s speed, 40x of 10 characters per second overhead mattered. now, humans aren't nearly fast enough to contest a network.
- admax88qqq 3y agoWhy? What do you do?
- atq2119 3y agoYes, but isn't the effect on the network a different one now? With encryption and authentication, your single character input becomes amplified significantly long before it reaches the TCP stack. Extra overhead from the TCP header is still there, but far less significant in percentage terms, so it's best to address the problem at the application layer.