have you tried kache? github.com/kunobi-ninja/kach…

lotta work to go before the world rewrites to rust without consequences

Yeah, shocking it was less 1TB.

Yup! I’ve OOM’d my hard drive with rust build targets!

Haha its a nightmare isn't it This helps! github.com/dnlmlr/cargo-clea… There's prob better ways but thats what I use until it gets something native

npm packages have been dethroned

Yeah, it's a problem

Go also build big caches over a period but it builds faster unlike .net or rust.

AGENTS.md: run cargo clean every time the worktree grows over 20gb

yes I am having exactly the same problem, builds taking over an hour as well 😂

that's not a build cache, that's a landfill with a compiler attached 😂 we built kache for exactly this, hardlinks instead of copies so you stop paying for the same crate seven times. Firefox is running it in prod and it's at 826 stars now. link's in @jleni's reply

And here I'm sitting writing skills to cleanup the wsl on my one dev box codex yolos on after each thing it does. (50gb VM disk lol) Otherwise it destroys itself and frustrates me.

Me, every Monday morning: Removed 193020 files, 220.5GiB total

And I thought all my sessions with dotnet/runtime artifacts were high...

One of the only downsides of rust. Rust with IL and CLR-like VM, nuget/dlls instead of clone and build source, and faster builds would be perfect. Said another way, .NET without a 20yo legacy dragging it down (Framework), MSBuild2, and lifetime based memory management, perfect.

Try kache ! @_kunobi_ started this concept of caching for both speed and storage!! Solve target/ mess while speeding up builds. Much before everyone started to be inspired by it. Much faster than anyone else that tries to catch up, and innovating every day with contributions from companies like Apache, Mozilla, SpaceX, and others! follow them at @_kunobi_ They promised to launch a few surprises soon. github.com/kunobi-ninja/kach…

Check out github.com/jdx/mr-boxington

That’s why I quit