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 505846
To view parent comment, click here.
To read all comments associated with this story, please click here.
WorknMan
Member since:
2005-11-13

The majority of these iOS apps crashes can probably be attributed to bad programmers that can't manage their memory properly.


You know, it's funny... if somebody makes a comment about how many desktop Java apps run like ass, people are quick to blame programmers as well. Surely, it CAN'T be the languages that suck ;)

Reply Parent Score: 2

warhawk Member since:
2012-02-03


You know, it's funny... if somebody makes a comment about how many desktop Java apps run like ass, people are quick to blame programmers as well. Surely, it CAN'T be the languages that suck


Have you considered upgrading your Pentium with 1 GB of RAM? As for languages that suck, well, they really don't get much worse than Objective C.

Edited 2012-02-04 00:20 UTC

Reply Parent Score: 0

Bill Shooter of Bul Member since:
2006-07-14

Well, I would upgrade my pentium to 1 G, but it doesn't have any more memory slots & maxes out with two 64 mb sims.

Reply Parent Score: 2

krreagan Member since:
2008-04-08

Except for C/C++, Java

Reply Parent Score: 0

darknexus Member since:
2008-07-15

As for languages that suck, well, they really don't get much worse than Objective C.


Couldn't agree more. A bastardized mix of C and SmallTalk, and neither bit bares even the slightest syntactic resemblance to the other. Even C++ is cleaner, and that's saying something. Why anyone thought the design of obj-c was a good thing I couldn't guess, and why Next (and as a consequence Apple) went with it is one of those mysteries we'll probably be wondering about forever.

Reply Parent Score: 4

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

sithlord2 Member since:
2009-04-02

"The majority of these iOS apps crashes can probably be attributed to bad programmers that can't manage their memory properly.


You know, it's funny... if somebody makes a comment about how many desktop Java apps run like ass, people are quick to blame programmers as well. Surely, it CAN'T be the languages that suck ;)
"

No, it's the programmers. You can perform bad memory management in every programming language (including java).

Ex:

In C/C++ if you don't release memory, you'll get memory leaks
In Java or .NET: If you don't dispose objects the GC will not re-use their memory, and will keep requesting new memory blocks from the OS with every new().

Memory management is the responsability of the programmer, not the language (despite what some Java or .NET folks say).

Reply Parent Score: 2