3 ms·
The confusion from multiple HN posters here confirms that the "recall" language is inadequate to capture what is happening here. Obviously attention should be
by jdelman 4y ago
The confusion from multiple HN posters here confirms that the "recall" language is inadequate to capture what is happening here.
Obviously attention should be drawn to the fact that there is a critical safety update being pushed OTA, but "recall" is too overloaded a term if it means both "we're taking this back and destroying it because it's fundamentally flawed" vs. "a software update is being pushed to your vehicle (which may or may not be fundamentally flawed...)"
I do think something beyond "software update" is necessary, though - these aren't your typical "bug fixes and improvements" type release notes that accompany many app software releases these days. I don't think it would be too difficult to come up with appropriate language. "Critical Safety Update"?
- 2h 4y agoI think recall is just fine. Recall offers no ambiguity in my mind. It means the manufacturer fucked something up, big time. Everything else is just details. In the current world of forced updates (looking at you Android), the word "update" itself is kind of toxic, and doesn't (and I would argue cant) represent what has happened here, even if its technically more correct.
- redundantly 4y agoIn this scenario 'recall' is a legal/compliance term. It's appropriately used.
- deleted 4y ago[deleted]
- tsgagnon 4y agoObviously attention should be drawn to the fact that there is a critical safety update being pushed OTA, but "recall" is too overloaded a term if it means both "we're taking this back and destroying it because it's fundamentally flawed" vs. "a software update is being pushed to your vehicle (which may or may not be fundamentally flawed...)" How many times in history has a vehicle recall meant the cars were returned and destroyed? What makes this situation any more confusing than all the previous times vehicles were recalled?