Re: multithreaded vs ...?
Re: multithreaded vs ...?
- Subject: Re: multithreaded vs ...?
- From: email@hidden
- Date: Mon, 18 Feb 2002 12:20:45 -0800
apparently they don't want to build in dependencies on third party
libraries to manage risk. large third party code bases are subject to
changes outside our scope of control. (the same is true of apple
libraries, we are stuck with those, and they get distributed with every
mac) it also adds to the support burden. a second, even more poorly
documented, (as hard as that is to believe) set of api's is something we
don't want to have to train every new employee on. it adds to the size
of our downloaded application. it adds legal costs for understanding,
complying with the license. it brings a lot of code into our
application that we're not using. i'm sure there are more reasons...
On Monday, February 18, 2002, at 12:08 PM, Greg Titus wrote:
Just curious, what is your financial backers' reasoning here?
On Monday, February 18, 2002, at 11:45 AM, email@hidden wrote:
I was suggesting that Apple might want to have such an api in the
product they are asking us developers to use.
My financial backers are simply not interested in shipping omni
framework based products.
On Monday, February 18, 2002, at 11:39 AM, Erik M. Buck wrote:
Something like performSelector, but
performSelectorFromYourRunloopInYourThread...
Good news. Exactly that exists. See the Omni frameworks.
_______________________________________________
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.