4 ms·

Off the top of my head: native hashmaps. Native JSON marshalling/unmarshalling. Native HTTP calls. Control structures that don't suck (ie, bash doesn't even sup

• barrkel 11y ago
  `test` (aka [) is a bash builtin, FWIW; integer comparison works perfectly well inside (( )). I generally prefer bash for job control and pipe parallelism. For more complex tasks that would require a hash, internet access complex parsing etc., I tend to write a script in a different language, and plug it into a pipeline with bash. The lack of parallelism in PS is the second biggest reason I don't use it. The single biggest reason is bash is my common interface across Linux, Windows (cygwin), OS X and Solaris (when I used to run it).
  • bkeroack 11y ago
    > The lack of parallelism in PS is the second biggest reason I don't use it. I've done parallelism in PS, it's not difficult[1][2]. IIRC there were some gotchas, but it's certainly possible. > For more complex tasks that would require a hash, internet access complex parsing etc., I tend to write a script in a different language, and plug it into a pipeline with bash Right, you have no other choice in bash. Powershell lets you do all that within the language itself trivially. 1. https://technet.microsoft.com/en-us/library/hh849693.aspx https://technet.microsoft.com/en-us/library/hh849693.aspx 2. https://technet.microsoft.com/en-us/library/hh849718.aspx https://technet.microsoft.com/en-us/library/hh849718.aspx