2 ms·
The days when every new Windows feature came with a snazzy UI to configure it are long gone. Realistically, Server 2012R2 was the last release that had full pa
by mdb31 5y ago
The days when every new Windows feature came with a snazzy UI to configure it are long gone.
Realistically, Server 2012R2 was the last release that had full parity between features and matching configuration 'screens'.
Since that time (so: Server 2016, 2019 and 2022, and to a lesser extent the consumer SKUs), configuring new features has required PowerShell and/or WMI. This trend is unlikely to reverse anytime soon. Mostly because features are increasingly complicated.
With Windows 10 and, especially, 11, the GUI parts of the configuration have been redone on a "whatever looks good and is usable for 80% of non-advanced users" basis.
That this now requires "web" technologies is disappointing, but unsurprising. There just isn't a good "native GUI" story right now: not in the open source world, but especially not with Windows or macOS.
- majkinetor 5y ago> configuring new features has required PowerShell Which it should. Window should be PowerShell-first, and GUI eventually. Even more, GUI should use PowerShell so that you can configure stuff via GUI and export the script for automation. This then leaves to anybody to create GUI if they want, and GUI is just a PowerShell frontend.