git ssb

0+

Grey the earthling / gkn.me.uk



Tree: 09853b2cb333cee284b5dd42cb21a933dbdc1b66

Files: 09853b2cb333cee284b5dd42cb21a933dbdc1b66 / content / computersdontlisten.md

1444 bytesRaw

title: > Computers Don't Listen date: 2005-02-20 12:53 status: published description: > Remember, folks, hardware is the part you can kick.

tags: computers


<p>
It's the old adage of the technophobe and we usually dismiss it as foolishness. Let's be fair - they couldn't tell a JPEG from a dongle. But they're right - computers <em>don't</em> listen. They always seem to be doing something more important than listening to you, the nominal user. </p>
<p>
The reason is a major design flaw in all operating systems - they give too much priority to doing things quickly. For example, if I'm moving twelve million files from a floppy disc to my hard drive, the computer might be a little slow, as a matter of course. But why need this be so? I, for one, would prefer if the computer paused doing that for a second in order to move the mouse pointer when I tell it to. </p>
<p>
Computers should be programmed so that the top priority is responding to the user. I don't mind if a <q>working</q> indicator has to be substituted for genuine progress - at least the computer would seem to be responding. When I move the mouse, the computer should drop everything in order to comply with my instructions. It should ensure that my music continues to play smoothly, then that the visualiser displays smoothly. Then if there's spare processor power - and only then - should it go about completing background operations like file moves. </p>

Built with git-ssb-web