amos“every rust project has a billion dependencies”
oh no they made code composable oh nooooooo should we call someone??
rust has a lot of problems, but let me tell you: “micro libraries” isn’t one
splitting packages per concern is good for build performance, it’s good for review, it’s good for API evolution.
the problems are technical (compiler perf), financial (funding OSS), human etc.
Martin Geisler@fasterthanlime > splitting packages per concern is good for build performance, it’s good for review, it’s good for API evolution
I do agree with this in the abstract, but there are certain corner cases where many small crates don't work super well.
In Android, we vendor all dependencies and each crate import requires its own approval: someone checks the license, someone else check the unsafe code, etc... We are working on improving the process, but right now, importing 20 crates takes weeks.
@fasterthanlime The problem here is a mix of process and tooling and we're improving both at the moment. Realistically, non-Cargo based projects like #Android and #google3 (based on #Bazel) has to write tooling to align with the expectations of Cargo. We haven't always been super good at doing this, but we're improving 😄