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

Did you ever wonder why C++ apps crash more than Java apps?

They don't. You are talking out of your ass.

Reply Parent Score: 2

MORB Member since:

You're the one who made an outlandish claim, not me, therefore the burden of proof is on you. The very fact that you didn't post any evidence of your arbitrary assessment is why I qualified it as talking out of your ass.

So, I eagerly await you to post your own research. It shouldn't take long, since you claim such research is simple.

Since I'm in a good mood though, I'll warn you about a couple of pitfalls that may undermine your research credibility:
- anecdotes don't count (things such as "I use this thing written in C++ and it crashes all the time")
- any comparison of the rate of crashing between java and C++ application must be adjusted to take into account the much larger amount of C++ applications compared to java applications.

Let's see you research. I'm sure it will be enlightening.

Edited 2012-02-04 11:35 UTC

Reply Parent Score: 2

JAlexoid Member since:

Well... Technically they do. But mostly because it's easier to screw up a C++ app and/or memory management.

Reply Parent Score: 3

bnolsen Member since:

It's easier to screw up the design of a java program and get away with it. c++ punishes bad programming practices a lot harder.

Reply Parent Score: 5

Elv13 Member since:

Java is not native so when it segfault, it just throw and exception and go on. While it may corrupt the application state to the point it still explode shortly after, it is not because of the fault itself, but the consequences of it. C++ application wont survive calling a method from an invalid pointer, array overflow and division per 0. It will close instantaneously.

That said, Java do suck and I code in C/C++/Lua when I can.

Reply Parent Score: 2

MORB Member since:

I don't think a buggy java application doing the things you mention will survive it any better than C++.

I doubt many java developers setup exception handlers to recover gracefully (or at all) from a division by 0, an out of bound array access or trying to dereference a null pointer.

Reply Parent Score: 2

BeamishBoy Member since:

C++ application wont survive... division per 0. It will close instantaneously.

Handling a division-by-zero error in C++ is trivial. Subclass std::runtime_error and handle it like you would any other exception.

Reply Parent Score: 1