3 ms·
> 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
by gurkendoktor 12y ago
> 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 :)
- deong 12y agoARC 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.
- gurkendoktor 12y agoI 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-crash-more-than-android-a-data-dive/ http://www.forbes.com/sites/tomiogeron/2012/02/02/does-ios-c...