Earlier quoted context omitted.
PowerShell is completely suitable. People are just used to bash and don’t feel the incentive to switch, especially with Windows becoming less relevant outside of desktop development.
Powershell feels like it's not built to be used in a practical way, unlike Unix tools that have been built and used by and for developers, which then feels nice because they are actually used a lot, and feel good to use. Like, to set an env variable permanently, you either have to go through 5 GUI interfaces, or use this PS command: [Environment]::SetEnvironmentVariable ("INCLUDE", $env:INCLUDE, [System.EnvironmentVa…
[Environment]::SetEnvironmentVariable($name, $value, "User")
You have un-necessarily used a full constant to falsely present it more complex. Please also note that you have COMPLETION. You are not forced to type that out. Second, you can use an alternative Set-Item HKCU:\Environment\MY_VAR "some value"
Third, if you still find it too long, wrap it in a function: function setenv($name, $value) {
[Environment]::SetEnvironmentVariable($name, $value, "User")
}
setenv MY_VAR "some value"
Also, can you please tell the incantation for setting an env variable permanently in bash ? You cannot since it doesn't exist.Powershell's model is far superior to Bash. It is not even a contest.