Driverless robotaxi fleet paralyzed for hours in San Francisco (thelastdriverlicenseholder.com)

Article summary

A fleet of driverless robotaxis from GM Cruise Automation was paralyzed for hours in San Francisco, with at least a dozen vehicles blocking an intersection. The exact cause of the issue is unknown, but it is speculated to be a software update that went wrong. The vehicles were manually driven to a depot by Cruise employees. The incident has raised questions about the reliability and safety of autonomous vehicles.

Main themes

• autonomous vehicles
• software updates
• safety concerns
• GPS jamming
• mapping data
• C and C++ in safety-critical systems
• reliability and testing

What commenters say

• Some commenters speculate that the issue may have been caused by a software update that was deployed during off-hours, which then triggered a bug when the vehicles were in operation.
• Others suggest that the problem could be related to GPS jamming or bad mapping data at the specific location.
• There is disagreement about the implications of a company being able to retroactively remove features from a product, with some arguing it is a major concern and others seeing it as a normal part of software development.
• Some commenters express skepticism about the maturity and reliability of self-driving technology, citing personal experiences with autonomous vehicles making mistakes.
• The use of C and C++ in safety-critical systems like autonomous vehicles is questioned by some, who argue that it is not suitable for such applications.
• Others defend the use of these languages, citing their widespread use in the industry and the presence of safety protocols.
• The incident highlights the need for more transparency and testing of autonomous vehicle systems to ensure public safety.