Your intution is good.
#sccache offers enough improvement that one can be sure it's operating. However, even with a
#Rust build cache that isn't filled, I've seen a build-time reduction of 50% only under ideal conditions and it seems to be closer to 14% in the average case.
For what it's worth, both numbers come from multi-hour builds that ought to have plenty of redundancy for a build cache to squeeze out. However, I've seen other comments online that make points similar to yours.
Regarding the welcome to the crab world, I'm pleased to see a number of interesting tools appear that, in many cases, simply build and work once things are in order. And they do build offline for me now, which is a plus.
It seems similar to the
#Go ecosystem in some respects. I've become attached to a few Go stalwarts such as "gitea", "mlr", and "rclone", and I imagine that similar Rust projects will grow in number and will reach critical mass.
I'm not shy to be a CLI guy and these have fallen out of the Rust sky like CLI pie so far:
alacritty - I'm using this one right now.
coreutils - Same as "busybox" but for Rust.
dog - Instead of "dig". Sure, why not.
lfs - Similar to "df -m" but output is more readable.
macchina - It's not "conky", but it has the basics. Plus a Tux.
mdcat - MD render cat is all that.
names - Fun name generator for repos, etc.
netavark - I gather that "podman" needs this now.
netscanner - Unexpectedly nice network scanner TUI.
pastel - This is certainly colorful.
procs - Credible alternative to "htop".
rg - I've heard about this one and look forward to trying it.
sd - Useful supplement to "sed".
csvlens and xsv - Useful supplements to "mlr".
zet - Useful supplement to "uniq".