Data Shows Google’s Robot Cars Are Smoother, Safer Drivers Than You or I
technologyreview.com
technologyreview.com
[Note that I haven't visited Thailand for about 20 years, Sicily for 10 years and India ever so perceptions may be out of date or incorrect based on media/TV coverage for the India case.]
Heck if a self driving car can get through some of the old parts of Boston and Philly I think they'd have a chance. Hell, if they can navigate D.C. with all the crazy turns that change depending on the hour of the day they definitely have a chance.
While some humans may be able to adopt to driving in Sicily or Thailand after the U.S., algorithms will never be able to do that. Unless, of course, specifically designed for driving in the U.S., Sicily and Thailand. (Or Russia for that matter, where driving is barely subject to any formalization.)
Humans can learn and adapt, it's in our nature, but an algorithm is just a reflection of some narrow aspect of what we, humans, have learned. Change a few external variables and your algorithm fails miserably.
I'm sorry, but somehow I don't believe in the future of self-driving cars, just like I don't believe in algorithms that would do image or voice recognition as well as we do.
I suppose I was thrown off by your phrasing "fundamental difference between humans and algorithms" and "algorithms will never be able to do that" and "I don't believe in algorithms that would do image or voice recognition as well as we do".
In fact, it seemed to me the entire point of your comment was to take the specific limitations of Google's current algorithm, and use it as an example of a general principle that algorithms are fundamentally limited in ways humans are not. If that wasn't the point of your original comment, what was?
Google's approach to the problem has nothing to do with the (nonexistent) "A.I." as media likes to present it, it's just incredibly complex software that's trying its best to tackle the problem of navigating the roads, recognizing signs, other vehicles, etc. I can imagine it's an enormous effort that doesn't guarantee success. See "Siri, Call Me An Ambulance" meme as an example of a comparable effort ;)
It is quite possible that the learning abilities come along with downsides.
The skill and alertness of the drivers in Sciliy were much greater than in the UK and the US but they had to be as those were relied on more than rules and systems.
I also wonder about what human driven cars, motorbikes and bikes might start to do once they know and can identify that there are nearly uncrashable and will reliably take avoiding action - will they learn that they can just pull out and let the computers avoid them?
They price their premiums so that they always make a profit, regardless of the risk.
That's why drivers that have accidents pay more than drivers with no accidents and young drivers (that are statistically more risky) pay more than not-young drivers.
Insurance companies will simply adjust the cost of insurance for self-driving cars to account for risk based on past data. If those cars will turn out to be involved in less accidents, the insurance will cost less. More accidents => cost more.
Basically Google can do the same for auto insurance that Amazon has done for online retail. i.e. they can operate on razor thin margins that no one else will ever be able to match because they'll be operating on sample-based statistics and it will take them a while before they have a significantly large sample to properly price their product.
They should at least talk to the engineers who design airplane autopilots, who know how to deal with that stuff.
What leads you to think they don't?
From what I read about the Deepwater Horizon design, and the Fukushima design, neither followed basic failsafe design principles.
From what I read about the Toyota "surging" issue, the throttle/braking system did not follow basic failsafe design principles.
Failsafe design principles are not taught in any engineering degree program I'm familiar with.
When I talk to other engineers about failsafe design principles, they are not aware of them.
Just like a frontend dev learns HTML/CSS/JSframeworks and a backend dev learns JSframeworks/Node/(no)SQL, embedded developers learn about creating real-time, fault tolerant, highly recoverable systems.
Tell an embedded engineer that he should consult with Boeing and he'll give you the same strained smile that you would give a family member who suggested consulting with Amazon/Ebay/YouTube because "they are good at making websites."
The code behind this will have to be completely open sourced to allay all fears.
And remember, it isn't just potentially the government who might do this. What about hackers working on behalf of some malicious and sinister agency? What if instead of kidnapping you, they mess with the controls and cause you to drive into incoming traffic? Or worse, an entire highway's worth of cars in a terrorist attack?
I'd be first in line to buy an autonomous automobile, but these are still real concerns. The more control you cede to programming, the more rigorous the code has to be.
Who are these sinister organizations? Chaos? E.V.I.L.? Or the FSB or what?
A terrorist attack? Wouldn't you be more worried people going crazy and driving down the wrong side of the highway?
By your thinking maybe we shouldn't even have cities because they are dense target rich environments. Even under an attack by Loki or whatever sinister organization from a comic book, you're still talking about something far safer than what we have currently.
I think it's hilarious that HN is the first place to see people saying the Boston Bombing was no big deal and more babies are killed each year by peanut buffer or something but yet here we have people more concerned about Magneto controlling cars and causing terrorist actions than reducing the very real 95% of traffic deaths. That's pretty hard to take seriously!
We already live in an age where pacemakers with wireless components can be hacked, and potentially kill the people who wear them.
I find it odd that people seem to be upset with governments intruding on their privacy in a purely abstract sense, but seem not to have issues with potentially giving up their physical autonomy completely to a system run by software (and potentially, by extension, a government.) Why be worried about the effect of a global internet surveillance apparatus but not be concerned about that being extended to the realm of vehicles, or the effect that that might have on personal freedom?
They were known to be very safe with a very low (almost non-existant) accident rate, but I believe this was the first presentation of some of the more detailed driving data such as acceleration and braking.
Why would it be exclusive? If a vehicle actually has an accident with a driver, and owner who is not a driver, and a manufacturer, then, depending on the circumstances, it is possible for all three to have some degree of liability. With a robotic vehicle, there's really not that much difference.
I like driving too, sometimes. Sometimes it's awfully boring and I wish I could do something else while on the road.
A common exchange: "Can you send us the fracking data?" "Sure, once I get approval I'll send it over." If you instead said "send them over" in this context it would suggest, at least in typical usage I'm familiar with, that there were not only multiple data points, but multiple data sets being set over.
WHen will they come out?