I had been somewhat comfortable with the older `netsh` commands from Windows 7. The PowerShell commands are overall richer for being consistent and composable if you're already comfortable with PS, but it does require a learning investment.

My general sentiment is that I am frustrated with tech companies imposing UIs on users. Some examples:

Duolingo changed its interface to this new "learning path" that took choices away from users.

Garmin updated its Connect app with a new UI that (I subjectively feel) shows less information and forces unnecessary compromises.

Microsoft has been messing with the Control Panel for years. The new UI is missing a lot of settings. I don't agree with the Ars article that you only need the legacy Control Panel for esoteric features: I never figured out how to set a Static IP Address in the new Settings app, which is hardly unusual for servers.

I trust it is possible to set a Static IP in the new UI, but I still feel like these changes are unnecessary and unwelcome.

Anyways, I do hope the PowerShell commands will remain stable for the next 20 years.

> We all learned to do it via powershell a couple of years ago

I presume it is documented on answers.microsoft.com. /s

Surely an API would be on MSDN and not the user forum. (also sarcasm)

haha nope!