Linked by Thom Holwerda on Tue 1st Dec 2009 23:53 UTC
Thread beginning with comment 397954
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.
so if a user operates an object incorrectly and the object malfunctions, it's the object's fault?
No. If a manufacturer makes a product such that it's particularly easy for users to render it useless by mistake then it's the manufacturer's fault that so many such products get rendered useless. (Of course the primary responsibility still lies with the one operating the product, but that's irrelevant since this obviously is a case with more than one fault.)
Apparently you've never known anyone killed by a drunk driver. Douchebag.
Nobody drives drunk by mistake.
Along similar lines, it's not MS's fault if the OS fries as a result of the user switching non-hotswap RAMs on-the-fly. That'd be against the specs and not something one would do by mistake.
And there's no reason for name-calling. Try to be civil.




Member since:
2005-09-13
so if a user operates an object incorrectly and the object malfunctions, it's the object's fault?
Apparently you've never known anyone killed by a drunk driver. Douchebag.