Examples aside, I think you are underestimating the complexity of the problem. A driveless car has been at the aim of very smart people for generations. That should give you an idea of the kind of effort here. It is the holy grail of AI. A machine that can interact with the real world, in a highly dynamic, highly complex continuous environment, without all the relevant information available, with split seconds decision making (as scary as a failure of a water or power station is, the systems running them have perfect information of all relevant variables at all times and very limited options available that they can outperform a human doing it).Jesterscup said:I'm a professional dev for my day job, so I'd say yes. And generally I agree with what you're saying. However we already have ( in the western world ) most of our critical infrastructure controlled & managed by computer, water, traffic management, planes, power ( inc. power generation ), our financial systems, pretty much all business on the planet, I could go on. Is it 'secure' no of course it's not, but the risk is managed.Lil devils x said:UGH. I have to wonder if anyone who thinks this is safe in any way actually understands ANYTHING about programming.
Of course there is a risk, BMW recently had to announce a patch since in theory it was possible to destroy a car engine via smartphone. But by the same point there are huge known issues involving SCADA systems that run our power grid, nuclear power stations, and a bunch of other really scary stuff.
No it's not a minor issue, but it doesn't make or break the concept, if it did we would have much bigger problems on our hands. You don't have planes dropping out of the sky, or nuclear explosions, power outages, complete financial collapse etc as a regular occurrence due to hacking ( though yes it does happen, stuxnet being a prime example). Clearly managing this risk, ensuring that the proper systems and resources are in place is important, but it is possible to manage this risk. Far from the chaotic "wild west" which is often portrayed ( and I don't deny there is a consistent "arms race" in security dev on many, many levels ), it is currently possible to manage this.
Generally security considerations scale in importance. Sure heartbleed was an utter nightmare ( lots of lessons learned there! ), but you find as the importance/criticality of a system or information assets increases, as does the time,effort, resources & collaborative effort to keep it secure.
It comes down to this, Do I believe that driverless cars can be safe or not from a security standpoint? If I didn't I'd be living in a cabin in the woods, far away from flightpaths,roads,power stations, and pretty much anything that could kill me with a programming error ( including my bluetooth fridge... I know that thing hates me, I can tell)
Forget Turing test. A software as complex as this would ace Turing test like it was a slow day.
We are going to make mistakes into this one. It is inevitable (there are bugs in Assassins Creed, and those are child's play compared to this)... the real question is, is the public willing to risk the mistakes until the system is reliable enough? And, as bad as humans are at driving, we are hundreds of times more competent than the most advanced software out there. It will be a long time before it gets to reliable enough, so, are people willing to risk being put into half a ton metal boxes at 50 km/h controlled by something that is about as competent as them?... As people here have said, most of the public would rather risk a human being accountable for that, that a faceless program that could be running in millions other cars.