Also, the dread of "removal instructions" that include stuff like "go through these directories and delete things that look like they belong to this software".
I used Appcleaner[3] for many years, and it's still perfectly serviceable
I'm keeping my eye on Pearcleaner[4], which is additionally open-source and written in Swift.
[1] https://docs.brew.sh/Cask-Cookbook#stanza-zap
[2] https://github.com/nrlquaker/homebrew-createzap
People should stop worshiping UNIX System V, while ignoring the chaos that came later with the explosion of UNIX clones.
There is a reason why the UNIX authors then went on designing Plan 9, followed by Inferno, while trying to fix what they percevied as design flaws in UNIX, from filesytem, security model, process execution model, and userspace languages.
I won't argue with your point because you are right, I was arguing that at least Linux and the BSDs, despite their stupid hierarchy, at least have standards that assign those directories specific functions. This is in stark opposition with Windows and macOS, where across the years stuff has been chucked basically everywhere (especially on Windows, which is the worst offender in this regard) without a lot of care about what was being put where. On macOS you can find binaries inside frameworks, stuff in /usr/bin, stuff in /sbin, stuff under System, ... and for quite a long time there really wasn't any apparent logic behind it except that it was the most convenient place to put it, similarly on Windows where some 64-bit programs chuck stuff in the 32-bit program application directory just because
Modern macOS separates things that are protected by System Integrity Protection and are unalterable (checksummed) in /System. Everything else, including user-customizable system components go in /Library.
Modern macOS file structure is highly organized and easy to reason about if you have even a beginner’s understanding of its security implementation.
Hmm.
/usr/bin
/usr/sbin
/bin
/opt/bin
~/bin
~/.local/share/bin
~/opt/bin
/include
/lib/include
/usr/include
/usr/lib/include
/usr/lib/clang/include
Why are Linux people always so misguided and haughty?
[1]: for instance, "usr" contains libraries only due to the first PDP7 at bell labs having two disks, the first mounted as /, the second as /usr (user). When they ran out of space under /, they replicated the filesystem structure in their user disk, thus the birth of /usr/bin and the like. When /usr got too cluttered they created /home (or /usr/home, don't recall which)