macOS is instead a consumer-electronics abstraction layer for non-technical users, that relies upon and integrates with a UNIX backbone.
Which is to say: Apple (unlike Microsoft until PowerShell) has always assumed that the people who want to get fiddly technical stuff done, know how to use a command line. macOS's "power tools" are CLI tools. macOS's GUI programs, on the other hand, are for the 80% use-cases of regular users. They don't expose niche use-cases, because that functionality was already exposed just fine by a CLI tool, and power users can just use that CLI tool.
Another example of this: a lot of things that would be exposed as checkboxes in some arcane MMC snap-in in Windows, are just exposed as "defaults write ..." in macOS. Why bother building a GUI for a rarely-changed, technical setting, when the CLI is already a perfectly good one?