Hacker News new | ask | show | jobs
by 203993203993 3779 days ago
What the hell are you talking about? You are saying google cars are stupid enough to cause a crash but smart enough to weight the worth of people inside and outside the car and then decide which to save. How would a car even kill the occupants? Drive into a wall without braking? Why would it even do that? Our cars are designed to deform and absorb most of the energy from a crash, it's better to stay in your lane and brake as much as the car can handle and if it ends up being unavoidable then hit the car in front of you. Somehow even with all that sophistication everyone dies but a foot brake could solve all problems?
3 comments

The car would not need to be "stupid" or "stupid enough" to cause a crash, sometimes a crash is unfortunately inevitable given the situation other cats put you into.

And yes, some people sometimes have to make the difficult decision between hitting another smaller car, hitting a truck, and hitting a person. I suspect these days, most people react irrationally in split seconds. However, with self-driving cars, all the data would be available and a real decision could be made...but what would be the constraints and what would you maximize? that is the scary question.

He is just saying that it's comforting to have the idea that you can always stop the car.
Tyre blows, the car starts sweering to the left into the oncoming lane, the computer can either:

1) decide that a critical error has occurred and shut down

2) apply full brakes on the remaining wheels, sending the car into a spin and killing a group of pedestrians on the pavement.

3) let the car continue, smashing into a minivan with a family inside it. The minivan is also auto-controlled but has no time to change course

4) try steering further left, hitting the barriers/trees, possibly killing its own occupants.

Now, situations 2-4 can be simulated before they happen with enough computational power. Therefore, the computer would have to take a conscious/programmed decision who to kill, and that is a huge deal morally, because at some point someone somewhere will have to write code that will literally be evaluating value of human life.

And before you say that humans would do no better in this situation - that is true, but no one will judge you for a decision you took in the split second you had, you would do what felt right at the time. The computer is programmed a certain way and you can always sue saying that if it did X then person Y would still be alive - and if there's one thing that companies fear it's litigation.

5) apply simple ABS'd braking to the three remaining wheels, maintaining control and bringing the car to a safe stop.

Cars do no just flip over and explode for no reason. Life is not a fast and furious movie.

This scenario is why a fully autonomous (and networked) grid could be a beautiful thing. You car takes option #3, but all oncoming traffic is already breaking and realigning to let you pass through the lane unharmed, and you car brings itself to a stop in the opposite shoulder.
Well, obviously the car's own occupants should always hold the highest priority for that car. Otherwise it is a terrible terrible product if the code even contains the possibility that it could ever prioritize anything over the lives of its owners.

In your scenario, smashing into another vehicle will be preferable to mowing down pedestrians; that vehicle's program just might be able to save itself, or the two vehicles might even communicate to minimize the damage to each other, and in any case a vehicle will most certainly absorb more of the impact than an exposed pedestrian could.

People on foot, who have nothing to do with the traffic, should never have to deal with the vehicles and the consequences of their programs. Number 2 from your scenario should not even be an option to the program.

While I agree with you, there still is a possibility of conflict in what you are saying. What if hitting a pedestrian is the only way to avoid killing occupants of the vehicle? On one hand, like you said - the vehicle should always prioritize its owners, but at the same time, it should have some overriding directive that says "never hit a pedestrian at all costs". One of those has to give - who decides which one?
The first priority should always be your occupants. Hardcoded.

Otherwise, can you imagine the first incident in which some passengers died because the code prioritized the life of someone else? Would anyone want to buy an autocar after that? "YOUR CAR COULD CHOOSE TO KILL YOU", the headlines will say.

The second priority should be the safety of pedestrians who are off the road.

Until we have computational power at the level of divine prescience, I don't think you can do much else in scenarios like the one you described, other than have a chain of basic priorities that falls back on "stop everything."

Eventually though, powerful-enough AI may be able to simulate all outcomes down to a very granular level, such as the difference between outright killing someone or just injuring their limbs to the point of crippling them for life.

Many factors will need to be considered then; who appears to be the weakest individual among the unavoidable targets? Are there any acquaintances of the owners among them? Is there a hospital nearby that could tend to their injuries? Does it look like a suicide attempt?

The government might and probably will change this rule.

I can imagine that after the first couple of accidents where the algorithm decides to kill N pedestrians to save 1 driver, the government could switch to a "utilitarian" point of view - minimize the number of lost lives - and will enforce this by law.

> the government could switch to a "utilitarian" point of view - minimize the number of lost lives

There's nothing "utilitarian" about this, unless you assume that:

(a) All people value their own lives equally

(b) Nobody places any value on anyone's life but their own.

(Side note: we know that both of those don't even come close to being true.)

Without those assumptions, a utilitarian point of view will show some pretty obvious biases against just killing the fewest people -- among other things, it will try to kill older people rather than younger people, and to kill people with the smallest number of relatives (who would be sad about a death in their family).

Right. We had an extensive discussion about this at BarCamp Philly this year. The discussion was on machine ethics and we spoke largely about these scenarios of driverless vehicles.

I made the argument that machine ethics aren't a real thing. Companies will do whatever they can to avoid litigation, then the government will step in with regulations as the closest approximation we'll get to ethical behavior.

I hope one day people will actually grow to appreciate that viewpoint and care about others too. Personally, I find the concept of a car that would consciously chose to save you at the expense of 5 pedestrians to be morally wrong.
The cars just need a high speed connection to the credit bureaus, then they can optimize for minimizing the sum of the FICO scores of those killed.

More seriously, I don't understand why this is always brought up in the context of autonomous cars. How often do crashes happen where killing people is inevitable but you get to choose who dies? How often will such crashes happen when autonomous vehicles are common? How far from the theoretical optimum will it be to just say "in an emergency, brake to a stop and steer to avoid obstacles"?

I'm pretty sure this is an edge case on the edge cases. If autonomous vehicles deliver on even 10% of their promise, safety will go way up. It doesn't have to be perfect.

The sticky part is, the software has to be written now. After millions of miles of exercising that code, every path will be taken.

So what do you put in the "Run over the kid, or run into a wall (or oncoming traffic)?" decision point? Somebody has to die. Just braking until you hit the kid is a pretty crappy hack.

And when the kid gets hit, the software will be examined. And the comment that says "screw it, just hit the kid" will come to light.

The software isn't going to say "screw it, just hit the kid." It's going to be more like what I said: brake to a stop, steer to avoid obstacles. If an obstacle must be hit, then default to going straight.

This is already going to be vastly superior to human drivers, who often don't bother to brake, or flinch and steer into oncoming traffic for no particularly good reason.

After we've cut down the 30,000/year death rate from car accidents by a couple of orders of magnitude, if we get start to get desperate about improving safety and have trouble figuring out how, then maybe we can start looking at rare and bizarre occurrences like these, if they ever actually happen.

Trying to work out the precise requirements for ethics in autonomous car crash response, when we don't have more than the vaguest idea of what kind of crashes they'll get into or what kind of responses might be available, is awfully premature.

And this is why driverless cars will never (or at least not soon) attempt to optimise trolley-problem-style for number of human lives saved or similar. The algorithms chosen will optimise for one thing and one thing only: Legal defensibility for the car's actions.