Linked by Thom Holwerda on Fri 27th Apr 2012 22:00 UTC, submitted by koki
Thread beginning with comment 516051
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: So, let me get this straight
by WorknMan on Sat 28th Apr 2012 06:31
in reply to "RE[4]: So, let me get this straight"
It also helped that BeOS native apps were small and clean, and thus would launch so fast that you could practically disregard the delay entirely.
Yeah, we'll see what happens to 'small and lean' and apps popping up instantly if/when they start porting apps like Photoshop to it
hehe BTW: I tried clicking on menus in several apps in Windows, as well as the Start menu. I don't know how long it took for them to appear, but I could not perceive any kind of delay.
RE[6]: So, let me get this straight
by The123king on Sat 28th Apr 2012 11:31
in reply to "RE[5]: So, let me get this straight"
RE[6]: So, let me get this straight
by looncraz on Sat 28th Apr 2012 15:33
in reply to "RE[5]: So, let me get this straight"




Member since:
2005-07-24
Humans can detect incredibly minute delays - particularly if they have muscle memory trained - there delays as little as 10ms can cause a slightly sensation of a disconnect, though that is at the very extreme (such as an audio sync problem, where the brain senses a slight disconnect).
When it comes to UI responsiveness, BeOS could open a menu in about 50ms when Windows was taking 250-300ms, this is a very large discrepancy in performance.
It also helped that BeOS native apps were small and clean, and thus would launch so fast that you could practically disregard the delay entirely.
And all that on lowly pentiums/II...
--The loon