Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It avoids the realization that you have been paying AWS to back up ~/.cache and ~/.local for the last 6 months.


The whole point of .cache is that it's supposed to be that one folder that you know you shouldn't back up. As opposed to a dozen different app-specific ones that we have today.


Yes, it's a great idea in principle -- and would be even better if its location were configurable, per the XDG spec.

My comment wasn't meant as a criticism of the basic idea of a standard directory scheme; it was a reply to someone asking why anyone would ever care about files you can't see.


Point of order: Some of us really want ~/.local backed up or otherwise persisted; I've got the equivalent of a second /usr in there, and I only don't worry about "backing it up" because ~/.local/etc is in version control, and the rest is installed by my setup scripts.

~/.cache can burn, though:)


The article says the standard is to put data in ~/.local/share/

So I guess if any of your applications have important data, you better back it up! (I learned today)


Keybase stores 1.1 GB of garbage* in mine. I think it's a cache of the network filesystem.

* My definition of "garbage" in this context is stuff I don't miss if I wipe the machine, reinstall the OS and the app, and sign in again.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: