It uses the LICENSE file as a lock. Before anything else, it reads the package's own LICENSE file and looks for a line that has no business being in a licence:

_sigh_

r2 storage is pretty cheap, all things considered

With all (a lot?) of this language, it's not that it's using new turns of phrases, it's that it will use the same rare but valid phrases over and over. Everybody has their own speaking patterns. But imagine if one person's idiosyncrasies were everywhere. That's what's happened here.

That doesn't seem that uncommon to me. A lot of people have phrases that they commonly overuse. Sometimes quite dramatically. I wouldn't be suprised if that's even more the case when communicating complex topics since, at least personally, once I find an approach that lets me communicate some difficult part of an argument I tend to reuse it.

With my wife's folding Razor, there's a factory applied screen protector.

Z Folds come with a factory applied screen protector too, which i assume i was gp was talking about.

Is the factory applied screen protector user replaceable? Or is it a screen protector in the same way that the glass is 'screen protector'? It's just a part of the assembly?

I've done similar things for large container images. My format allows for using FastCDC to chunk files, but there's a tradeoff between number of shared chunks and between number of HTTP requests. I keep it turned off by default.

It uses some form of keyframing. Not entirely free.

This is a strategy I’m taking as well. Build the tooling that can be integrated into anyone’s platform, over some all in one system that inevitably won’t check all the boxes.

Yes, especially in a field moving as fast as robotics, users need the flexibility to extend the system quickly

Congrats on the launch. I've been in the robotics industry for a decade now, I've seen that boundary lie at many different places. I'm not sure there's a clear cut answer.

Self plug: I'm the founder of Clipper, a container registry that has 10x faster pulls and 7x faster builds over DockerHub, targeted at robotics. I got tired of robotics deploys taking all day and fixed it myself. If you're interested in that or just want to talk shop, let's chat.

What about container registries do robotics companies need that are different from other industries?

Docker is built for web. The mental model is that the internet speed is relatively fast, the image is relatively small, and the device you're pulling onto is starting with essentially no data. All three of these assumptions are wrong for robotics:

  - I've had someone in the Docker discord tell me at length that my container shouldn't be bigger than 1GB, which is impossible the moment you pull in CUDA or any ML libraries.

  - Robots pull over 3G/Starlink/slow customer WiFi

  - Robots are edge devices! They have previous related images, they aren't pulling onto a fresh disk like on web.

It's super common to have a layer in your Dockerfile that has several GB worth of dependencies. If you touch one of the dependencies, it thrashes that layer and anything below it. To quote the CPO from a company I left "Anytime anyone looks at the container the wrong way its a 13g dl over a shit cell connection or starlink". It's extra shit because most of the data the robot is pulling, the robot already has in another layer!

Clipper solves this by breaking apart Docker layers and indexing the files within. When you pull an image it will reuse related files in images you already have on your device. This has other side benefits as well, like being able to mount layers as networked filesystems and much more easily being able to run P2P updates.

It's less that robotics needs a different container registry and more that robotics needs a better container transport, and I've built the infrastructure around it for my registry.

Very interesting. We’ve for sure felt the pain of large robotics images and slow deployments, especially when CUDA and ML dependencies are involved, or when adding a seemingly small ROS package pulls a long chain of transitive dependencies. The file-level deduplication approach is clever. Curious how transparent it is to existing Docker/OCI workflows. Does it require any changes to the client, or it mostly sits underneath the existing tooling?

It mostly sits underneath existing tooling. I replace the push/pull client (run `clipper pull` instead of `docker pull`, and optionally the BuildKit driver (to get build outputs natively in my format). That pull command ingests the image into your chosen runtime, meaning your docker/podman/k8s run commands remain the same. If you're interested I can set up a demo/call/coffee.

Awesome - thank you for the detailed response.

layered rsync, in a sense

In some sense, yes.

This isn’t quite true, is it? A mutation that killed 5 years after childbirth would result in higher mortality rates for the child.

Octopus have extremely high mortality rates and extremely large litters, so there’s that

They don’t raise their offspring

Though FWIW, they do protect their eggs quite well.

Isn't this tied to the senesce? Where their digestive tract has closed and they starve to death at the nest

Indeed, AFAIK. I've never seen an explanation for this. Most things that reproduce successfully want to do it again - or at least their DNA does. Perhaps octopuses are simply disappointed by the experience.

Octopus senescence isn’t a choice. It’s a fully programmed part of their life cycle. There’s a bunch of hormones released by the optic gland that put them in this stage where they stop eating, stop healing, and sometimes even mutilate themselves.

For the mothers, the entire time is spent cleaning and blowing water over the eggs.

It’s generally accepted this behavior is the necessary pair to their high aggression and cannibalism. It’s likely if they didn’t go through this they’d end up eating their babies. By dying, they make way for a new generation. And this is their reproductive strategy. Live a short very active life. If you survive, mate, then die and leave the hunting grounds to the next generation.

That explains how the mutation was promoted

But not whether other adaptations could be possible. Fix the digestive tract issue and keep the female well fed and defending the nest in a different way

There's no single mutation. Nor is their sensecense merely a digestive tract issue. This is a core feature of their lifecycle. If you mutate the genes that make the hormones that trigger it, or the receptors for those hormones, you won't just prevent their sensecense, because those genes have other functions important to other parts of their life cycle.

Ah yeah, I was thinking humans

I grew up in a valley half an hour south of Seattle that at one point was farmland. It was hard to find anything that didn't like the soil, so of course blackberries loved it. The entire back fence of the half acre or so lot was covered in blackberries that we'd have to hack back every year. As a result, we had some of the biggest best tasting blackberries I've ever had. Unfortunately, I wince every time I see a little tiny thing of blackberries at the farmers market for $7. I know there's economic reasons for it to be this way, but it sucks paying money for something I know grows out of the ground for free somewhere else.