Should the cache directory live in $HOME by default? about peru HOT 3 CLOSED

In general, this seems to add complexity (see list of cons) for the sake of speed (see "list" of pros). As already mentioned, there are other battles we can fight to win speed; I'm not convinced this is the one to focus on, especially since it will likely burden users with complexity rather than just our code.

The behavior today is understandable, unsurprising, and tends to work well. A shared cache makes "building in space" harder, and today may actually break that mantra, no?

Personally, I haven't experienced any notable pain yet using a per-repo cache, but I also do not execute cleans very often. How much of an impact do we expect this to have on our most compelling use cases?

from peru.

My workflows tend to be trigger happy with git clean, so maybe I'm overestimating how much a normal user is going to blow away their cache. I think if we both set PERU_CACHE in our shellrcs that would be a red flag, but if you don't set it I'm less concerned.

from peru.

I do not set PERU_CACHE. I've done it by hand to experiment, but I don't script it.

There are clear benefits (speed!), so it is worth mentioning in README.md, but I'm not sure it actually needs a lot of attention.

from peru.