Re: Processes vs. Threads in Cocoa software architectures
Re: Processes vs. Threads in Cocoa software architectures
- Subject: Re: Processes vs. Threads in Cocoa software architectures
- From: "Shawn Erickson" <email@hidden>
- Date: Wed, 6 Sep 2006 14:45:47 -0700
On 9/6/06, Erik Buck <email@hidden> wrote:
Look, just don't use multiple threads OK.
*rolls eyes*
Can we stop with the absolutes... every tool has its use and every
tool can be misused... learn the tools and make decisions on what to
use when based on what your goals are.
I wonder if you realize that Core Graphics color correction of images
before display will automatically utilize multiple threads (sensibly
scaled to the number of processors in your system). If this was spun
off to a separate process it would easily underperform what currently
takes place. Same goes with various functions provided by the
Accelerate.framework, Core Image, Core Audio, etc.
In other words Apple utilizes multiple thread in YOUR application all
the time. If they can do it surely you can learn to do it as well.
You either value memory protection or you don't.
As soon as you have ONE thread in your process your can screw up your
own processes memory just as bad as you could with multiple threads.
Anyway what does this have to do with Cocoa?
-Shawn
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden