Re: Tech update avoiding legacy code
Re: Tech update avoiding legacy code
- Subject: Re: Tech update avoiding legacy code
- From: SevenBits <email@hidden>
- Date: Fri, 14 Aug 2015 13:31:11 -0400
On Fri, Aug 14, 2015 at 12:42 PM, Jens Alfke <email@hidden> wrote:
>
> > On Aug 13, 2015, at 11:27 PM, Appa Rao Mulpuri <email@hidden>
> wrote:
> >
> > Thanks for the priority order. In GDC Vs ARC, GCD is the first one to opt
> > unless if you are app has more memory leaks. Correct me If I am wrong.
>
> ARC will simplify your source code, make new code easier to write, and
> make memory issues (leaks, crashes due to messaging dealloced objects) less
> likely. Once I switched I couldn’t imagine how I worked without it.
>
> GCD is useful if you make heavy use of concurrency in your app and need
> all the performance you can get. Not all apps will need it. If you’re using
> NSOperationQueue, you’re already taking advantage of GCD on OS’s that
> support it.
>
> One thing we both forgot to mention is blocks — I can’t remember, can you
> even use blocks in an app targeting 10.5? If not, those would be a huge,
> huge reason to drop support. Possibly bigger than ARC. Blocks make the
> language so much more flexible, even without GCD.
>
Amen.
>
> —Jens
> _______________________________________________
>
> 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
>
_______________________________________________
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