meh.<p>the pattern I see is people not learning enough bash to use it properly and then complaining about it.<p>nothing new under the sun.<p>I just saw the demo at <a href="https://www.youtube.com/watch?v=T5Bpu4thVNo" rel="nofollow">https://www.youtube.com/watch?v=T5Bpu4thVNo</a> ... I guess time has come for us to launch scripts inside headless google chrome windows? /s<p>on a more serious note... thanks but no thanks.<p>Bash is more than fine. I've said this over and over and I'll say it again: shell scripting is software writing. You can't expect to get correct behavior without understanding your tools and your shell. You can't expect not to do error-checking and corner-case-checking and still have stuff working 100% of the time.<p>I don't like to be rude, but: if you don't do error-checking and blame it on bash when stuff goes down then you deserve what you get.<p>----<p>One could blame it on programs: a shell language is a glue language to chain commands together and to evaluate simple conditions to choose the next step: if existing programs and new programs do not behave consistently, and you have to resort to do weirder and weirder bash kung-fu, can you really blame it on bash?