This is a pretty poor comparison of the two, especially once it gets into the syntax, of which most of the Bash examples are broken in some way. There’s also a lot of just straight errors, such as mentioning “true” and “false” “values” in Bash, which don’t exist—the userland toolset includes “true” and “false” programs that can be used to inject desired exit code status into some logic flow, but there is no real conc…
Linux Bash vs. Windows PowerShell
11–20 of 93 posts
Re: Linux Bash vs. Windows PowerShell
#12The real difference is: in any reasonable bash script there will be a significant amount of awk, cut, tr and other commands to munge the output of one command into the input expected by the next. In PowerShell that totally goes away.
By 'goes away' do you mean you don't need it or there's nothing equivalent?
Re: Linux Bash vs. Windows PowerShell
#13The real difference is: in any reasonable bash script there will be a significant amount of awk, cut, tr and other commands to munge the output of one command into the input expected by the next. In PowerShell that totally goes away.
Re: Linux Bash vs. Windows PowerShell
#14Re: Linux Bash vs. Windows PowerShell
#15Re: Linux Bash vs. Windows PowerShell
#16Article might be more successful if it demonstrated some of the advantages of PowerShell, such as returning the output as objects instead of lines, and what you can do with them as a result. I'll admit to being in the "Bash is what I know, I'll just install WSL/Cygwin/PuTTY on my Windows workstation and be done with it" crowd. PowerShell is on my bucket list of things I need to learn at some point, or at the very lea…
Prior to this I had never really explored PS, but it is definitely cool
Shameless Plug:
Re: Linux Bash vs. Windows PowerShell
#17@vedipen, thera's a typo in bash "if" example, an if-block is closed with "fi". edit: "if" example also misses a semicolon before "then".
Re: Linux Bash vs. Windows PowerShell
#18The real difference is: in any reasonable bash script there will be a significant amount of awk, cut, tr and other commands to munge the output of one command into the input expected by the next. In PowerShell that totally goes away.