Oil was solely a lighting product at this point. The Teamsters were clearly not thinking 70 years into the future to stop automobiles. But I think the "monopoly" part of the quote is somewhat germain, even if it's just opinion of the author.

"From the first discoveries, teamsters, lashing their horses, had clogged the roads of the Oil Regions with their loads of barrels. They were more than just a physical bottleneck. Holding a monopoly position, they charged exorbitant rates; it cost more to move a barrel over a few miles of muddy road to a railway stop than to transport it by rail from western Pennsylvania all the way to New York. The teamsters’ stranglehold on transportation led to an ingenious effort to develop an alternative—transportation by pipeline."

https://github.com/achatham/epub_speedread

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.

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.

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?

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.

Well, two ways to make that true!

And then an explosion of underground bunkers and volcano lairs.

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.

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.

Level 2 and 3 are the mostly-automated version, and they differ in how much notice they're supposed to provide and how much attention they require.

You seem to be comparing an actual, private tech project to what you wished public transit looked like, not what it actually looks like.

Public transit is awesome, but construction costs in the anglophone world are bananas (https://transitcosts.com/).