I'm also surprised "disk space usage" isn't an issue for many. I just cleared out dozens of GB of disk use by Rust, and I had to fix my CI/CD to clear itself properly.

Anyway, interesting results, thanks for posting!

[–] SorteKanin 3 points 1 week ago (1 children)

dozens of GB of disk use by Rust

I was well above 100GB the other day 😅. But I think there's a problem with the setup as well

[–] sugar_in_your_tea@sh.itjust.works 3 points 1 week ago* (last edited 1 week ago)

I've been there. This is just on a small personal project I'm working on every so often. It's a tauri app, so there are a fair amount of dependencies, but certainly not GBs per build.

Ideally, cargo build could be configured to just take care of it. I really don't need anything other than the most recent build per target, and I certainly don't care about stuff from older compiler versions.

cargo-sweep is nice and I use it (that's how I fixed my CI/CD), but it's a little annoying and I don't think a lot of people use it, hence why I expected it to be higher.

[–] Giooschi@lemmy.world 1 points 1 week ago (1 children)

I'm also surprised "disk space usage" isn't an issue for many. I just cleared out dozens of GB of disk use by Rust, and I had to fix my CI/CD to clear itself properly.

For me it's just a matter or clearing the target directories used by older rust releases when I upgrade every 6 weeks. cargo-sweep is a godsend for this task

[–] sugar_in_your_tea@sh.itjust.works 2 points 1 week ago

Yeah, cargo-sweep is nice, I wish it was more automatic. When I make a build, I just want it to clear out old crap. Just keep whatever the latest is for each target.