> Something like Waymo also has humans constantly monitoring and helping, but I don't see much discussion about that being "controlled by humans".
Constantly doesn't really make sense, riders can call for support and get a near instant response, but it's pretty obvious from some of the mistakes that humans aren't watching every ride in real time. There's video from inside a Waymo which is stuck in a lot repeatedly looping, discovering the exit it wants to use is blocked and then just driving to another exit before deciding hey, perhaps the exit I want to use is open (nope, it isn't) and returning again, and again, and again for example.
All the humans involved can see what's wrong here, but the Waymo driver software doesn't get it and so I think eventually a human (Waymo employee) has to drive the car out.
And yeah, there's definitely in San Francisco for example some people who believe it's all a Mechanical Turk again, even though that doesn't make any sense. In their heads, driving is another of those "uniquely human" abilities and so the only way to have AI cars would be fully general AI, and the real explanation has to be off-shore remote driving.
Would it even be feasible to provide a taxi service with remote human drivers? I get the remote driver occasionally dealing with slow movement, but I think full time driving at speed would be impossible due to latency issues. It’s not a remote piloted drone that is in the air and so has much less of a chance of hitting something by accident.
Otherwise you think someone would have tried offering taxis driven by people in India or the Philippines already.
I believe there's a startup saying they'll deliver cars to you, so, cars with no people inside them driven remotely, once there's a human inside the human is driving. I don't recall the name.
Waymo itself is clear that it has no remote driving capability whatsoever. The Waymo driver is in your vehicle, so any technical issue (e.g. phone network drops out, satellite fails, whatever) won't affect the vehicle's self-driving. It may give up and pull over and let you out, but since it's local any situation where the driver is disabled would be similar impact to a human driver - if a block of concrete drops off an overbridge and smashes the Waymo driver, that could easily happen to your Uber driver the same.
Hence their choice to employ humans to attend in person and drive a Waymo which gets into trouble. In fact the humans sometimes have had to "chase" a Waymo car that, unless it has been specifically told to stop, assumes it should try to complete the journey once it can figure out how. Waymo's remote support can reach into the driver's model and tweak it e.g. to label a stray traffic cone as just trash, not actually off limits - but they aren't driving the car.
Constantly doesn't really make sense, riders can call for support and get a near instant response, but it's pretty obvious from some of the mistakes that humans aren't watching every ride in real time. There's video from inside a Waymo which is stuck in a lot repeatedly looping, discovering the exit it wants to use is blocked and then just driving to another exit before deciding hey, perhaps the exit I want to use is open (nope, it isn't) and returning again, and again, and again for example.
All the humans involved can see what's wrong here, but the Waymo driver software doesn't get it and so I think eventually a human (Waymo employee) has to drive the car out.
And yeah, there's definitely in San Francisco for example some people who believe it's all a Mechanical Turk again, even though that doesn't make any sense. In their heads, driving is another of those "uniquely human" abilities and so the only way to have AI cars would be fully general AI, and the real explanation has to be off-shore remote driving.