OTOH when developing for Apple platforms there's not a huge loss when developing only for iOS 6+ (85% - 90% of users), whereas on Android you're pretty much required to target very outdated versions of Android as well. For example we target Android versions starting with Froyo.
I don't think the lipo tool will ever be regarded as hack. It's pretty much required when supporting multiple architectures / instruction sets. At some point there will likely be a ARMv8 architecture (if it doesn't exist yet).
Also many libraries make use of lipo to create convenient static binaries that can be used both in the simulator as well as on the device.
fpgeek|13 years ago
Google has been focused on enabling backwards compatibility since at least Android 1.5 (well before anyone knew how Android updates would play out in practice): http://android-developers.blogspot.sg/2009/04/backward-compa...
Meanwhile, Apple seems to prefer to make achieving backwards compatibility as hard as possible (short of explicitly banning it).
wsc981|13 years ago
fnayr|13 years ago
Still it is a hack that Apple could start disallowing at any time.
wsc981|13 years ago
Also many libraries make use of lipo to create convenient static binaries that can be used both in the simulator as well as on the device.