In the same way, seeing that something is possible gives hope to the people who are making those open models that you want.

I mean, come on, let's drive some competition on something other than profit. If someone wants to buy the greenest compute they can, and they can afford a slightly higher price, let's empower them to do that!

But hi, if I spent $10,000 on a piece of hardware, let me program the metal, thanks.

Now I think "guard rails" is the thing I'm hoping for. Your car actively tries to prevent accidents.

Then, I think once that's seen as working really well, I think what's next is that it will become prohibitively expensive to insure your car without keeping the guard rails on all the time.

I hear Flock cameras have even more valuable materials inside them.

The money comes out, but the cops show up.

https://www.youtube.com/watch?v=Y-A8xvFKaRA

Is here okay?

I want to have physical storage over here, and logical storage over there, and I want to control the mapping from one to the other. I want to talk about encryption, replication, latency. Make "time machine" available on this logical storage. And then I buy some new physical storage, and it joins the story. This physical storage is over at my friend's house for backup. This physical storage is slow and archival. This is a device for writing archival media, and there's a brand new media in it, go ahead and write to it. Show me the health report on all of the physical media, and show me what you've done to protect the logical storage. Graph my usage and make suggestions about when to add more physical storage.

Buying physical storage with power and wifi, and configuring it with a QR code that's on an e-ink display - seems like it should be the most obvious thing in the world, that we should all be really used to doing by now.

What am I missing?

But that to clean up a codebase requires even more people.

So, at first blush, it looks like "more people = more problems," but if you actually give yourself some breathing room, the code can get cleaner with effort.

How will they achieve cleaner code, with fewer workers? Seems like a well-intentioned platitude.

That's the only way this thing adds up in my head.

https://www.midjourney.com/medical/scan_gallery

I look forward to the benchmarks, but am highly skeptical.

Looks like operational transforms to me.

The doc claims it's the first with this technique. A 30 second search reminded me of Darcs, and taught me about Pijul, and Weave. And yes, Google Docs storage works the same way - there are probably papers documenting how efficient Google Docs storage is, but it's not wrapped up in a full VCS that folks can use.

The example in the doc uses text, and unfortunately I think it's for a reason. I think with large, binary game assets, the most common operation is going to be strings of "replace A with B", and depending on your chunk size relative to the distribution of changes you make on your assets, I see it as pretty close to a wash, for efficiency. Especially considering that content-addressable blocks also solves de-duplication, which for a multi-game studio is probably going to be significant. Especially if they're managing multiple releases, patches, development branches, etc.