on the other hand, if you know your old software is buggy and could cause fatal accident, you release a software update, but for some unknown reasons, the user keeps denying updating software, what would you do ?
It should be costly. You want to encourage companies to make better/safer products that have been well tested. The whole “Move quick and break things” is from the perspective of a completely nonessential social media service. They have no consequences when they break things, although even that has changed as every minute of downtime is lost revenue. Self inflicted financial pain is completely acceptable, if they choose to take that path. Car companies should not.
Just issuing a recall is not enough. There are countless reasons why someone does not return the product: They maybe simple not know, and there is no way to reach them.
That is why Samsung push update to disable note 7 even after recalling them.
> There are countless reasons why someone does not return the product: They maybe simple not know, and there is no way to reach them.
In Germany we let the Kraftfahrtbundesamt handle this. You are required by law to keep your address updated with the authorities, and all vehicles have to be registered to get a license plate. When a recall for safety reasons happens, the Kraftfahrtbundesamt writes a notification letter, and if you do not respond in time with evidence of having the recall issue remediated by a qualified shop (or doing it yourself and getting a sign-off from a licensed inspector), eventually they write to your local DMV office that can ban your vehicle from the roads, and if you miss that the police shows up at your home and physically removes the license sticker from the table.
And heaven forbid you get actually caught driving the car after having gotten the notification letter from your local DMV. That's automatically felony territory. Our authorities really, really do not mess around.
As American, I assume most the thread above was assuming US locale and it Seems like a solid case of the all too common “impossible by US status quo standards” when in fact the solution can be quite simple we just lack the imagination or willingness to see what worths elsewhere
You can apply every fancy safety model (V cycle, iso262626, ASIL, MIRSA) and nothing can guarantee you write one-shot bug free software when your software is slightly more complex than just controlling some lights, sensors or actuators.
Are you suggesting the “does it drive” test after an update isn’t a reasonable test that should be a fairly common sense one to add in?
In all scenarios, tricky bugs will happen. Something inconceivable will go untested. But that’s not what happened here. This is basically functionality being lost that very obviously should have been tested.
In that sense, they could have made progress. Nobody is expecting perfection. You seem to be hung up on the distinction
