> I feel like the author really overstates how hard it is to make a new crate. I read it more as the maintenance overhead when publishing. You need to bump ver

> I feel like the author really overstates how hard it is to make a new crate. I read it more as the maintenance overhead when publishing. You need to bump version, check dependency versions etc. I'm speaking from personal experience here. The more I split my crates into sub-crates, the longer the release/publish process takes. There are some parts you can automate with e.g. cargo-release but I now think a lot harder before cutting a release to crates.io. I also have the gut feeling this is happening throughout the ecosystem. I have a lot more overlays in my Cargo.tomls now than I used to, two years ago. I.e. there are PRs and fixes in the repo. that you need but the author hasn't cut a release. This may be coincidence ofc but I can't help but think there may be a connection.