github.com/ScoopInstall...

WinGet still struggles with environment variables (PATH) and portable apps. Scoop extracts apps to `%USERPROFILE%\scoop`, so you don't need admin permissions. I use Scoop for all CLI apps, unless I use a tool specific version manager (fnm for js, uv for Python).

Scoop the package manager, awesome for installing CLI tools _and_ adding them to PATH.

Since the end of January? No, it's been available for Mac and Linux for many years. devblogs.microsoft.com/powershell/p...

Sure, I get that. Looks to me like you want three states for an input type that has two; either enabled or disabled. Maybe I'm just dumb and don't get it, that's a possibility too. 😊

You want to treat -s:$false as true?

$PSBoundParameters.ContainsKey('s') will return true if both -s and -s:$false.

I don't see a problem. Why would you not want -s:$false to result in $s.IsPresent => $false? You've then set the switch to false, as in -not $s.IsPresent. Expected behavior IMO.

Windows PowerShell ("powershell") is preinstalled. PowerShell Core ("pwsh") is not.

Azure Automation Account has PowerShell v7.4 in preview, you just have to create a custom runtime environment, which also is in preview. 🤦🏻‍♂️

If all those modules used Assemly Load Context (ALC), it wouldn't be a problem. PowerShell should try to enforce or push this as a best practice IMO. Created a discussion for it some time ago:
github.com/PowerShell/P...

And heres a great video woth Andy Jordan explaining it:
youtu.be/__J7b84BAmQ

Thats Windows Terminal, not PowerShell. 😊