OSS is similar to sharing knowledge/design; so there would be no liability. But if a consultant or organization builds a product or service from OSS and provides it to another entity, they would be liable. Currently organizations selling software based on OSS provide the same liability that closed source organizations provide. I suspect that the same would continue if new regulations are introduced.

Presumably the person's hands would slip from the steering wheel. Now one can claim what if the person's hands are stuck in the wheel while asleep. That person has to understand that safety systems are about reducing risks, they may not be able to always eliminate risks completely!

Until you understand that though Supreme Court denied certiorari petition in June 2015, Google filed petitioned again in January 2019 to challenge the two rulings that were made by the Appeals Court on whether copyright extends to a software interface like an API and whether the use of the Java API by Google fell within fair use. The Supreme Court granted certiorari in November 2019. https://arstechnica.com/tech-p... https://www.supremecourt.gov/d...

The correct way to put this is 1/3 people did not want Trump. You cannot claim that those who did not bother to vote did not want Trump.

Having worked in both US and India, and having seen the software developed in both countries, I can safely say that the code written by comparably qualified developers is not that much different! Just like you are complaining about bad design and bad code, the developers in India also complain about the quality of code when they are handed code written by developers in US and asked to debug it and develop it further! Agree on the productivity part, I would put the productivity at around 60-75%. One thing I would additionally like to correct - "Getting it right" always shows up in the management KPIs as the cost of rework!