[lug] BASH Scripting book recommendations?

[Jeffrey S. Haemer]

A serious question, for which I can think of two serious answers

(1) Horses for courses

Some problems are better solved in the shell.  "Better" can mean faster to
code, easier to maintain, or more suited to the language in other ways.
 It's the same answer for "Why bother to write in Perl?  Every system I
work on has Java."

(2) Most programming isn't writing code.

Most programming is maintenance -- fixing someone else's code.  (Or your
own that you wrote so long ago that you don't remember why you wrote it
that way.)

Sometimes, especially in a Linux world, that code is in shell scripts.
 Even if your fix is a Perl script, you often have to be able to read, and
sometimes debug, the original code.  If you're facing this, bash is a
different enough language that even knowing a bunch of C or Perl or Python
or Tcl may still leave you at sea.

On Tue, Dec 27, 2011 at 12:51 PM, Rob Nagler <nagler at bivio.biz> wrote:

> Probably not what you want to hear, but....
>
> #!/usr/bin/<your-favorite-interpreter>
>
> Why bother scripting?  Every system I work on has Perl, Python, Tcl,
> etc.  Sometimes I have to modify shell scripts, but usually that's
> system config so I program the mods in Perl and write tests against
> them.
>
> Happy New Year!
>
> :)
>
> Rob
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
>



-- 
Jeffrey Haemer <jeffrey.haemer at gmail.com>
720-837-8908 [cell], http://seejeffrun.blogspot.com [blog],
http://www.youtube.com/user/goyishekop [vlog]
*פרייהייט? דאס איז יאַנג דינען וואָרט.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20111227/dbc6ee51/attachment.html>