To view parent comment, click here.
To read all comments associated with this story, please click here.
While you are technically correct, your argument is a bit facetious on the grounds that any bug can be converted into a feature, simply by stating intent.
For instance, I often joke with QA that bug X is actually a feature. If it's deliberate, then it can't be a bug right?
Bottom line though, if your software breaks other installed software, then that's a bug in my opinion, whether it is intended or not.
Guess all antivirus software are bugs then.
If my software breaks other software installed under the same OS then, yes, it might be a bug. If my software causes an entirely different OS to have issues then that is not something I am ever going to worry about. Expanding the potential problem domain of my software to include every OS that might conceivably ever be installed on a computer, and attempting to test against that domain, would be asinine.






Member since:
2006-02-01
Nice classic strawman argument there, "You dislike item A so I'm incorrect for pointing out issues with statement B." The two items are in no way related. I'm not defending Microsoft, I'm pointing out that the author's statement of that functionality being a bug is incorrect. Regardless of who makes the software or how many people dislike the way it behaves the feature being discussed is, within the bounds of its design, not incorrectly implemented. Whether the design is flawed or not is an entirely different argument.