That might not be bad for new technology and was showing trend improvement, but it doesn't compare favourably with accident rates for human drivers
https://static.googleusercontent.com/media/www.google.com/en...
Among people, there are some good drivers and some poor drivers. The average driving ability --- including fast reflexes for dealing with accident situations, for example --- is somewhere in between.
Is it fair to possibly force self driving cars on the good drivers?
(they probably shouldn't jump on the self-driving car bandwagon early anyway, but just a thought.)
I have pretty good reflexes, but that doesn't make me a good driver.
I equate good driving with common sense, not speeding over the limit or taking unnecessary risks, not tail gating people, and in general not being a tool.
I.e. when you're driving a 2-tonne metal tank going at 80 km/h, good == safe.
In this sense, autonomous cars have already far surpassed us.
Again though, I was discussing the situation in which cars were only slightly above average, meaning there were likely situations where some people would do better than it and might be putting themselves in more risk going into a self-driving car.
(if your point was more to make sure people don't take the wrong message away from my post, sorry for this response then!)
People suck at paying attention to boring situations. So, the easiest part of the trip is likely the best thing to automate.
Remember, the actual accident rate is very low. Further cars and humans are likely to make different mistakes so if you supervise and the car does sub second reactions and 24/7 360 degree vision the combined rate is likely to be great.
In addition, impaired drivers causing accidents will pay a fine or go to jail. Who takes the responsibility of impaired sensors in self-driving vehicles?
I don't think that's a fair comparison at all.
Tesla, with the current AutoPilot, will have to collect data for closer to 20 years in order to have good enough statistics to claim AutoPilot is safer. (Since AutoPilot only works in some situations, they wont get 10 000 miles per year.)
After all the work that was done with the DARPA Grand Challenge(s) in the past decade, it would be an embarrassment to Google if they couldn't get the cars to work in controlled conditions, rather than it being a staggering achievement in getting them to where things are at now.
I really want self-driving cars to happen, but I see the biggest impediment to that vision of the future being the general public's level of optimism and credulity WRT this stuff, to say nothing of the tech community's optimism and credulity. It's a domain that is a nearly infinite bucket of incredibly hard problems, problems that may ultimately prove insoluble as currently specified. If everything goes well, then maybe in 20 or 50 years a lot of transportation will take place in self-driving cars which operate with sets of known constraints in environments that are (to some degree) controlled.
If everything doesn't go well, then people will keep talking about how self-driving cars are inevitable, and how in a just a few years they're going to pick you up at your house and drive you to work using the exact same roads set up the exact same way as roads are now, doing the exact same commute that they might've been doing when driving themselves. This credulity will push the money and the technology forward, until too many disappointing setbacks occur, and then all the money dries up and nobody's talking about self-driving cars anymore.
If you tell somebody that something is inevitable and almost here and it's just a matter of throwing enough resources at it, it's much easier to get people to give you money to do those things, but as soon as anything happens that doesn't fit that script, they will assume you've been lying to them all along (or just aren't credible), and the R&D money goes away. Whereas if expectations are set appropriately, it's harder to get that money, but as long as there are achievable, realistic goals and people aren't basically pitching magic, then the funding is more likely to stick around during the rough patches.
Writing high quality, reliable code (for example, in airplane control software), including testing etc, tends to take 5-8 years. So from a project management perspective, that's the reasonable estimate.
Maybe phrased less combatively: Do you have a source that's not Google (or a Google-slanted PR piece) that has hard data about what's possible today and what will be possible soon?