3 ms·
It seems to me that terms mostly had semi batch IO mindset. The basic unit is a chat, not a signal over time like `<sensor> down for half a second` which only m
by agumonkey 6y ago
It seems to me that terms mostly had semi batch IO mindset. The basic unit is a chat, not a signal over time like `<sensor> down for half a second` which only make sense for high frequency or real time user interactions.
- leoc 6y agoThe original ttys were literally Teletypes https://www.bell-labs.com/usr/dmr/www/picture.html https://www.bell-labs.com/usr/dmr/www/picture.html designed to send text directly to another Teletype over a phone line. As such they sent and received sequences of characters, not key events, yes. OFC these are also basically the same ASCII text streams that Unix pipes between shell commands and the file system.
- agumonkey 6y agoI get the legacy aspect both in internals of the time and usage. But I'm curious how to upgrade the old way to support finer grained interactions.
- imtringued 6y agoThat's simply not possible nor desired. It's like trying to think of a way to make ints support fractions in C without storing a second int for the denominator. What you really want is that SSH implements support for a remote keyboard so that the application on the other end can simply read local machine key events and this is as far away from "upgrade the old way" as possible.