a_t48

Can also help if you can remove IR filter + add an IR noise projector

I once lost out on 3 months severance and a laptop when I quit a place and they shuttered two and a half weeks later. There had been no direction from the top for over a month other than "ehh, do something useful". I was working remotely and slowly going crazy.

  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.

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

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.

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.

In some sense, yes.

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.

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.

Ah yeah, I was thinking humans

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