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: John Stiles <email@hidden>
- Date: Wed, 6 Sep 2006 18:45:37 -0700
On Sep 6, 2006, at 6:38 PM, Erik Buck wrote:
How many naive folks in this forum jump into threads without
understanding the issues ? How many Computer Science graduates can
write correct multi threaded code ? My anecdotal observation is
that at most 50% of recent CS graduates even know what a mutex lock
is let alone how to correctly use one.
I do agree with you here. All the same, how many CS grads know how to
use bindings and Core Data? ;)
Yes, some things are hard to do right, and threading counts. I've
seen code from smart people that had glaring thread issues. That
doesn't mean that nobody should ever use threads—just be cautious,
and if you're not sure that you know what you're doing, stop and ask
for help. And hey, that's what this forum is all about.
I do suspect that a lot of forum regulars here do know how to use
threads well, and get excellent mileage out of them, far more than
one would get via a multiple-process approach. And I also think that
in many cases, threads are a lot simpler than trying to get two
separate processes to communicate and play nice with one another.
_______________________________________________
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