@fasterthanlime while micro-libraries still irk me a bit, my issues with them are not really anything i actually worry about
the major issue with the rust ecosystem is the lack of integration with the rest of the system: vendoring every dependency, no easy way to update them without patching the lockfiles of every package a distro may ship, static linking only, randomly building vendored and possibly outdated c libraries inside build.rs (one of the worst ones), etc
@navi@fasterthanlime I fully agree that build.rs is a nightmare. Everything else you describe is the standard tension between project developers and distro maintainers that is as old as time. 🙂
@tedmielczarek 1.80 releases, breaks the time crate, we at gentoo now have to hunt every rust package that uses directly (or indirectly via a library) and patch the lockfile to use the new version of time
if this was c, c++, or python, or similar, we'd bump the time crate package and maybe trigger a reverse-dep builld, that's it
but rust, (and go and nodejs stuff too, to be fair) require manual patching to bump a dependency, it's kinda really sad and a bit ridiculous imo
but even if you drop the static link point on my post, everything else is way more problematic, vendoring and lockfiles, building random c libs in build.rs
@navi@tedmielczarek And that's with time being merely broken, not something like a security issue in a widely used crate (and pretty sure so far most distros just ignore this when Rust is involved).