ARC, worth it or not?

Question

When I moved to Objective C (iOS) from C++ (and little Java) I had hard time understanding memory management in iOS. But now all this seems natural and I know retain, autoreleas

Answer 1

Watch the WWDC video on ARC: https://developer.apple.com/videos/wwdc/2011/?id=323

Apple's official stance in that video is that all apps that can use ARC should use ARC. The video goes into why, and is an excellent overview of the technology, so I'm not going to repeat it all here.

Answer 2

Have you read Apple's documentation on ARC? It answers a lot of the questions you're asking.

Based on my experience, here's what I think:

1. Yes, it's simple. You definitely need to test your app after converting, though.
2. It can help reduce your app's memory usage and leaks, but it's not guaranteed to do that.
3. Yes. You'll want to test after converting to ARC.
4. You don't have to waste as much time thinking about and tracking down leaks. You can spend more time and energy on your app's actual code, rather than worrying about retain/release. Even if retain/release code is natural and easy for you, you're not infallible and you'll occasionally forget to release something. ARC doesn't forget.
5. If you're supporting iOS 4, you'll have to handle weak references, as ARC doesn't support those in iOS 4.

Answer 3

Here's my specific take on ARC:

1) XCode has "Convert to Objective C ARC" menu. Is the conversion is that simple (nothing to worry about)?

It's simple. It works. Use it. As Kevin Low points out though, you will need to go through and fix up the bits where you use Core Foundation objects. That will just require a healthy lashing of __bridge or __bridge_transfer though.

2) Does it help me in reducing my apps memory foot-print, memory leaks etc (somehow ?)

Nope, not really. OK, sort of. It will help reduce memory leaks where you have coded incorrectly previously. It won't reduce memory footprint.

3) Does it has much testing impact on my apps ?

None whatsoever.

4) What are non-obvious advantages?

The future. There'll be more to come on the bonus that the compiler taking an intricate knowledge of how objects are reference counted gives. For example ARC provides the lovely objc_retainAutoreleasedReturnValue optimisation already, which is very nice.

5) Any Disadvantage os moving to it?

None whatsoever.

Please take my word for it and start using ARC. There's no reason (IMO) not to, thus the advantages definitely out-weigh the disadvantages!

For an in-depth look at how ARC works to perhaps help convince you that it's good, please take a look at my blog posts entitled "A look under ARC's hood" - here, here, here & here.

Answer 4

1. If you're using Core Foundation or non-Objective-C code, then it's not as simple as you will have to manually go through your code and make sure all the casts between Objective-C and Core Foundation are bridged (if you have any casts). You'll also still have to manage memory for non-Objective-C code.

2. It's supposed to essentially take care of all memory leaks for you, since it automates the retain, release, copy, etc. So far, I've never had an Objective-C leak since switching to ARC.

3. No. Building might take a tad bit longer since it has to go through all your code and insert all the retain and release code.

4. Not sure if there are any. In the end, all ARC is, is an automator.

5. You will have to learn about bridged casts as well as you cannot build for anything lower than iOS 4.

In the end, it's definitely worth it. I was skeptical at first, but after watching the WWDC video where they explain how it works, I liked it more and more.

Answer 5

3) You should re-test your apps, but in my experience it will pretty much just work. Look at all the compiler warnings very carefully though!!!

4) Non obvious advantages: it's just really faster to code when you do not have to think about memory management. Perhaps that is obvious but the amount it helps still surprised me.

5) Disadvantages: Really the only disadvantage is having to turn off ARC for some third party libraries.

ARC has been so useful I simply will not code without it any longer. There's no reason to have to deal with all of that any more and it works well enough in practice.

Answer 6

Here's what you really need to know about ARC:

The compiler understands Objective-C and Cocoa better than you. I don't mean this as an insult; it understands it better than me. I think you could safely say it understands the rules better than all but maybe a dozen people worldwide. And it knows tricks to use them to a degree that you and I can't repeat, even if we understood as well as it does.

The rest is just details:

• You will write a lot less boring code. Code so boring it's easy to make mistakes.
• As a blended compile time and run time process, it has access to tricks that you don't.
  • It will a better a job of writing memory management code than you can, even if you write the theoretical perfect memory management code.
  • It will reduce "high tide" memory usage (somewhat) without any effort on your part.
  • With zeroing weak references, it's much easier to avoid crashes caused by dangling pointers.
• If you are starting a new application, stop thinking about it and just use it.
• If you have an existing application:
  • You will need to re-test it. You need to make sure you have no circular references.
  • If you have an existing application that targets iOS before iOS 5, zeroing weak references are not supported. You should seriously consider requiring iOS 5.
  • If you have an existing application that targets iOS before iOS 4, you can't use it at all. What are you thinking, supporting crap that old?!?
• In the last version of Xcode, it was not entirely bug free. It probably still isn't. But it's still worth using.