Re: [Q] Why is the threading and UI updating designed to be done only on a main thread?
Re: [Q] Why is the threading and UI updating designed to be done only on a main thread?
- Subject: Re: [Q] Why is the threading and UI updating designed to be done only on a main thread?
- From: JongAm Park <email@hidden>
- Date: Wed, 14 Mar 2012 13:21:57 -0700
Well, I'm sorry if I confused you.
BTW, "common advice to avoid threading" doesn't mean that threading
should not be used.
Just like salt, if it is used for right occasion, it is very good.
However, when there are another way not to use thread but just to use
threading because "it can be used" is not right.
I think that is the meaning of "common advice to avoid threading".
So is "Necessary Evil". I saw this expression in one of Microsoft's
Windows Programming book in early 90's.
:)
On 3/14/2012 10:25 AM, Scott Ribe wrote:
When you said "just like threading itself" it seemed to me that you were echoing common advice to avoid threading, and I don't necessarily agree with that because threading can be very useful and I use it extensively. I guess I would agree with advice to always consider carefully before going to multi (or more) threads.
On Mar 14, 2012, at 11:09 AM, JongAm Park wrote:
Well.. Yes. I understand what you mean. I just added the threading stuff in the discussion.
Probably it is due to my English? I thought "just like..." could serve to express my understanding of your concern for "UI main thread and other threads" and just provided analogous thing. ( Arr.. my English.. )
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden