You can use tmux, vim, sed, awk or whatever binary you want from PowerShell. Those are binaries, not shell commands.
You can use pipes, redirects, stdin and stdout in PowerShell too.
I personally don’t regularly use any object oriented features. But whenever I search how to do something that I don’t know what to do, a clear object-oriented result is much easier to understand than a random string of characters for awk and sed.
Mixing the two philosophies of coreutils and unix bins and whatever is happening in PowerShell seems even more unholy to me than the phrase “object oriented result”, but different strokes.
I gave up on PowerShell on Windows as a plausible alternative to Bash on Linux the minute I realized there’s no real equivalent tocat, there’s type or if you hate yourself - Get-Content which is aliased as cat but doesn’t really work the same way.
If I can’t even very basically list a file irregardless of what’s in it, it’s just dead out of the gate.
On Linux, I once sent myself an MP3 from my server to my laptop with cat song.mp3 | base64 -w0 > /dev/tcp/10.10.10.2/9999 because I cba to send ssh keys.
I’ll give modern windows a few points - the new terminal emulator application is sweet, and having ssh makes it easy to login to remotely.
PowerShell is a strange programming language that makes me wish I was just writing C#.
Bash is a shell language. At its heart it’s a CLI, emphasis on the I, it’s the primary way of interacting with a computer, not a way to write programs. Even awk is arguably better suited.
That’s why it neither needs to be verbose nor readable for complete beginners, you memorize it the same way you memorize where buttons are on a keyboard or what items you can expect in a right click context menu on Windows.
Most bash scripts people write are far too complex for it and could stand a rewrite in perl or python or heck, what I think actually works amazing as a “scripting language” - C.
I’m one of those that use PowerShell on linux.
You can use tmux, vim, sed, awk or whatever binary you want from PowerShell. Those are binaries, not shell commands.
You can use pipes, redirects, stdin and stdout in PowerShell too.
I personally don’t regularly use any object oriented features. But whenever I search how to do something that I don’t know what to do, a clear object-oriented result is much easier to understand than a random string of characters for awk and sed.
Mixing the two philosophies of coreutils and unix bins and whatever is happening in PowerShell seems even more unholy to me than the phrase “object oriented result”, but different strokes.
I gave up on PowerShell on Windows as a plausible alternative to Bash on Linux the minute I realized there’s no real equivalent to
cat, there’stypeor if you hate yourself -Get-Contentwhich is aliased ascatbut doesn’t really work the same way.If I can’t even very basically list a file irregardless of what’s in it, it’s just dead out of the gate.
On Linux, I once sent myself an MP3 from my server to my laptop with
cat song.mp3 | base64 -w0 > /dev/tcp/10.10.10.2/9999because I cba to send ssh keys.I’ll give modern windows a few points - the new terminal emulator application is sweet, and having ssh makes it easy to login to remotely.
PowerShell is a strange programming language that makes me wish I was just writing C#.
Bash is a shell language. At its heart it’s a CLI, emphasis on the I, it’s the primary way of interacting with a computer, not a way to write programs. Even
awkis arguably better suited.That’s why it neither needs to be verbose nor readable for complete beginners, you memorize it the same way you memorize where buttons are on a keyboard or what items you can expect in a right click context menu on Windows.
Most bash scripts people write are far too complex for it and could stand a rewrite in
perlorpythonor heck, what I think actually works amazing as a “scripting language” - C.