3 ms·
Honestly this sounds like a "if your computer weighs less than 5 tons and can fit on a desk, it's not a real computer" argument someone would have made 30 years
by gregmac 4y ago
Honestly this sounds like a "if your computer weighs less than 5 tons and can fit on a desk, it's not a real computer" argument someone would have made 30 years ago.
Reality is people use multiple different and mobile devices, roam across connections, and intermittently go offline. Building software and protocols that are designed around this is beneficial to every use case - even those using whatever you consider a non-"terrible computer" to be.
- superkuh 4y agoI don't believe you really think that. Not being able to keep a TCP connection open is not some trivial aesthetic or nostalgic issue. Pretty much all information transfer on the internet is over TCP.
- gregmac 4y agoWhat the OP was talking about, which I totally agree with, is protocols that can't tolerate interruptions to their connection. This can be done with TCP. When I worked in an office, I had the same issue as the OP - docking/undocking my laptop resulted in switching from wired to wireless, and connections (eg: SSH, RDP) would often drop. I ended up unplugging the ethernet at my desk and using wireless most of the time because it was just easier. What would help is protocols actually support the concept of a "reconnection" -- ie: a TCP session that has the same identifier or token as a previous one that lets it it silently resume instead of starting fresh with new authentication. This isn't even that hard to implement if designed in from the start.