miniblog.

Shower thought: using a tool like cargo-semver, could you build a package registry where the uploader never chooses the version number? E.g. your last release was 5.2025-09-13 and you've just changed a type, so today's release is 6.2025-11-05.

One nice feature of cargo that I wasn't previously aware of: you don't need to do anything after updating your Cargo.toml. In npm, you need to remember to `npm i` after changing package.json. It's not declarative and the state can get out of sync.

Is there any relationship between language adoption and the size of its standard library? These days it seems completely orthogonal, but early Java adopters spoke highly of the collections library compared with C++. Maybe it's the widespread availability of package managers?