Why should I, as a Windows Admin, have to write an incredibly long and painfully meticulous netsh command to allow something past my firewall when I can just click my way to network settings?
Step back a second, and ask all of those questions with their Linux counterparts. The answer turns into "BECAUSE THERE IS NO OTHER RELIABLE AND UNIFORM WAY TO DO SO."
Reliable and uniform -- not the words I would have have used in context of windows administration. The problem with windows administration (and I mostly mean 3rd party server software, but also Microsoft stuff) is that often the GUI is the only sane way to do things -- the cli interface, if it exists, is an afterthought. So automating anything is impossible or hard and debugging problems becomes a game of guesswork.
Yeah, that may be an unfair extrapolation from my experience that includes some fairly bad software vendors and it might even be outdated (as I haven't touched windows in years). Still, that is one of the reasons I prefer not to have anything to do with Windows, at home or at work.