3 ms·
> But saying "Okay, but we're not responsible for damages" will not fly with regulators, legislators, public opinion or the integrity of their brand. Why not?
by snowwrestler 10y ago
> But saying "Okay, but we're not responsible for damages" will not fly with regulators, legislators, public opinion or the integrity of their brand.
Why not? It flies just fine now with physical goods. If someone hand-builds their own bicycle wheel, and installs it on their bicycle, and then the wheel breaks and they crash... no one is blaming the bike manufacturer. No one is saying "that bike company should have welded the safer wheels on and issued a license prohibiting wheel alterations."
Everyone gets that the customer took the liability in their own hands once they started using their own hands to modify the product. It's the classic trade-off of freedom vs. security.
This ability to allocate liability to the customer is part of what we DO need for software, IMO. Right now there is a popular perception that software cannot be modified or interacted with by anyone but the company who wrote it. I don't think that has to be true forever though.
- snrplfth 10y agoSee my answer to AnthonyMouse below for my thoughts on this. I'm not saying that it's ideal for Tesla to lock down the system like this. I'm saying that, given the risks they face, in terms of legislation, regulation and public opinion, their approach is very understandable.
- snowwrestler 10y agoI agree that it's understandable in the current environment. I'm interested in thinking about how the environment would need to change to give us the company behavior we want.
- snrplfth 10y agoYou mean for society to quickly turn into technophile contractarians? I'm not holding my breath, personally.
- snowwrestler 10y agoI'd be happy to start with a framework that permits the technophiles who already exist to work on the products they already own.
- deleted 10y ago[deleted]