However, your argument omits a couple of interesting details. First off, if a car can have uncontrolled acceleration, it can likely have any number of glitches. It may for example think it's accelerating uncontrollably, and try to throw me off a cliff. Or it may think that the cliff is a small ditch. Or it may think that a bunch of balloons tied to a mail box is a crowd. If you are a programmer, what would you rather debug: code that prevents uncontrolled acceleration or code responsible for killing the driver by recognizing crowds and cliffs?
The other details is whether the metaphorical crowd should even allow me to buy a car that has logic built into it to drive over them. What if instead of a cliff and a crowd it's actually two different crowds of different sizes? What would a human driver do in these cases?
As a developer I wouldn't buy a car that would drive off the cliff.
It's a tough problem. Personally I would make a quickly/poorly thought out analysis of how to do the least damage. Being human I'd probably get it wrong.
What does being a developer have anything to do with it?
Non-developers would assume the computer to be (somewhat) infallible.
I haven't tried to figure out what the numbers are, but my gut expectation is that vehicles driving into crowds is so rare that there aren't really statistics about it.
What if you're in your car with your family?
The best answer is of course: never let the car travel so fast this scenario happens - but given the possibility of an oil spill around the bend -- that might be very slow indeed.