It is really weird, yeah. Half the commands are actual sentences. Tbf most of the common ones have shorter aliases (test-netconnection -> tnc, clear-itemproperty -> clp, get-content -> cat, etc).
The killer feature of PowerShell imo is the -WhatIf flag. I wish all shells had something like that, it’s fantastic for testing scripts without risk of damaging anything.
I love its Verb-Noun system and verbose parameter names. It’s easy to understand what command or parameter does just by the name. Get-MailboxPermission probably retrieves mailbox permissions, Stop-Process stops process, Remove-ADUser deletes AD user etc. If there would be no auto complete I might find it irritating, but once you get a hang of it, it’s a breeze.
Ofc they do. But most users don’t use it at all. Even most windows admins (based on my experience) don’t know PowerShell which doesn’t mean they know how to use CMD.
They must be some pretty shitty admins then. PowerShell is essential for managing more than a handful of windows boxes. If you’re running server core (which you should be in most cases) PowerShell and rsat are the only way to manage your boxes
Another example is Exchange where all Admin Center (GUI) operations are calling PS commands underneath. Not everything is in Admin Center so you must use PS eventually. Not to mention that you cannot perform batch tasks without scripting.
Another example is boot or login scripts that run on all the servers/desktops to make environment changes you can’t handle with group policy. This person is talking nonsense, they don’t know any windows admins.
Sounds to me like they chose to be helpdesk. It’s nearly impossible to be a windows admin without using PowerShell, unless you’re super old school and use vbs for everything.
If only windows and macos included a terminal…
I hate powershell so much
Why does it have to be so verbose
It is really weird, yeah. Half the commands are actual sentences. Tbf most of the common ones have shorter aliases (test-netconnection -> tnc, clear-itemproperty -> clp, get-content -> cat, etc).
The killer feature of PowerShell imo is the -WhatIf flag. I wish all shells had something like that, it’s fantastic for testing scripts without risk of damaging anything.
I love its Verb-Noun system and verbose parameter names. It’s easy to understand what command or parameter does just by the name. Get-MailboxPermission probably retrieves mailbox permissions, Stop-Process stops process, Remove-ADUser deletes AD user etc. If there would be no auto complete I might find it irritating, but once you get a hang of it, it’s a breeze.
Ofc they do. But most users don’t use it at all. Even most windows admins (based on my experience) don’t know PowerShell which doesn’t mean they know how to use CMD.
They must be some pretty shitty admins then. PowerShell is essential for managing more than a handful of windows boxes. If you’re running server core (which you should be in most cases) PowerShell and rsat are the only way to manage your boxes
Another example is Exchange where all Admin Center (GUI) operations are calling PS commands underneath. Not everything is in Admin Center so you must use PS eventually. Not to mention that you cannot perform batch tasks without scripting.
Another example is boot or login scripts that run on all the servers/desktops to make environment changes you can’t handle with group policy. This person is talking nonsense, they don’t know any windows admins.
They chose to be windows admins.
Sounds to me like they chose to be helpdesk. It’s nearly impossible to be a windows admin without using PowerShell, unless you’re super old school and use vbs for everything.