3 ms·
Command line wizardry, part two: Variables and loops in Bash
- oh_sigh 5y agoBeing too good at bash is actually a bad thing, because you'll be tempted to reach for it for complex problems you need to solve instead of using a real language
- devchix 5y ago... and for the things within your reach, you will leave a legacy of unmaintainable bash scripts; the inheritors of which will loathe to modify or throw them out all together because of code inertia and their foggy understanding of it.
- sgarland 5y agoKnowledge of how to do something sub-optimally isn't bad. It's up to you to decide where the dividing line is when you should switch to a different language. Beyond that, I enjoy knowing how to do tricky things in the terminal simply for the sake of knowing it. Also, while it's not necessarily a guarantee that Python or Perl will be in a given environment, Bash will practically always exist. I will grant you if you find yourself in this predicament, you should probably be rethinking your build/deploy strategy altogether.
- whatsakandr 5y agoI would say "just use python!" but python, in my experience, has been difficult to keep running on an environment. Bash scripts have thier place, but one must be weary of accidentally writing an unintelligible script.