Hey HN. Clipper is an alternative container registry/pull client/BuildKit driver that can do operations an order of magnitude faster by ditching OCI’s tarball format. I’ve spent the past few months heads down on getting the build side of things fast.
The text boxes on top aren't bad, but the background is a total turnoff, it's a big red flag to me. I'd ditch it, remove the fade-in effect that runs at like 10fps, and rewrite your text.
If any Podman engineers are here: does the new /libpod/local/artifacts/add endpoint let me ingest individual layers? I have an alternative pull client that's currently a little hamstrung on Podman compared to docker+containerd, due to having to convert the entire image to tarball to ingest rather than only new layers.
Hey HN. Clipper is an alternative container registry/pull client/BuildKit driver that can do operations an order of magnitude faster by ditching OCI’s tarball format. I’ve spent the past few months heads down on getting the build side of things fast.
zstd has higher level modes. Default is -3. I saw a good tradeoff between compression speed and ratio up to -9 or so. From -20 to -22 it will use much more memory and IIRC can have downstream effects on decompression speed. I'm using -9 for my container registry and plan to recompress at a higher level for commonly accessed base layers, as well as give customers a button that lets them pay a bit more to do it themselves.
I get this a lot. Yeah, you can have an LLM copy what I've built, no it's not going to be as good unless you also spend the equivalent of the amount of hours I've spent on it.
At least in Oakland, it's the landlord's responsibility to manage pest control. It needs to be done at a building level, or else the roaches will just get shuffled around.
Vulkan is a rendering technology, Unreal is an engine, that can render using Vulkan under the hood. You can absolutely do this in Unreal. I implemented this at Cruise using UE4 for integration testing, and it worked great for inference (we weren't doing training on sim at that point, but I was pushing for it! There was a paper out in 2018 or so that showed mixing in a bit of simulated data had an outside positive impact on the outputted model). There are companies out there right now doing this with even more modern renderers. I can't comment on how much the rendering realism gap matters here. I think there's some people out there using a variant of lower quality rendering + some kind of diffusion to get "better" images without having to do detailed modeling/lighting for their sims (fuzzy memory, I don't have a source on this).
I made Docker not suck for large images. 2-10x faster depending on the operation. I’ve spent the past two weeks burning down the last bits needed to release a BuildKit integration.
I remember this person's blog from before she went on haitus. The drawings attached used to be cute and the header (hero?) image semi-relevant. I hope she brings them back, they had charm!