I was thinking more of one product companies using a $XDG_CONFIG_HOME/Boop Snoot Partners, Inc/<Software Name You Remember Installing>/
convention, which seems to be the norm inside APPDATA%
.
But I take your point. 😊
I was thinking more of one product companies using a $XDG_CONFIG_HOME/Boop Snoot Partners, Inc/<Software Name You Remember Installing>/
convention, which seems to be the norm inside APPDATA%
.
But I take your point. 😊
So much this. It’s like these clowns don’t read the XDG directory spec and think $XDG_CONFIG_HOME
and $XDG_DATA_HOME
are interchangeable, and even that cache files can be in either or both. No, one directory you need to backup for when things go sideways, and the other can go to /nev/dull.
I’m not a fan of ~/.local/share/
being the data directory (two directories deep seems stupid), but it’s definitely where regular data belongs.
Never mind developers who, in 2025, still think their project is special enough for a $HOME
dotfile/dotdir or - somehow worse - those who put $XDG_CONFIG_HOME/<weird-name>/subdir/[subdir/]
. The latter strikes me as well-meaning Windows developers trying to follow best-practice-like-Microsoft-does, but it makes my teeth itch.
Rant over. :)
I don’t mind it with companies that produce multiple products, as nesting them does make sense.
But for one-hit-wonders it’s a bit… 😬