Waymo drives 4 million miles every week (500k+ miles each day). Vast majority of those collisions are when Waymos were stationary (they don’t redact narrative in crash reports like Tesla does, so you know what happened). That is an incredible safety record.
We all know Tesla likes to play smoke and mirrors game with vehicle numbers — they have 300+ "robotaxis" but only 7 of them are unsupervised [1], and they shut down when it rains [2].
So let's use a metric that unequivocally shows who is 'winning'. I'm confident Waymo will have more paid rides per week than Tesla at the start of 2027 (I'll give you 2028 if you want). No other metric indicates scale better than passenger trips. If you have more robotaxis or you are in more cities, it will show up in the trip count.
I'll give $1000 to a charity of your choosing if Tesla beats Waymo in this metric. Fully unsupervised trips only, does not include trips with a safety driver or a monitor in a passenger seat, none of the usual games they like to play.
Pay close attention to the wording: "The Waymo Driver ... remains in control of driving". That means it applies the controls needed to go from point A to point B on its own. However, it does not choose point A and point B on its own: a human chooses them. That's autonomous path planning, but not autonomous navigation, and certainly not "fully autonomous" anything.
Waymo prevaricates about the "influence" the human operator has on the path taken by the Waymo Driver [1] but it is clear there are situations that the Waymo Driver cannot choose point A and point B on its own, at least safely, otherwise Waymo would not be paying for humans to do it. They'd let the system do it on its own. It can't. It's not "fully autonomous".
We can play with words and accept whatever terminological obfuscation Waymo wants to impose in order to pimp its wares, or we can accept that current systems have limitations, and choose to understand the real SOTA over marketing.
_____________
[1] Fleet response can influence the Waymo Driver's path, whether indirectly through indicating lane closures, explicitly requesting the AV use a particular lane, or, in the most complex scenarios, explicitly proposing a path for the vehicle to consider idib.
> Tesla is executing the strategy that most quickly scales to 100% of the population.
So, uh… where is this “scale” then? This “strategy” has been bandied about for better part of a decade. Why are they still in a tiny geofence in Austin with chase cars?
Waymo is doing it right now. Half a million rides every week, expansion to a dozen new cities. Tesla does a few hundred in a tiny area.
Scale is assessed by looking at concrete numbers, not by “strategies” that haven’t materialized for a decade.
That was 2 generations of hardware ago (4th gen Chrysler Pacificas). They are about to introduce 6th gen hardware. It's a safe bet that it's much cheaper now, given how mass produced LiDARs cost ~$200.
This is the real story buried under the simulation angle. If you can generate
reliable 3D LiDAR from 2D video, every dashcam on earth becomes training data.
Every YouTube driving video, every GoPro clip, every security camera feed.
Waymo's fleet is ~700 cars. The internet has millions of hours of driving
footage. This technique turns the entire internet into a sensor suite. That's a bigger deal than the simulation itself.
It's not unheard of, there are a handful [0] of metric monodepth methods that output data that's not unlike a really inaccurate 3D lidar, though theirs certainly looks SOTA.
> Persistent directory at ~/.claude/projects/{project-path}/memory/, persists across conversations
I create a git worktree, start Claude Code in that tree, and delete after. I notice each worktree gets a memory directory in this location. So is memory fragmented and not combined for the "main" repo?
Yes, I noticed the same thing, and Claude told me that it's going to be deleted.
I will have it improve the skill that is part of our worktree cleanup process to consolidate that memory into the main memory if there's anything useful.
Yes, it provides external validation for the valuation. Otherwise, Alphabet can simply "self value" Waymo at a funny amount like $1T.
There's also a strategic partnership angle in these rounds. For example, Magna and Autonation were early investors in Waymo. Magna operates Waymo's factory in Arizona to upfit their vehicles with sensors, Autonation (the huge dealership/service network) is the maintenance partner.
In general, the Alphabet playbook is that projects "graduate" out of Google X, and are expected to operate as a standalone company, including being responsible for raising funds.
reply