Sure. It mostly isn't a first class customer, however. We may never have "The Year of The Linux Desktop" because of this, but command line configuration in Linux is the first class use case.

I don't agree with the comment you responded to but all server tools for Windows are configured via Powershell, and the GUIs just use the PowerShell Apis.

They started migration back in server 2008 or 8r2 to support Headless/Azure.

The GUI is literally a second class citizen in Windows Server these days.

Fantastic. My experience is that when I have an issue on Windows my searches give me a ton of GUI screenshots, but in Linux I get text file edits and terminal commands. However I may be doing it wrong.

Not wrong, but things change. As far as OS philosophy, Microsoft has changed rapidly in a short time.

Well, if it's controllable through a group policy. Otherwise you'll quickly regress to myriads of registry key incantations. Some things take hours or days to figure out how to configure.

You can do everything for the operating system, sure.

But you often can't script X random Windows app via PowerShell, whereas there are very few Linux tools that aren't first class command line citizens.