The packages that didn't want to leave
Everyone writes up the modules that came out. The decisions that mattered were the four packages I decided to leave exactly where they were.
Tags
8 pages
Packaging
I graded every package for how badly it wants to leave
Twenty-seven packages, four marks each, out of ten. The interesting column wasn't the one I expected, and one row explained the whole programme.
The repo that downloaded 170 gigabytes
An hour to compile and 170GB of artefacts to clean up afterwards. Rust has a built-in answer to that, and I only used half of it.
A format per module, not a fatter config core
Viper reads a dozen extensions. Mine reads one, and the other formats live somewhere else entirely. Here's what that bought, measured rather than asserted.
One cache key per lockfile filled my runner's disk
The documented cargo cache key gives every lockfile its own cache. On a self-hosted runner that fills the disk. Whose disk was the advice for?
An encoder on borrowed time
The last US AVC patent expires in November 2027. Until then ffmpeg-wasi's H.264 encoder ships on sufferance, on Cisco's binaries taught to run under WASI.
Stop installing the same tools on every pipeline job
Nearly every CI job began by fetching and compiling the same tools. Baking them into one image instead, and what that saved per pipeline.
Why my photo app won't build for Windows
Dropping the Windows build of a photo tool rather than fixing it, and why that is the right call for a one-person project.
