N
Nick Maclaren
|> > Yes, but that is in response to relatively coarse interactions,
|> > such as individual commands. A 100 millisecond delay on
|> > character deletion is a real pain, and it makes many GUI
|> > operations (such as drag to position) extremely stressful
|> > and slow. With such things, the maximum delay you can tolerate
|> > without irritation is down in the 10-20 millisecond range.
|>
|> I've found long feedback delays (multi-second) are perfectly
|> acceptable so long as they occur when the human can confidently
|> type-ahead or is satisfied to wait (complex command executing).
|>
|> Delays become irritating when the visual feedback is required
|> (another cursor keypress?) especially when they are inexplicable.
Precisely, on both counts. A 3 second delay between complex
commands is vastly less irritating than a 0.1 second delay between
characters or in responding to a cursor drag.
|> > This is one reason that I stick with the Bourne shell in
|> > Unix; it is the only one that uses cooked mode, and therefore
|> > line building is done in the kernel. From choice, I use an
|> > environment where it is done locally (i.e. on my desktop or
|> > equivalent) when executing commands obeyed on a remove system.
|>
|> I do not believe SSH has any such line-by-line protocol
|> as TELNET does.
No, and I wish that it did. However, I mean to investigate why
it works as well as it does, some day when I have plenty of time.
But you can still build lines locally and execute them remotely
when writing scripts that use SSH.
Regards,
Nick Maclaren.
|> > such as individual commands. A 100 millisecond delay on
|> > character deletion is a real pain, and it makes many GUI
|> > operations (such as drag to position) extremely stressful
|> > and slow. With such things, the maximum delay you can tolerate
|> > without irritation is down in the 10-20 millisecond range.
|>
|> I've found long feedback delays (multi-second) are perfectly
|> acceptable so long as they occur when the human can confidently
|> type-ahead or is satisfied to wait (complex command executing).
|>
|> Delays become irritating when the visual feedback is required
|> (another cursor keypress?) especially when they are inexplicable.
Precisely, on both counts. A 3 second delay between complex
commands is vastly less irritating than a 0.1 second delay between
characters or in responding to a cursor drag.
|> > This is one reason that I stick with the Bourne shell in
|> > Unix; it is the only one that uses cooked mode, and therefore
|> > line building is done in the kernel. From choice, I use an
|> > environment where it is done locally (i.e. on my desktop or
|> > equivalent) when executing commands obeyed on a remove system.
|>
|> I do not believe SSH has any such line-by-line protocol
|> as TELNET does.
No, and I wish that it did. However, I mean to investigate why
it works as well as it does, some day when I have plenty of time.
But you can still build lines locally and execute them remotely
when writing scripts that use SSH.
Regards,
Nick Maclaren.
