My experience has been the exact opposite. Bash, when properly learned, is very powerful and, what's more important, SELF SUFFICIENT.
Ruby and Python either make for very long scripts to accomplish even the basic tasks or pull in a gillion libraries as dependencies, which turns it into a sysadmin nightmare. BTW, the process helper library you linked to is a classic example of that.
My personal preferences for scripting: bash when possible, Perl when necessary, Python if you're adventurous and NEVER Ruby.
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great summary.
I've written a ton of bash.
My rule for writing bash is to write as little bash as possible.
Anything with any sort of even mildly complex logic, use a modern scripting language - Ruby (my preference) or Python.
I've also written github.com/thewoolleyman/process_h... which makes dealing with subprocesses much nicer in Ruby.
My experience has been the exact opposite. Bash, when properly learned, is very powerful and, what's more important, SELF SUFFICIENT.
Ruby and Python either make for very long scripts to accomplish even the basic tasks or pull in a gillion libraries as dependencies, which turns it into a sysadmin nightmare. BTW, the process helper library you linked to is a classic example of that.
My personal preferences for scripting: bash when possible, Perl when necessary, Python if you're adventurous and NEVER Ruby.