Of course, it doesn't help just to complain about the issue in a void, so I've also submitted like 10 PRs and filed quite a few issues. Projects like pnpm and Poetry took note, and now they comply!
Someone's gotta clean up house, and I don't mind doing the dirty work.
You should fix this. While macOS and its system applications and bundled applications don't adhere to the XDG Base Directory Specification; many programs that run on macOS do.
In fact, almost all of the programs you list run on macOS and (by definition) use the XDG Base Directory Specification. So I would clean that up to not give an incomplete statement.
BTW, the macOS directory structure [1] has been documented since macOS (MacOS X back in the day) shipped in 2001.
[1]: https://developer.apple.com/library/archive/documentation/Fi...
Is there an exact phrasing you would prefer?
The classic Unix utilities and apps typically use $HOME on macOS, while their modern, often Rust-based replacements—WezTerm, Exa, fd, broot, Fish, etc.—use XDG.
Vim uses ~/.vimrc while Neovim uses XDG.
Exa is the latest, trendy ls alternative.
I don’t think you should remove the Exa example but you certainly should show how to use ls to do something similar for those people still living in the dark ages—ls was created in the 1970s and it hasn’t kept up with the times all that well [1].
I created an ‘ll’ alias for Exa using the Fish shell; obviously you make shell-appropriate aliases in Bash or Z shell:
function ll
exa --color always --long --no-user --no-permissions --all --icons $argv
end
No need to have a rosetta stone of alternatives to demonstrate an illustrative example where the basic tool that everybody already knows and understands at a glance works.
I'm not saying that exa, or fish, or ripgrep, or any other trendy tool is bad.
I.e. if it's empty, or if the first character is not a forward slash, then use the default?
Admittedly, the ~/.bashrc etc. files should be there too - but I wanted it to look cleaner :P