Linked by gsyoungblood on Tue 20th Jul 2010 18:01 UTC
Thread beginning with comment 434148
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2006-07-26
It sounds like your applications are making invalid assumptions and crashing as a result. This generally results from not looking beyond "it works on my machine" and not doing proper error checking nor checking if something exists before using it. While it is a lot easier to program that way, it doesn't produce high quality code.
Getting mad at your users for giving their honest opinion of your code is counterproductive. Rather than let your programs crash, pop up an error message explaining what it is that is lacking on their OS. Then your users will pressure the ROM makers to provide that functionality.