rm -r ~/.foo/cache ~/bar/cache ~/baz/data/app/cache [20 more apps..]
rm -r ~/.cache/\* rm -rf ~/.*/cacheEach of the data, config, and cache envvars would all be set to ~/.data in this setup (though “data” isn’t a name I’d use)
It doesn't seem like you understand much about the specification? I'd recommend reading it, or at least a short summary I've made available here: https://xdgbasedirectoryspecification.com/
There are another 41 things in .config, including Bitcoin, Calibre, Chromium, DjVuLibre, Gomuks, htop, Inkscape, Mumble, OpenSCAD, Transmission, and other things. If I had to choose, I would say that those are the things "going against the grain of the ecosystem". But I think it's fine. As long as it doesn't change in another ten years to be .Config, or .conf, or Configuration, or either Configuration or Configuración depending on whether I installed the machine in English or Spanish. Because then I am seriously going to look into government surplus cruise missiles.
Some of those already do, though. At least Vim and Emacs do, and I personally have zsh in .config as well.
Also, would you please stop posting unsubstantive/flamebait comments more generally? It's not what this site is for, and it destroys what it is for.
Literally every program I’ve installed for the last several months--WezTerm, Neovim, bat, broot and many more just use XDG by default. Most of the time, the user doesn’t have to do anything, though they might initially be confused if they’re looking for their config files.
vs
> the de-facto community standard
Feels like you’re just selectively defining “community” to exclude XDG. Maybe there’s a good reason, but you haven’t really described it.
Whoever defined $HOME as a place to stick configuration files was also “just some group.”
So are ISO, W3C, IETF, etc.
> dropping config files in .programname is the de-facto community standard
Dropping litter and open-air defecation are de-facto community standards in some unfortunate parts of the world. That's not an argument to keep doing it.