Because those are the same games I have available while not in a Waymo and I can play them anytime/anywhere. By having Waymo exclusive games that save state between rides that aren't available outside the Waymo, it builds the "only in Waymo" excitement.
Making my own epub reader with the kitchen sink of features I'd like. It's a speed-reading app first and foremost, using RSVP (rapid serial visual presentation, one word at a time). Also answers questions about the book with an LLM without spoilers, and can create illustrations. I've been reading _Mercy of the Gods_ lately, which has vivid descriptions of a bunch of alien races, but the pictures have done a great job supplementing my imagination. I've read more books in the past month than the last year, but we'll see if I keep it up.
My personal project is illustrating arbitrary stories with consistent characters and settings. I've rewritten it at least 5 times, and Nano Banana has been a game-changer. My kids are willing to listen to much more sophisticated stories as long as it has pictures, so I've used it to illustrate text like Ender's Game. Unfortunately, it's getting harder to legally acquire books in a format you can feed to an LLM.
I first extract all the entities from the text, generate characters from an art style, and then start stitching them together into individual illustrations. It works much better with NB than anything else I tried before.
We use c++ modules at Waymo, inside the google monorepo. The Google toolchain team did all the hard work, but we applied it more aggressively than any team I know of. The results have been fantastic, with our largest compilation units getting a 30-40% speedup. It doesn't make a huge difference in a clean build, as that's massively distributed. But it makes an enormous difference for iterative compilation. It also has the benefit of avoiding recompilation entirely in some cases.
Every once in a while something breaks, usually around exotic use of templates. But on the whole we love it, and we'd have to do so much ongoing refactoring to keep things workable without them.
Update: I now recall those numbers are from a partial experiment, and the full deployment was even faster, but I can't recall the exact number. Maybe a 2/3 speedup?
How much of the speedup you're seeing is modules, versus the inherent speedup of splitting and organizing your codebase/includes in a cleaner way? It doesn't sound like your project is actually compiling faster than before, but rather it is REcompiling faster, suggesting that your real problem was that too much code was being recompiled on every change (which is commonly due to too-large translation units and too many transitive dependencies between headers).
This was in place of reorganizing the codebase, which would have been the alternative. I've done such work in the past, and I've found it's a pretty rare skillet to optimize compilation speed. There's just a lot less input for the compiler to look at, as the useless transitive text is dropped.
And to be clear, it also speeds up the original compilation, but that's not as noticeable because when you're compiling zillions of separate compilation units with massive parallelism, you don't notice how long any given file takes to compile.
Clang modules are nothing like what got standardized. Clang modules are basically a cleaned up and standardized form of precompiled headers and they absolutely speed up builds, in fact that is primarily their function.
At Waymo we use c++ modules via clang and got the demanded 5x speedup.
As the article mentions, you need a close relationship between the compiler and build system, which Google already has. The google build tooling team got modules to mostly work but only turned them on in limited situations. But we but the bullet and turned them on everywhere, which has sped up compilation of individual files by more than 5x (I forget the exact number).
The remaining problem is that sometimes we get weird compilation errors and have to disable modules for that compilation unit. It's always around templates, and Eigen has been gnarly to get working.
> “While TBD Labs is still relatively new, we believe it has the greatest compute-per-researcher in the industry, and that will only increase,” Meta said.
I've worked on autonomous vehicles for 16 years and my largest philanthropic effort is improving public transit. The common theme is being really interested in transportation and wanting it to work well for people.
Cruise was also the top funder of one San Francisco's recent MUNI funding ballot propositions (which just barely failed). You can certainly have a cynical take on that, but they still did it.
The paper under discussion only considers human accidents in similar environments to where Waymo operates. So it's only making a claim about like-for-like driving.
You could still say you care about snow driving and want to see that comparison, but it doesn't mean the claims in this paper are wrong.
reply