The only criticism I could have of Linux filesystems is that user mounted devices show up in /run?/media/<user>/<device> rather than ~/media/<device>. Otherwise everything a user does or makes is showing up under ~ somewhere, and the superuser's stuff resides in a mix of /etc, /root, and /usr.<p>Well, I'll take that back, the fact the config folder is hidden by default is also kind of sucky, and the habit of some software putting configuration data in ~/.local/share and some applications putting non-config data in ~/.config is extremely annoying but should be solved on a per-application basis.<p>Just a few offenders on my desktop in config:<p>* Chrome/ium stores extensions in .config rather than share. Those take up 600MB each in my config folder on my system.<p>* Qupzilla has a profile network cache of 32MB in config.<p>* Brackets has 14MB of cache data in config.<p>* Clementine puts its indexing databases in config.<p>* Spideroak puts everything in config - its index database and snapshots.<p>I'm not as familiar with offenders putting configurations into share, but I know at least KDE's kscreen puts monitor layouts in share/kscreen when they belong in config/kscreen.<p>I'd like to see Ubuntu, Arch, or Fedora (the big distros with the market share to push for best practices) enforce disk quotas on config directories - ie, a program cannot use more than 5MB of space there, akin to localstorage's limit and the intent to use it as a config store rather than persistent data store which is what indexdb / share are.<p>Also, .config should just be config. No dot. Users need to configure their stuff, they should be able to see it.