simmonmt

The town is pretty wild too. Well, in a not wild sort of way - at least in winter.

It's one thing to read most residents live in the same apartment building. For me what really brought it home was seeing for sale flyers on the bulletin board in the coffee shop: "For sale: a table. Questions see Bob in apt 23".

The sight of an indoor playground complete with swing set was fun too.

Crude oil is sketchy stuff. All sorts of VOCs, etc evaporate from it. Some valuable, some, flammable, some will merely kill you. Keeping it confined makes all that more manageable.

Maybe? If you assume a cell can just disappear at a moment's notice, then I'm guessing you don't even try backing it up. Whatever goes into and out of the cell (request logs and results) gets backed up, and no doubt that's more complicated than a monolithic system, but it may not be so bad assuming the replay systems and global transaction router do their thing?

Yep. When did virtual screens come in? My last full time experience with X was with Xsun in the early 2000s under Solaris. There was a shared cursor, I thought you could drag windows between monitors, but I also thought the DISPLAY variable was different for each (though I could be misremembering)

This is pretty cool - especially that it's at the point where it can be used with a real window manager.

I'm curious why multiple screens is considered legacy baggage and thus out of scope, given how common multiple monitor setups are these days. I also have zero familiarity with X internals, so don't know if multiple monitor support is a horror show that'd be miserable to support.

This was one of the reasons given, at the time, for why Netflix created fast.com. It's served by the same infra that does their streaming, and is thus difficult for isps to game. That is, it'd be hard for them to do some hack to make fast.com numbers without also benefiting Netflix streaming performance in the bargain.

I mean ... step 1 is probably fixing the part where it lands in the ocean, falls over and explodes. Once they've done that and can get their hands on the tiles I'm guessing they can continue to iterate there until they get a more easily reusable design.

It jumped out at me too, but because I wondered what it would look like in the AI version of this story. Having had it build the SQL version do you ... a) miss the leap because you don't understand how it works, don't care to know, and go off to vibe the next thing b) ask it lots of questions because reasons to develop that deep understanding then make the leap or c) rely on it (prompt: "this can't be good enough do better") to go make the leap for you.

(Assuming for the sake of argument that you guided it to the SQL version first)

That's true, but the human can do a much better job planning for the journey if they know what to expect along the way.

One example, from the end of the journey: knowing in advance where the actual entrance to the business is, or the specific curb cut that leads to the residence, makes it easier and far less error prone to decide exactly where the journey should end. Even humans have a hard time figuring out the right access point for a business or residence. This is a job for an offline process, fed by as many data sources as possible.

> When they want data about a school intersection in SF at a certain time of day, they just... synthetically generate it and simulate

I think it's more about detecting changes to the world. You need boots on the ground, so to speak, to see that new speed limit sign or the new lane paint. The Waymo vehicle can no doubt react to changes in the world when it encounters them, relaying them back to the mothership, but it's better to know about them in advance.

I think he meant a very small (stub) MEMORY.md whose sole contents are something like "don't write here - write there".

If you consider say elevator music - music that's just there to fill space, rather than to be listened too - then I don't think there's that much difference between using AI to produce it and using AI to produce clip art or boilerplate code.

That's an anti pattern, at least the way we use it. If you need to add complexity, you define custom functions. If that's not enough, CEL probably isn't the right choice, and you'd be doing yourself no favors banging it into that square hole.

Interesting. I made the same jump and noticed a huge increase in speed and decrease in memory pressure (the likelihood that iOS will kill an app I've switched away from). I miss the physical silent mode button though.