However, that's not all of it. The iOS teams wouldn't touch the GC with a 10 foot pole, even had it worked, and with good reason. As the parent poster pointed out, GCs make performance and memory consumption unpredictable, especially on memory-constrained devices.
And yes, phones are memory-constrained, despite the 1/2 - 1GB of memory, because you are also managing some potentially very large assets (retina class images, ...). Especially without virtual memory, where having an unexpected spike in memory consumption can get you killed, having unpredictable memory consumption is a non-starter...and the pain you have to go through on Android to avoid GC problems is significant (for example real-time OCR via the video camera overlaid onto the video stream).
It's interesting that Android appears to be moving away from JIT to AOT with libart, I am very curious as to how that works out. My guess is that at least a subset of developers, those with stringent requirements, would also welcome more predictable memory management solution.
WP7 was full .NET with JIT.
WP8 is WinRT/.NET with AOT compilation.
Both seem to perform much better than Android and on par with iOS.
Although I do conceded that on WP8 there is a mix of reference counting(WinRT) and GC (.NET).
Google was supposed to present more information about ART at FOSDEM, but they canceled the presentation on the last minute. So still no information what they plan there, besides AOSP source code.
Xerox PARC systems already had GC enabled programming languages (Cedar/Lisp/Smalltalk) and they surely were less powerful than today's phones.
- Lisp OS
- Smalltalk OS
- Mesa/Cedar (a GC enabled systems programming)
Plus the underlying C part, didn't allow for more than a plain conservative GC.
ARC works by generating the retain/release calls the developers would write anyway with NeXTStep/Cocoa framework.
So while it is a good solution for Objective-C, it isn't because it thrumps GC, but rather due to Apple's failure with a stable GC.