Forgot your password?

typodupeerror

Comment: Re:Bad apps crash. News at 11. (Score 1) 358

by jeremyp (#38937089) Attached to: iOS Vs. Android: Which Has the Crashiest Apps?

The Skype app crashes all the time, and it's almost always iOS's fault. If you go through the diagnostic logs, you'll see that almost every time that Skype "crashed" it's because it's either using "too much memory" or because it "didn't respond fast enough."

So it's actually Skype's fault. iOS issues low memory warnings before it kills apps. Well written apps respond to that.

Imagine if Windows killed Firefox every time it started (Not Responding) - that's iOS in a nutshell.

Maybe the programmers would put more effort into making FireFox more responsive. Actually, sometimes I wish OS X would do that to Safari. I'm seeing far too many beach balls at the moment.

The other reason apps crash all the time on iOS is because they're written in Objective C. And while there are API tools to make memory management easier, it's still far easier to shoot yourself in the foot and seg fault with Objective C than it is with Java, where the worst you can do is get a NullPointerException or an ArrayIndexOutOfBoundsException.

NullPointerException and ArrayIndexOutOfBoundsException are both equally as bad as seg faults. They both indicate severe programming bugs and it doesn't mean they are not serious just because the program can catch them and attempt to carry on.

Comment: Re:How to poke a dead body (Score 1) 545

by jeremyp (#38686786) Attached to: How To Get Developers To Document Code

There's nothing wrong with the carrot and stick metaphor. In the metaphor, the reward is represented by the carrot, the punishment is represented by the stick and the person is represented by the (implied) donkey, that likes eating carrots and dislikes being beaten with a stick. It has nothing to do with the carrot on a stick metaphor.

Comment: Re:Just another... (Score 1) 286

Despite your mean-spirited assertion, clicking the link DOES NOT provide any information about whether this is market share by: total browser views, unique browser, etc. It just asserts the nebulous term "market share" without any real explanation of what that meant or how it's calculated.

The methodology is explained in the site FAQ.

"If the code and the comments disagree, then both are probably wrong." -- Norm Schryer

Working...