Skip to content

Revert private cache enabled by default#2003

Merged
netblue30 merged 2 commits into
netblue30:masterfrom
SkewedZeppelin:revert-private-cache
Jun 15, 2018
Merged

Revert private cache enabled by default#2003
netblue30 merged 2 commits into
netblue30:masterfrom
SkewedZeppelin:revert-private-cache

Conversation

@SkewedZeppelin
Copy link
Copy Markdown
Collaborator

@SkewedZeppelin SkewedZeppelin commented Jun 14, 2018

Commit caa7ad8 enabled private-cache by default globally.

Should this really be enabled by default? Preventing programs from having persistent cache directories overall has many negative impacts.

  • Most email clients cache emails to allow various functionality and downloading them can take many minutes
  • Caching makes webpages load faster
  • Most music players cache album art from libraries
  • Mapping programs (gnome-maps, viking) don't need to constantly redownload tiles
  • Mesa shader cache improves graphics load performance
  • General waste of bandwith of clients/servers
  • General increase in recomputing things
  • General potential increase in disk I/O

I think it'd be better if we just manually add private-cache only to suitable programs.

private-cache will need to be added to more programs as identified by

grep 'whitelist ${HOME}/.cache' -L $(grep "private-cache" -L $(grep "redirect" -RiL))

grep "cache" -L $(grep "redirect" -iL $(grep "whitelist" -RL))
@Fred-Barclay
Copy link
Copy Markdown
Collaborator

I agree. For those of us who want it globally, we can just add private-cache to globals.local.

@netblue30 netblue30 merged commit 31bb894 into netblue30:master Jun 15, 2018
@netblue30
Copy link
Copy Markdown
Owner

Reverted!

@SkewedZeppelin SkewedZeppelin deleted the revert-private-cache branch June 17, 2018 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants