3 ms·
> But all those arcane commandline wizardry and the configuration madness still irks me now and then I'll take this over the seemingly endless layers of GUI ba
by H1Supreme 6y ago
> But all those arcane commandline wizardry and the configuration madness still irks me now and then
I'll take this over the seemingly endless layers of GUI based configuration screens that Windows servers use. A text based configuration file is much easier to understand, and well, configure, imo.
- wtetzner 6y agoAnd version control.
- alkonaut 6y agoI don’t think anyone wants to maintain windows servers. I have probably 5 or so computers at home, counting various NAS’es and raspberries and such. Most are Linux. All that have a screen however, are windows. A server I have to configure. It’s doing some kind of job. My desktop I just want to plug hardware into and see it work, and run proprietary binaries without ever configuring anything.
- AnIdiotOnTheNet 6y ago> A text based configuration file is much easier to understand, and well, configure, imo. Too bad there are dozens of different incompatible text-based formats for everything... oh and that they completely lack discoverability.
- Pxtl 6y agoIt's better now that Windows has gone all-in on Powershell. Now, I said "better" but still not "good" as the powershell APIs for many critical windows features are a nightmarish trashfire of multiple buggy overlapping implementations of the same thing, but they exist. It is now very possible to admin a Windows box from the console. And as much as Powershell is a bad programming language, it's a very powerful and expressive one that bridges the gap between shell scripting and full-fledged programming.