On Apr 17, 2012, at 12:28 AM, Graham Cox wrote: > Well, I don't find ARC to be necessary. I tend to assume it was added to > counter the argument from developers coming from other languages to iOS that > Objective-C is "old fashioned" and requires too much hand-holding on the MM > front that they are not likely to be used to. > > However, seeing as your email address contains apple.com, I'll accept there > could be more to it than that and I bow to your inside knowledge. I would say > though, that having been using Objective C productively for over 10 years > now, that I still find ARC something I have not needed. So far. I'm kinda > hoping that remains true, because it actually seems pretty complicated in > order to cover all the arcane use-cases and I'd rather stick to what I know > which has the overwhelming advantage of being really, really simple.
Myself, I’m becoming a fan of ARC just for the performance benefits. Particularly once the frameworks get converted to ARC, it’s going to result in a lot fewer autoreleased objects being created, which will not only cut down on overhead but also make Dave’s statement about not needing to worry about autorelease pools much closer to being true (in general, I find that users tend to get upset if your app grabs huge chunks of memory when it doesn’t need to, even if performance is good). Charles _______________________________________________ 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
