[73] in Back_Bay_LISA
Re: perl/noperl
daemon@ATHENA.MIT.EDU (Todd Kaehler)
Thu Nov 19 13:40:47 1992
To: bblisa@inset.com
In-Reply-To: Your message of "Thu, 19 Nov 92 11:40:50 EST."
Date: Thu, 19 Nov 92 13:03:59 +0000
From: Todd Kaehler <kaehler@zk3.dec.com>
*** In message <9211191640.AA01369@oberon.sw.stratus.com> you write:
>
>I was interested in Adam Moskowitz's note about sys admin stuff.
>I don't know perl. My concern is that I don't want to lose flexibilty.
>Using "one tool one task", as Adam calls it, if I find something
Perl is very flexable. Their are things you can do in perl which
you cannot do (well, at least not without adding a c program) using
the unix tools.
>that does one piece of a job, I can incorporate it, rather than having
>to translate it. Conversely, if a multi-task job is slow, I can find
>the dog, and rewrite only that piece.
One of perl's strong points is speed. If your application is running
to slow you can either recode in c or perl. Because you do not need a
long pipeline with perl you are not always exec'ing awk/sed/...
all the time. I use shell scripts most of the time, but when I need
more speed I will use perl. C programs need to be recompiled for
each architecture you are managing where perl, like other shells,
does not. I think perl is just one more tool which can be very
useful to any system admin.
>
>So speaking of dogs, am I being an old dog, unwilling to learn new tricks?
Maybe. Try it before you reject it.
>
>-Tony Rudie
--Todd Kaehler
--
Send mail for the `bblisa' mailing list to `bblisa@inset.com'.
Mail administrative requests to `bblisa-request@inset.com'.
