Argh! The Internet doesn't understand 64-bit.
Just listened to the Android Central podcast, and Jerry's comment sent me into a rage as he had zero understand of 64-bit and Apple's iOS support for 64-bit. And Jerry's supposed be to AC's tech nerd. Ugh, rage face. Shouldn't be surprised as those guys didn't understand how color works or multiprocessing either when the respective technologies started hitting smartphones.
What really sent me into rage was the iOS 7 64-bit support comments. It's as if they don't know anything about computing history. They said it fragments iOS apps and iOS basically can't be 64-bit as it has to ship on older devices too. Argh, the problem has been solved for 2 decades now.
1. iOS 7 will be 64-bit on the 5S. All of Apple's built-in apps will be 64-bit.
2. iOS 7 will be 32-bit on older devices and Apple's built-in apps will be 32-bit.
3. Only one "application" will be downloaded from the App Store. Each application (which is really just a folder) will have a 64-bit and a 32-bit binary; and, the appropriate binary will be loaded for the appropriate system.
4. This has actually been happening for years on iOS and for decades on Mac OS X reaching back to NEXTSTEP. For iOS 7, it has to support 32-bit Cortex-A8 (iPhone 4), 32-bit Cortex-A9 (iPhone 4S), 32-bit Swift (iPhone 5), and 64-bit Swift (iPhone 5S). There could be apps with 5 binaries in them, as I believe there are compiler targets for each of them.
5. There's an obsolescence issue for iOS 6 and older devices. Apple may not have implemented a multi-architecture binary format for it or have not supported the filtering for it in the App Store for people still on those devices. But that's not shocking either.
And ugh, the analogy Jerry used for 64-bit computing was horrible.