Re:Common App Rejections
by gurkendoktor on Monday September 01, 2014 @03:17AM
(#8251825)
> it's just harder to introduce crash bugs in Java than Obj-C
I am not convinced. ObjC pointers are a lot safer than C pointers under ARC, and sending messages to nil won't even crash. It's almost more likely to have bloody AutoLayout crash your app :)
ARC is still awfully fiddly. Between all the bridging casts that are often necessary and the interaction with strong/weak/etc. modifiers you can put on properties, it's really easy to crash or leak memory with ARC. It's an improvement I guess, but I'm not sure it's much of one, because it lulls people into thinking they don't need to understand the underlying reference counting.
Re:Common App Rejections
by gurkendoktor on Tuesday September 02, 2014 @04:01AM
(#8256276)
I agree that it's terrible in theory, but it I've rarely had a memory bug slip into the App Store. Would love to see statistics from HockeyApp or others on reasons for app to crash.
I've only found statistics about the number of crashes: http://www.forbes.com/sites/tomiogeron/2012/02/02/does-ios-c...
iOS is clearly ahead when it comes to anything having to do with multimedia but for a very large class of apps these days it's either a tossup or a win to Android. iOS 8 will probably close the gap to some degree because it allows devs to hook into the OS to a degree that was never possible before but I also expect Android apps to improve now that people can afford to ignore 2.x and the baseline for cheap phones has been raised by the Android One program.