Choosing Perl/Python for my particular niche

[U-CDK_CHARLES\Charles]

On 30 Mar 2004 22:23:50 GMT, Fred Ma <fma at doe.carleton.ca> wrote:
> Robin Munn wrote:
>> 
>
> Well, my bout with Perl took much, much more than an hour.
> It worked, though.  It's probably not enough experience to
> get a good look at the strength of Perl.

Well, here's two cents American, leaving the exchange calculation as an
excercise for the reader.

My first task at my last job was to automate a test that could run from
the Solaris prompt.  Knowing C, I tried to script it in csh, which
proved difficult--redirecting stderr was needlessly convoluted.

Then I read "csh scripting considered evil" and decided to give the
Bourne shell a whirl.  Though the syntax had a learning curve, once I
cracked that nut, the project "Just Worked."

Being a C programmer (embedded systems mostly) it was "Easy" to learn to
use Python as "C without the compile"

It took some playing before I realized the strength of Python as a
prototyping language and stopped trying to write C code in Python.

Of course, NOW I'm trying to learn how NOT to write C++ code in
VisualBasic, so go fig.