Re: threads vs run-loops for keeping your GUI responsive
Re: threads vs run-loops for keeping your GUI responsive
- Subject: Re: threads vs run-loops for keeping your GUI responsive
- From: Markus Hitter <email@hidden>
- Date: Fri, 9 Dec 2005 20:28:28 +0100
Am 09.12.2005 um 19:26 schrieb Erik Buck:
It is so hard in a multi-threaded process that in my opinion it is
almost never justified to use multiple threads per process for most
types of application.
Doesn't each Cocoa app come with three threads by default already?
NeXTstep had some -becomesMultiThreaded method, so it was possible to
run a single-threaded app. Mac OS X phased this method out, due to
the changed background.
Having a working thread and a GUI thread is fine, IMHO, and fits
almost all of your discussion. In earlier days, you'd have used
signal handlers for this stuff.
In my opinion, the original reason for introducing threading was to
reduce process creation time, but process creation is so fast on
modern systems that the original reason is no longer valid.
Didn't you come across a programmer complaining "Why does Mac OS X
allow 1024[1] threads, only", yet?
Markus
[1] No, I don't know the real number and researching this number
won't enhance the discussion :-)
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
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