The only hiccup I can remember was being in an intersection (past the crosswalk) to make an unprotected left and while we were waiting the light turned yellow. A human driver would likely wait for the light to go red and then make the turn, but the Waymo gave up almost immediately and instead decided to circle the block to make the left (three rights). A little odd, but I never felt unsafe.
If we had Waymo where I live I'd take it everywhere. It's slightly cheaper than an Uber, a nicer car, a better driver than some Uber's I've been in, and there's something nice about not having to interact with a real person.
This is the end-goal, I guess? Not just avoiding a taxi/Uber driver, but avoiding as much human interaction as possible.
Is it surprising that technology is (collectively) being evolved to isolate humans from each other?
AFAICT, we can't have our cake and eat it too -- a completely frictionless life is a zero human-interaction life, which would be very sad.
Edit: I fall into this trap too, but I'm aware that every time I choose convenience over friction, I'm losing a tiny bit of my Human-ness.
I would gladly trade the 1% of rides where I had a decent conversation with the driver to remove the 99% where I we both try to make forced small talk or we both awkwardly sit in silence. Plus, not having to worry about me and my friends annoying our driver when we're drunkly coming back from the bars at 2am is such a win.
I totaled two cars when I was newer to driving because I did exactly that (waited for the light to turn red and then went), only to collide with people running the red.
Insurance faults the person who was making the left, so I can understand why the Waymo would want to be more cautious
But both Waymo and Cruise lose money on every ride. All the sensors and on-board compute are expensive, and also the R&D, and the 3D maps. Both services rely on detailed 3D maps of the areas they service, and are geofenced to that.
So right now, it does not scale yet until they can bring down the costs, and/or reduce reliance on those maps, which take a long time to make.
Videos of my rides: https://youtu.be/q-l23cMs1Fs?si=R1hjPQokqAMCff_T https://youtu.be/FZTWxDe1i6g?si=mGbcixGTKCQchnVv
I think we need to split this into fixed vs variable costs. It's hard for me to believe that the sensors+compute is more expensive than a human. Those sound like the variable costs. I'd be surprised if selling an additional ride causes e.g. Cruise to lose a bit of money, but I'd love to be corrected.
But that's largely a sunk cost that (in SF anyway) has already been spent, right? It's not like that cost goes up on a per-ride basis.
For places where that's already done, you only need to account for the cost of sensors/compute/maintenance of the vehicle themselves, which seem (intuitively) like they would be lower than the expense to users. Which would mean that a ride is net positive.
Maybe it's the case that configuring and maintaining the cars is incredibly expensive. That would be the only way I could envision actually losing money on a "per ride" basis.
For mapping, no.
Waymo maps the city constantly with every car, and they have a mapping team that reviews those changes before they go to the other cars. So ongoing cost of the human side is a thing (for now?).
They also have a team of "remote operators" that watch the fleet in real time in case they have a panic attack over something, so more ongoing cost that's not just sensors/cars.
- no driving on freeway with passengers (that alone is a huge limitation. You couldn't get to most major airports (in any sensible time) under that limitation. Add in trucks, rush-hour, ripple congestion, lane-splitting motorcyclists.) But presumably also, Waymo and Cruise don't want to pick an all-out war with human drivers working for Uber. Not yet.
- if a driverless car gets confused or can't handle a situation on a city street, it can slow and stop completely and block traffic (and wait for emergency responders to intervene, or wait minutes/hours for remote human driver to override), which is "merely" an annoyance to locals. Whereas doing that on a freeway could injure or kill large numbers of people.
- "selected cities" seems to currently only be southwestern and southern US (SF, PHX, LA, AUS), warm and mostly clear skies, nothing regularly getting near a bad freeze or with bad rain/ snow/ slush/ storms/ gusts/ visibility/ unpredictable ice and skidding [0].
- only cities with well-maintained signage, roads, road markings which can be imaged reliably etc. This is an implicit limit on the locality's income and tax base.
- the recent Cruise secondary incident (near-fatality from a hit-and-run caused by a human-driven car) in SF and other incidents with pedestrians, cyclists and human drivers. "Just fix a few minor issues around the edges" will have a different meaning if you're a pedestrian, cyclist or transit user near a high-traffic street. This could easily become a political issue in some localities. Or maybe driverless will only be allowed in bus lanes or certain lanes of certain streets, or at certain times of day, or not near school pickup/dropoff, or through residential areas (like in 2011 when there were deaths of pedestrians in East Palo Alto residential areas due to drivers rat-running, exacerbated by the rush-hour to Facebook and on 101[1]).
[1]: https://paloaltoonline.com/news/2011/09/28/girl-7-killed-in-...
City-bound autonomous vehicles are still far away for the reasons you point out, but autonomous long-haul trucking is back to being a sci-fi pipe dream at this point.
(also does anyone have current data on the viable market size of driverless rideshare vs driverless delivery vs drone delivery vs helicopter taxis vs autonomous long-haul trucking)?
> "Even if Waymo could place fully autonomous taxis into every city in America, that consolation prize wouldn't nearly make up for the shortfall of not taking over the logistics industry as was hoped."
I want to decouple discussion to what's actually technically and politically achievable (within say 5 yrs), versus whatever story Waymo was telling its shareholders 5-10 yrs ago.
I think it's a mix.
Waymo cancelled their self driving truck division recently to focus on ride share[0].
They're most likely feeling push back from someone over self driving trucks, but I wonder if the bigger thing is liability and dangers around the weight it would be hauling. They already have had one of their trucks be ran off the road by another semi already and haven't released ANY statements about it.[1]
[0]: https://waymo.com/blog/2023/07/doubling-down-on-waymo-one.ht...
[1]: https://techcrunch.com/2022/07/01/behind-the-scenes-of-waymo...
I am wondering if it is reasonable goal, what share driver's payroll takes from total logistics expenses(vehicle + maintenance cost, gasoline, last mile logistics: loading/unloading truck and storage, delivering package to final recipient).
I never considered SF as southwestern, but Wikipedia says you're correct
https://en.wikipedia.org/wiki/Southwestern_United_States#Reg...
the southwestern US extends to the Sonoran and Mojave deserts on the west side.
It lists the largest cities of the southwest as Phoenix, Las Vegas, El Paso, Albuquerque, and Tucson.
SF is not in there...
Videos that show up on the r/self drivingcars subredddit show increasing fluency/confidence in driving from Waymo. But there's always going to be socially weird situations in cities where the answer is to benignly break the law, and it's not clear how well SDC's will ever do with those.
I’m not affiliated with Waymo. Just someone who got early access by joining the waitlist.
It's always the last 20% that are demanding. You're left with tricky edge cases, legal battles, and operational challenges.
I’m not aware of any connection it has to Waymo though.