FreeIPA is fine, and I don’t care much about the GPO aspect of Active Directory. But the standardization-by-ubiquity that made it easy for everyone to just follow along and make it so it Just Works has been a godsend.
Yes Microsoft built on the shoulders of giants but trying to make things work with OpenLDAP or the other also-ran directory services was a nightmare.
It’s much better now, I put off moving from cmd until somewhere around 2015 when I was using ‘invoke-command’ constantly, over the last decade or so I’ve moved to powershell proper cmdlets… Its actually not that bad.
You explode lists manually into items when calling commands on a variable list of arguments instead of “quoting variables” to prevent them from exploding.
Who came up with the bullshit idea that exploding strings into words is such a common use case that this footgun is preferable to have an “explode lists” syntax?
Errors. No more set -euo pipefail; shopt -s lastpipe to beat some semblance of sanity into bash
One of the things I really like about PowerShell is the “verb-noun” convention. It makes things a lot easier when learning by examples. Wtf is a sed or an awk? But New-Item -Type Directory oh yeah that makes sense.
Get-OutOfHere
Powershell is probably simultaneously the best and worst thing Microsoft has ever created
Second best. The best was Active Directory.
Tell that to the Linux folks
https://sh.itjust.works/comment/26521372
I am the Linux folks.
FreeIPA is fine, and I don’t care much about the GPO aspect of Active Directory. But the standardization-by-ubiquity that made it easy for everyone to just follow along and make it so it Just Works has been a godsend.
Yes Microsoft built on the shoulders of giants but trying to make things work with OpenLDAP or the other also-ran directory services was a nightmare.
I remember powershell being extremely slow to start on my laptop and sometimes slow to catch up to my typing (and I’m a slooow typist).
tbf it was the win 8.1 days, dunno if it’s better now.
Really liked using it tho. At least it used my actual keyboard layout, unlike cmd.
It’s much better now, I put off moving from cmd until somewhere around 2015 when I was using ‘invoke-command’ constantly, over the last decade or so I’ve moved to powershell proper cmdlets… Its actually not that bad.
It’s better now
Then give nushell a go. It’s basically a modern implementation of some of the better ideas Powershell had.
What were those?
Types.
You explode lists manually into items when calling commands on a variable list of arguments instead of “quoting variables” to prevent them from exploding.
Who came up with the bullshit idea that exploding strings into words is such a common use case that this footgun is preferable to have an “explode lists” syntax?
Errors. No more
set -euo pipefail; shopt -s lastpipeto beat some semblance of sanity into bashOne of the things I really like about PowerShell is the “verb-noun” convention. It makes things a lot easier when learning by examples. Wtf is a
sedor anawk? ButNew-Item -Type Directoryoh yeah that makes sense.To be fair, the comparison there is
mkdirwhich means make directory, but I don’t doubt there are better examples.Unironically though. It takes time because it’s structurally different than python but it’s fun when you figure it out
This but unironically
It even kind of suck as a Windows-only shell…
Honestly it’s pretty good, but it’s very verbose in its commands and output.
The default settings are irritating but it takes only minor tweaks to make it tolerable (mainly fixing the tab completion)
It’s nicely consistent with its object handling.
As a windows shell it is head and shoulders above cmd.exe. I’ve thought about using it on Linux but there I like fish better.
Big oof