Linked by Thom Holwerda on Fri 3rd Feb 2012 23:43 UTC
PDAs, Cellphones, Wireless There's an article making the rounds right now about how applications on iOS crash more often than applications on Android. I'm not going to detail the entire methodology - the article itself does so - but it does raise an interesting talking point about how both mobile operating systems handle application crashes and updates.
Thread beginning with comment 505850
To view parent comment, click here.
To read all comments associated with this story, please click here.
JAlexoid
Member since:
2009-05-19

Are you implying that Java sucks?

That said, Java's Swing tool-kit was always a slow ram hog when used without proper knowledge.

Reply Parent Score: 2

warhawk Member since:
2012-02-03

Are you implying that Java sucks?

That said, Java's Swing tool-kit was always a slow ram hog when used without proper knowledge.


I'm implying that the gold rush on mobile apps has attracted sub par developers that write crash prone iOS apps because they don't understand memory management.

Reply Parent Score: 2

JAlexoid Member since:
2009-05-19

I'm pretty sure that Objective-C uses some kind of mem management... It's not just plain C

Reply Parent Score: 2

qbast Member since:
2010-02-08

Like Apple devs? Because right now most crashy app on my iPad is Safari.

Reply Parent Score: 2

adinas Member since:
2005-08-17

The problem isn't with the developers. They want to focus and making the app do what their imagining, why should they waste time on memory management? C# and Java prove you can develop without memory management.

Reply Parent Score: 2