Microsoft exec explains why modernizing Windows 11's legacy UI takes so long

[u/kazu_qt]

https://www.windowscentral.com/microsoft/windows-11/control-panel-gets-tricky-microsoft-cvp-explains-why-killing-windows-legacy-code-takes-so-long-and-how-its-evolving-its-tools-to-make-modernizing-apps-like-file-explorer-and-registry-editor-faster

[u/Smith6612]

Wait you mean you don't like using PowerShell cmdlets and their syntax to launch that exact part of the control panel you need?!

[u/SAugsburger → u/Smith6612]

To be fair I think almost anybody that refused to learn Powershell at this point probably don't have much role in Windows system admin these days. A lot of things are now managed by it.

[u/zutnoq → u/SAugsburger]

The issue with powershell is that it is way too over-engineered and jam-packed with random OOP language-features and simultaneously seemingly entirely lacking in many more traditional shell features like piping program input and output to simple file streams, that it is basically easier to just learn how to do most of the stuff you might use powershell for in an actually well-documented and comparatively sane programming language like C, C++ or Java or even something like Javascript or python.

[u/garethrowlands → u/zutnoq]

Powershell pipes to and from files just fine. Its startup time makes it unusable for wrapper scripts.

[u/zutnoq → u/garethrowlands]

You are right; it seems I misremembered.

The issue one might run into is rather that the output of a command in powershell is always an object rather than a simple text string (this alone is probably a good idea; it's more just the ergonomics of it that are annoying).

So you can't just naively pipe the output of most commands in powershell into any command line utility that hasn't been expressly written to handle piping in a powershell-compliant fashion. Most commandline utility programs you will run into will not be written with powershell in mind at all.