Re: cursor ills
Re: cursor ills
- Subject: Re: cursor ills
- From: robert l clair <email@hidden>
- Date: Thu, 2 Oct 2003 17:43:16 -0400 (EDT)
Whoops. I forgot the golden rule. Never mention religion
in the same post in which you hope to get technical information.
#include "TheatricalSigh.h"
I try and avoid arguing with true believers, but several points:
>
Hogging the CPU for a lengthy
>
mount of time without responding to events is considered bad form
>
for an application on a modern, pre-emptively threaded, multi-tasked
>
OS.
Hogging the CPU and not responding to events are not the same thing.
It is rather the point of _pre-emptive_ multi-tasking that it prevents
you from hogging the CPU. (Am I accidently going to start an extensive
discussion on defective scheduling algorithms :-) ? )
>
It's a feature, not a bug. It's Apple's way of telling you to
>
rethink your application's design, instead of messing about as you
>
would have done on those old single-tasked OSs
I was reporting on the experiences of a number of "normal" users (mostly
artists and musicians). It wasn't my application they were complaining about.
And inflicting pain on your users/customers is a rather questionable way
of "enforcing" "good" design.
And aside from a brief and extremely unpleasant experience with
windows98 I have never worked on a single-tasked OS.
>
In the good old MultiFinder days, Apple tried by asking nicely with
>
their cooperative multitasking. That didn't work, so now they just
>
force you to do the right thing by otherwise forcing the beach ball
>
upon you.
At the risk of offending various long time Mac people on the list: I don't
know nor do I care to know anything about pre OS X macs.
The problem with this (and various other B&D approaches to software
and life) is that unfortunately in the real world one size does not
fit all. It is a nice thought that the user should be able to work
while the difficult things happen in the background - but sometimes
it just doesn't work that way. Consider a drawing/paint program.
For a large design the screen redraw may become slow. But the
appearance of the screen is pretty much the most important thing
here. While I'm sure you can contrive a case, in fact there is
very little you useful you can do (other than quit) until the screen
redraws, whether or not you are spinning the event loop. Artists in
general do not like to draw blindfolded even if it is theoretically possible.
.....Bob Clair
-------------------------------------------------------------
The Confusion is the gradient of the Potential for Confusion.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
| References: | |
| | >cursor ills (From: robert l clair <email@hidden>) |