Re: Threaded drawing
Re: Threaded drawing
- Subject: Re: Threaded drawing
- From: 2551 <email@hidden>
- Date: Thu, 12 Dec 2013 19:44:53 +0700
OK, OK, point taken.
I think I'll print that list (and Uli’s caveat) and hang it on the wall, right next to the space I use for banging my head when struggling with Cocoa… :p
On 12 Dec 2013, at 18:46, Uli Kusterer <email@hidden> wrote:
> On 11 Dec 2013, at 16:01, Jens Alfke <email@hidden> wrote:
>> On Dec 11, 2013, at 4:39 AM, 2551 <email@hidden> wrote:
>>> It’s certainly seemed the case to me that I would have probably spent less time just writing my own code from scratch than I spend trying to figure out how half the methods I’m trying to use should be implemented.
>>
>> That’s probably not actually true; our experience of time is pretty subjective, and time goes by faster when you’re in a ‘flow’ state than when you’re trying to figure out something new.
>>
>> Even if it’s a bit faster to write your own code, using the system APIs is probably still a win because
>> (a) their implementations are almost certainly better debugged and more performant than your brand-new unused code;
>> (b) they will be improved and maintained by other people over time, saving you the trouble;
>> (c) they’ve been designed to be reusable, so you’ll be able to use them quickly in your next project;
>> (d) you can later hang out here explaining the APIs to noobs and make yourself look like a guru (or better yet, write books) ;-)
>
>
> Let's preface that with the statement that I agree with your conclusion.
>
> Using Apple's code generally saves a lot of hassle and work because your code has only you doing QA. Apple's code has all of Apple, plus you, plus everyone else outside Apple who uses this API doing QA. It's bound to be more solid. That said, Apple's code still has only whatever team at Apple is responsible for that code fixing it. Only they have the source code.
>
> So occasionally, when a piece of code isn't or stops being a priority for Apple, item (b) above can actually be a liability. Still, we've seen how people circumvent that with sync code and CoreData. People first use Apple's code, getting a leg up and a release out the door and money in their coffers, and can then afford to fund their own version.
>
> -- Uli Kusterer
> "The Witnesses of TeachText are everywhere..."
>
>
>
_______________________________________________
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