6 ms·

Fair points except that the prettiest UI doesn't always win - more productive, more flexible UIs that look decent enough do. And I don't think Android in itself

Fair points except that the prettiest UI doesn't always win - more productive, more flexible UIs that look decent enough do. And I don't think Android in itself has any limitation that prevents a developer from creating pretty looking apps. Also GC mostly is huge benefit when it is available - like everything it has its downside as you rightly pointed out, but I prefer that over having to remember to release memory in different code paths. Gives me more time to think about program logic. Plus you can always write native code in NDK when you want more control over object deallocation for performance critical code.

Xuzz 16y ago
You don't have to do that on the iPhone. There's this magic thing called "autorelease". Call it on an object, and it'll release itself (and its memory) sometime in the future, after the current call stack (probably sometime a few runloops ahead). Most things come pre-autoreleased for you, the only time you ever have to manage memory yourself is if you are storing it inside the instance variables of an object, at which point you just have to remember to add a line to the destructor to free it.