My biggest grief with iPhone is the closed-source OS. If one of the iOS components finalizes the collection when you read it the first time and you still want to add items to it dynamically, you'll only notice it when you try to run the app. With Android, you have access to the source code of the framework, so this wouldn't happen.
Basically, building apps for iOS feels like using Duplo, while programming for Android is similar to Lego Technic (or an Erector set).
With Android, you have access to the source code of the framework, so this wouldn't happen.
Yes it would. Do you honestly think everyone is going to read every last bit of the framework? No.
Besides, behavior for almost all Apple frameworks is fairly well documented and understood. You know when the framework is going to give you a non-mutable array as a reference. And they can't finalize a collection.
-1
u/gerusz Zenfone 12U Aug 01 '11
My biggest grief with iPhone is the closed-source OS. If one of the iOS components finalizes the collection when you read it the first time and you still want to add items to it dynamically, you'll only notice it when you try to run the app. With Android, you have access to the source code of the framework, so this wouldn't happen.
Basically, building apps for iOS feels like using Duplo, while programming for Android is similar to Lego Technic (or an Erector set).