Hacker News new | ask | show | jobs
by arp242 748 days ago
It's fine to put ~/.cache on tmpfs, but doing it by default for the general case is going to cause a lot of hurt.

My ~/.cache could be rm -rf'd without too much worry right now, but that doesn't mean that persisting it isn't useful. For example on my system right now:

- Browser cache is useful to persist, especially with some larger sites.

- I put my Go module and build cache in ~/.cache, and while that can be deleted it's useful to persist because it make builds shorter, and avoids having to (re)-download the same modules over and over again. Note that at the moment my internet is kind of crappy so this can take quite a while.

- Some other download cache things in there, from luarocks, xlocate, few other things.

- I store psql history per-database in ~/.cache/psql-dbname. It's useful to keep this around.

- Vim backup files, persistent undo files, and swap files are stored in ~/.vim. The swap files especially are important because I want to keep them after an unexpected system crash.

Some of this is solvable by moving stuff to other directories. Others are inherently unsolvable.

I also have just 8G of RAM, which is fine but not fine for storing ~/.cache in RAM.