3 ms·
As an ancient UNIX person, I've always loved PowerShell from the start. I remember the first time I played around with the first version that wasn't a download
by jasoneckert 4y ago
As an ancient UNIX person, I've always loved PowerShell from the start. I remember the first time I played around with the first version that wasn't a download (2). I wanted to see how it dealt with objects, so I ran something simple:
$ui = (Get-Host).UI.RawUI
$ui | Get-Member (to see the methods and attributes available)
$ui.WindowTitle = "Hello World Window!"
After that, I was hooked. PowerShell providers and modules are incredibly useful, as is piping output to Out-GridView. Later versions have introduced more cmdlets that, quite honestly, everyone should use instead of DOS commands (e.g., Get-NetIPConfiguration instead of ipconfig). I do remember a bit of timing issues (often solved by inserting Start-Sleep) and other general flakiness like others have noted here, but the ones I've noticed were fixed in later versions.
- deafpolygon 4y agoI've been using some form of *nix since 1997? Pretty much since I had my first computer. I was very late to the party - didn't touch a computer until college! I've used Windows on and off throughout those years (gaming, mainly). Using PS is a joy, I've re-written all of my usual utility stuff from bash/zsh to PS inside a few week, and managed to improve on a bunch that I didn't want to do before because bash is painful to debug/test/etc. I rarely fire up WSL now, and it has replaced Python for my general utility scripting language. Note: if anyone is reading this - if you're still using PS5 built into W11, then you owe it to yourself to install PS7 (it can be installed alongside 5). It is invoked via pwsh rather than powershell, and can be setup to use the same startup scripts as the default PS.