http://www.perlmonks.org?node_id=246239


in reply to Re^2: Convincing co-workers to learn Perl
in thread Convincing co-workers to learn Perl

>> Next time, educate yourself before blindly insisting that Perl is the right tool for the job.

Our project is written in Java and I don't insist that it should be re-written in perl just because I think perl is better. I don't advocate to blindly use of any technology

In this particular case, perl *is* the right tool for the job because we plan to support only HPUX or may be windows... and perl runs quite fine on them

When I have more time, I will re-write the same program in perl and then demostrate it to my colleague on how much better the perl program is than his shell script. That is one way I hope to convince them.

After reading this post I realize that I shouldn't have given the impression shell scripts suck...(When I saw if statements ending with a fi, I laughed and laughed)

regards,
Abhishek.
  • Comment on Re: Re^2: Convincing co-workers to learn Perl

Replies are listed 'Best First'.
Re^4: Convincing co-workers to learn Perl
by LAI (Hermit) on Mar 27, 2003 at 18:32 UTC

    Yeah, the first time I saw the if/fi construct I boggled. Even better is case/esac. I remember my prof's explanation of it: that *nix shell scripting was thought up by people on lots of drugs. I don't know for sure how accurate that is, but it seems to fit.

    I personally am of the 'if it can be done with Perl it's probably better off done with Perl' camp. That said, nothing would ever get done without shell scripting (I am so not writing any of my rc.* in Perl), but in my experience it is most useful for simpler tasks. A shell script gets bulky and unreadable pretty quickly.

    LAI

    __END__