3 ms·
In my opinion this is not just for scale. In my opinion anything more than a one-liner is too large of a scale for bash. More thoughts on this: https://blog.ha
by thomashabets2 5y ago
In my opinion this is not just for scale. In my opinion anything more than a one-liner is too large of a scale for bash.
More thoughts on this:
https://blog.habets.se/2021/06/The-uselessness-of-bash.html https://blog.habets.se/2021/06/The-uselessness-of-bash.html
Another piece of evidence is that I do many many code reviews. Not once have I reviewed bash script changes that did not have subtle bugs that would bite us in real life. Not once!
- mixedCase 5y agoDoing all my scripting in Go because some people don't care to learn bash seems like a small version of hell. If I'm using bash, I just need to glue a few tools together and I've most likely decided already that concurrency more complex than simple wait(1p) is unnecessary, and that fine-grained error handling is unimportant. If I really cared about those things, I'd probably use something like Haskell that actually improves on error handling, unlike Go, or if I'm scripting something for a specific software project, whatever that project's language is.
- thomashabets2 5y agoIt's not so much about them not knowing bash, as it takes MANY lines to do things correctly sometimes. Per the example in my blog post full of mkfifo and stuff. But sure, my choice is Go. You do haskell if it's best for you.