4 ms·

If I had to guess why, maybe because PowerShell is a little “busy”. It always feels unclear whether he was trying to make something similar to Unix Shell or a s

If I had to guess why, maybe because PowerShell is a little “busy”. It always feels unclear whether he was trying to make something similar to Unix Shell or a shell for the .NET environment. It’s greyed somewhere in between in a confusing and inconvenient way. Something as simple as a diff requires using objects, it just doesn’t feel like it was designed with SysAds in mind. My guess was it had to do with marketing, sort of like how JS started off as a Scheme dialect, but higher ups enforced Java Syntax. .NET was pretty new at the time.

luma 4y ago
As a sysadmin, you can pull pwsh from my cold dead hands. Evrything being an object is a feature, not a bug. Going back to bash feels like going back a half century.
- cm2187 4y ago
  It has its rough eges though. The one that pisses me off is psremote. Complex to set up, takes forever to come online after a reboot, runs in a network context which isn't allowed to interact with certain windows APIs, not the least windows update. How you create a remote shell that cannot do something as simple as updating the OS is beyond my comprehension.