4 ms·
Powershell will probably be fine. Besides them both being a REPL and scripting language they're very different. I guess the simplest way to put it is in powersh
by brazzledazzle 11y ago
Powershell will probably be fine. Besides them both being a REPL and scripting language they're very different. I guess the simplest way to put it is in powershell you're passing around objects and in bash you're passing around strings. That's an oversimplification though. I'd start wondering about powershell's future when bash starts getting the ability to tap into .Net the way powershell does.
- TallGuyShort 11y agoAs exemplified by this announcement, Bash in isolation is not that valuable. It's the standard UNIX tools that most Bash scripts just assume are there that really round it out as a platform. Supporting the piping of objects instead of text? Not such a big deal. Replacing UNIX tools with object versions? I agree - very valuable, but now a massive undertaking involving redefining a lot of flags, etc.
- TillE 11y agoRight, PowerShell is probably irreplaceable as a sysadmin tool. But for other tasks lumped into the "scripting" category, I'd much rather use bash.