3 ms·
What if I change the firmware? What if I change the hardware? Where is the line and why distinguish between a pure hardware product and a combined product tha
by mulmen 9y ago
What if I change the firmware? What if I change the hardware? Where is the line and why distinguish between a pure hardware product and a combined product that uses both hardware and software? Why should we legislate engineering decisions?
- wtallis 9y agoI don't think any of those are productive questions. If you alter firmware that is usually unchanged over the life of the product (as for a desktop graphics card) and you specifically edit the rules it contains for thermal throttling, then you are obviously liable for the lump of slag that you end up with. Likewise if you're making hardware modifications that compromise the thermal management capabilities. In either case, it will be pretty easy to show after the fact that the product was modified, and that your modifications were probably related to the failure. None of that applies when the host software is responsible for preventing hardware damage. As I've explained, relying on software running inside of Windows to prevent hardware damage is asking for trouble even without user intervention. You may also notice that I'm not advocating for "legislating engineering decisions"; though there are plenty of situations where engineering decisions obviously should be determined by legislation, this is more a question of after the fact liability to be worked out by the courts, which are generally pretty good at figuring out whether to place the blame on a user or on the engineers.
- bradstewart 9y agoIt all boils down to personal responsibility which, admittedly, doesn't seem to be a particularly valued trait these days. Both you and the manufacturer know if your customization was the likely cause of a failure or not. Life would be much simpler if everyone just admitted that and moved on.