4 ms·
When actively developing Python projects, running uv a dozen times per hour isn't unusual. Those seconds add up fast. Whereas freed disk space remains unused.
by Xirdus 1mo ago
When actively developing Python projects, running uv a dozen times per hour isn't unusual. Those seconds add up fast. Whereas freed disk space remains unused.
- pas 1mo agowarm cache case is only imperceptibly slower, no?
- Xirdus 1mo agoTrue, haven't read the source and only went by what the other commenter said. But one could argue 500MB more free space is similarly imperceptible.
- Timon3 1mo agoThere are still many environments with <=250GB, below that I wouldn't call it negligible. And let's not forget that the price per GB has appreciated a LOT!
- Xirdus 1mo agoThey're likely the same environments that can't keep warm cache in memory, so the performance penalties are higher too.
- kekebo 1mo agoYou could reverse the last sentence to "freed disk space reduces the need to clean the hd". And I don't even mean physical limitation as much as the compulsion to manually clean ballooning cache dirs once in a while.
- Xirdus 1mo agoOverprovisioning also reduces the need to clean the disk. I've had a terabyte Macbook for over a year, developing in 7 different tech stacks simultaneously, never cleaning anything up manually, and I still have over 60% space left. It's a tradeoff between wasting a little time everyday vs. wasting equally little time every year or so but also having the mental load of cleaning up plus maybe existential dread vs. spending more money to never have either problem. I do understand the last one isn't an option for everyone, but if it is, it's absolutely worth it.