Have you considered that other people have usage requirements different from yours?

Of course there's not much reason to complain about System Settings if you never use it, but that's missing the point.

You could copy paste your comment to everyone here, "have you considered that other people use it differently".

That's not all the commenter said. "The moaning and groaning about how bad it is just seems so.....pointless to me."

If System Settings is fine for the commenter, that's great for the commenter. (Although "I virtually never use it" isn't exactly a great response to "It's virtually unusable" or a great defense of System Settings.) However, the commenter is criticizing other people for complaining about it, and that's not justified.

This is exactly how I do it, and I also do it this way in Ubuntu. And in both OSes, I hide docks/apps.

There exist equivalents that have exactly that same functionality as described above. I don't know what GNOME uses, but KDE's krunner searches system settings, user files and applications, bookmarks, browser tabs, solves arithmetic and unit conversions, does spell checking, searches the web, searches active windows, applications and workspaces, etc.. It's configurable with many plugins available. I expect GNOME's system works similarly.

For seven years longer and with 20K more ports than Homebrew, and without leaving a mess on your system or munging permissions, so is MacPorts.

There's still some weird annoyances for me, though. For example, it's still intended for single-user mode only. The best solution I came up with was to create a separate user for Homebrew and then basically alias `brew` to `sudo -H -u homebrew brew`.

And generally, if you attempt to use a non-standard prefix, such as in your home directory, packages will have to be built from source. I understand why, but it sucks because this means when you need x86-only packages via Rosetta, you're stuck with the old `/usr/bin` prefix, unless you want to and can build from source.

Also, in general, maintaining multiple prefixes/architectures is annoying too. I wish the default command allowed me to just pass `--arch amd64/arm64` or something when installing packages

Goofy shit like this randomly happens, particularly after OS upgrades. I remember some crazy hell where I couldn't finish the OS install on a new Mac, because Apple decided that Apple IDs must be email addresses, and my ancient ID was not. Required a call to customer support.

And the "untrusted developer" shit always bites me in the ass every couple months or so... It is particularly painful when using pro audio interfaces, which will just suddenly stop working every now and then. It requires a magic key-press during a reboot to clear some kind of special RAM.