Xref: utzoo comp.sys.ibm.pc:28739 comp.sys.amiga:33734
Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!husc6!bloom-beacon!apple!motcsd!xdos!doug
From: doug@xdos.UUCP (Doug Merritt)
Newsgroups: comp.sys.ibm.pc,comp.sys.amiga
Subject: Re: OS/2 vs AmigaDOS
Message-ID: <281@xdos.UUCP>
Date: 13 May 89 05:58:43 GMT
References: <5664@microsoft.UUCP> <6793@cbmvax.UUCP> <2948@rti.UUCP>
Reply-To: doug@xdos.UUCP (Doug Merritt)
Followup-To: comp.sys.ibm.pc
Organization: Hunter Systems, Mountain View CA (Silicon Valley)
Lines: 28

In article <2948@rti.UUCP> bcw@rti.UUCP (Bruce Wright) writes:
>
>I have *NEVER* heard anyone complain because their {machine, operating
>system} was too fast!

Naturally. Although in a different area it happens: I read a paper
some years ago discussing problems with an experimental user interface
that was too fast...they had hot special purpose hardware, and found
that when the display changed it often happened too fast to notice,
leaving users confused, and taking several seconds to re-orient.

At the time I said, "wish we had problems like that!" (I was using
9600 baud vt220's on Intel 310's: 286 with 4-6 users running Xenix, blech).

Since then I've experienced this problem frequently, with Blitz on
the Amiga, and various software on Suns. It actually is helpful to
have some finite-time transition to help cue the perceptual system
to the fact that a change occurred. This is one of the charms of wicon.

This is going to be more and more of an issue in user interfaces in
the years to come; y'all be sure to keep it in mind when writing
software!
	Doug
-- 
Doug Merritt		{pyramid,apple}!xdos!doug	doug@xdos.com
Member, Crusaders for a Better Tomorrow		Professional Wildeyed Visionary

"Of course, I'm no rocket scientist" -- Randell Jesup, Capt. Boinger Corps