On 11 Dec 2013, at 1:39 pm, 2551 <2551p...@gmail.com> wrote: > The commonality of this experience makes me wonder almost with everything I > try to do in Cocoa whether it really IS true as advertised that the > pre-written APIs make it easier than writing your own raw code all the way > down in C and Obj-C or whether the whole Cocoa edifice has turned into such a > monster that for anyone except the seasoned expert, quite the reverse is true.
Actually I think my experiences illustrated in this thread show the opposite. I started by attempting to write my own code (still in Obj-C) and it got moderately complicated before I gave up without showing any performance benefit (in fact the opposite). Using CATiledLayer, as badly documented as it is, was about 5 lines of code and actually worked in doing what I had been attempting to do all along. The problem for me was one of even realising that the class was a good fit for my situation. On the whole, using Cocoa is a huge benefit. Of course it’ll have some bugs, bad documentation, etc - in other words the same problems all projects have. The difference I suppose is that it has many knowledgable engineers working on it, it is extremely well-funded (in theory) and is more thoroughly debugged than pretty much anything you could write on your own of its size and scope. We do complain sometimes, and frustration isn’t uncommon, but let’s keep things in perspective. File radars, maybe we’ll get better documentation. —Graham _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
