Reminds me of a problem Microsoft has with Word or with some versions of it. Seems if you load a badly formed document or one incorrectly formed, instead of Word saying the document is damaged, it quits. Microsoft claims this is correct behavior that is intentionally designed that way.Ice Cream Jonsey wrote:No, it's a bug, asshole."Thanks for the reports. I want to assure you this isn't a bug, it's working as intended," said a Google worker going by the name nealem.
To quote someone I know, "No, it's a bug, asshole."
A "bug" is any form of undesirable behavior which makes the product less useful. "lLess useful" in this case can be anything from minor error behavior to complete unusability, since "less useful" is potentially anything below 100%.A certain kind of developer thinks that the definition of a bug is unintended consequences or unexplained actions. It's not. You can intentionally make your app die every sixty seconds. It still means it's buggy as shit.
Now, if the bug is desirable behavior but the manufacturer doesn't want it to have that behavior, you can bet that gets fixed in lightning speed. There was a bug in the signed code system for the original XBox that, if you loaded a corrupted save game for a certain game - I think it was one of the James Bond licensed games, but don't hold me to that - it would allow you to bypass the mandatory signed code requirements, and replace the dashboard with one particular piece of software not lauthorized by Microsoft, that piece of software being the Linux Operating System. The change lost you the dashboard and the ability to use XBox live while you had Linux on the 'Box, but was completely reversible. So you could install a running version of Linux on a $300 XBox, which, is sold at a loss and Microsoft did not like this.
While there were a number of "ring of death" errors and other problems that plagued the XBox that didn't get fixed, Microsoft "with all deliberate speed" fixed this "bug" in the XBox with lightning rapidity.