Re: multithreaded vs ...?
Re: multithreaded vs ...?
- Subject: Re: multithreaded vs ...?
- From: Greg Titus <email@hidden>
- Date: Mon, 18 Feb 2002 13:24:00 -0800
All perfectly reasonable. (Except maybe legal costs of complying with
the license - not much there to comply with, so any costs should be near
zero.) Still, makes sense.
Thanks for the response,
--Greg
On Monday, February 18, 2002, at 12:20 PM, email@hidden wrote:
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?
_______________________________________________
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.