Smartcars: Dangerous if software companies would make them

Posted by hkwint on May 27, 2013 10:08 AM; By Hans Kwint - The Netherlands

LXer Feature: 27-May-2013

In his article "Smartcars – dangerous or simply can’t make money out of the apps?" Ray Shaw wrote:
Quoting:“The motor industry is slow to adopt because it fears it would lose its control over the process and its profit. "No it is too dangerous to have smartphone/tablet control” say the motorcar companies “What if it failed and crashed?”. More FUD

In his article, he proves to be totally clueless about the automotive industry: All software companies would be bankrupt if they made cars. Besides, fear, uncertainty and doubt about customer safety in the car industry is less acceptable than in software companies who have been selling bug ridden defective products for years without problems. Please let me explain you the difference.

Mr Shaw ends his article with:

Quoting:I suspect that Google, Apple and Microsoft et all need to use some spare cash, buy a motor car company (like Tesla) and seriously disrupt the status quo.

When it comes to "entertainment systems", I'd agree, but when it comes to software related to driving, no way software companies can ever be disruptive - except for causing their own bankruptcy.

For a starter, how's this: $4.9 Billion Jury Verdict In G.M. Fuel Tank Case

Compared to this, the $900 million fine of Microsoft by the European Union is a "minor detail". Why is product liability so much harsher on automotive companies then any laws on software companies? Well, in product liability, there's the concept of strict liability. As Wikipedia puts it:

Quoting:Rather than focus on the behavior of the manufacturer (as in negligence), strict liability claims focus on the product itself. Under strict liability, the manufacturer is liable if the product is defective, even if the manufacturer was not negligent in making that product defective.

And here a famous landmark-quote from Justice Traynor:
Quoting:It is to the public interest to discourage the marketing of products having defects that are a menace to the public. If such products nevertheless find their way into the market it is to the public interest to place the responsibility for whatever injury they may cause upon the manufacturer, who, even if he is not negligent in the manufacture of the product, is responsible for its reaching the market.

In other words: "We do not wish car manufacturers to calculate a price for the losses of lives / health and comparing them to making their product safer". Because if car manufacturers can choose between spending 5 million on making a fuel tank safer or spending 2 million on not doing so and paying in fines in the court after accidents, we all know what they will probably choose. So, if law makes the price for a life or loss of health high enough, say several billion, car manufacturers will never put safety-savings first, but always the health of the consumer.

Apart from liability, what else have we? Let's see:

Toyota's Recall Costs Could Top $5 Billion

When was the last time Microsoft had to pay $1 billion in damages to LSE because of errors Microsoft made, the stock system crashed? When was the last time Google had to recall 2 million phones to the stores because they had a programming error - and it had to be fixed?

Make no mistake, a liability claim will put most smaller companies - such as those who supply to car makers - straight out of business, and a recall might do the same. In the PC and especially software world, there's no such thing. You can sell bug-ridden software and never be held liable for damages.

The only case I know was Intel - who had to recall the Sandy Bridge - and it cost them a whopping $700 million. There's simply no discussion: If Microsoft and Google where held to the same high standards as car makers, they would already be bankrupt.

You see, it's simple statistics. Companies such as Toyota and their suppliers are only allowed to make a mistake in let's say 4 out of 1 million parts (4ppm), and then it's already a lot. Given some assemblies are made of multiple parts, that means if let's say 4 out of 1 million gearboxes would be allowed to be faulty, then for the gearbox-parts it's even lower, maybe 1 in 5 million is allowed or something.

Let's compare: "Commercial software typically has 20 to 30 bugs for every 1,000 lines of code". Whahaha, LOL. Now let's suppose Google doesn't make a hobby project of 10 lousy cars, let's talk about mass production. BMW sold 1,8 million cars over 2012. Let's consider a really lean kernel: Linux 0.01 had 10 000 lines of code, so if the same numbers would apply to Google / Microsoft 'disruptive' technology and they would apply safety-critical software in every BMW, there would be at least 36 million "errors" on the road. Would you dare to cross the road if such a BMW was approaching?

Now way Microsoft or Google will ever be disruptive in the automotive industry! First of all, if their software applied to safety-critical components, they would be sued straight out of business. Second of all, if MS had to recall all their defective products because they were liable - even if not negligent - they would be darn bankrupt too.

Now you know why it's not trivial to supply sensors to self-driving cars: The physical sensors and the software better had about a magnitude of one million times less errors per part than typical Microsoft / Google software, or the sensor supplier can say goodbye to all the employees and pay fines until 2050.

And when it comes to liability, ask yourself these two things:

1) Would you step in a plane if it ran Linux for safety-critical systems, with 20 faults per 1000 lines of code?

2) Would you step in the same airplane if Windos or Linux only ran the entertainment systems?

The answer to those two questions will point out where the place of Linux / Windows and Google / Microsoft in cars will be and certainly where it will end: They're only suited for entertainment, and better not be connected to anything safety related. With the record of Microsoft / Google and even the Linux kernel, and the number of errors they sell - and get away with - they will never be serious automotive suppliers for critical parts, car brands are not like software-buyers. Make a few mistakes in a few parts and you're out - usually for at least the next 10 years or so.

If Mr. Shaw asks "when was the last time your tablet failed"? I think of Dell. Sure, only 1 out of million accu's explode, I mean, come on, what's the last time you saw a Dell laptop explode? You didn't see any ever, did you? So it must be safe. Haha, good joke. On to real life, if that Dell battery was a battery in a Boeing Dreamliner, Dell would have had a lot of trouble and a bad name. Do you think Airbus will choose GS Yauasa and Thales next time they design an airplane - as Boeing did? Or after the melting batteries in Mitshubishi's, do you think BMW will choose them? Does it comfort you that you never saw one melt?

Hopefully, by now, you understand that BMW was not being conservative or afraid to lose control over their income when BMW made their claim:

Return to the LXer Features

Subject Topic Starter Replies Views Last Post
Don't Forget the EULA. theboomboomcars 5 3,770 May 27, 2013 8:53 PM

You cannot post until you login.


  Latest Features
Scott Ruecker: My Linux Laptop
May 08, 2022

Scott Ruecker: Laptop Dual Boot Project: Part 2
Nov 30, 2021

Scott Ruecker: Laptop Dual Boot Project
Nov 30, 2020

Scott Ruecker: Lenovo Laptop Love..Not!
Nov 01, 2019

James Dixon: Attempting to install Linux on a new laptop, a follow-up
Sep 21, 2019

James Dixon: Attempting to install Linux on a new laptop
Jun 07, 2019

Hans Kwint: Updating from Ubuntu LTS 16.04 to 18.04
May 03, 2018

Dr Tony Young: A KMail Breakthrough.
May 01, 2016

James Dixon: Installing jstock with Slackware 14.1
Jan 19, 2016

James Dixon: Installing sbopkg with Slackware 14.1
Jan 16, 2016

View all

  Search Features

Search LXer Features:

[ Copyright © LXer | All times are recorded in Central Daylight Time (CDT) ]

[ Contact Us | Privacy Policy | Terms of Service | About us | rss | Mobile ]