It is now clear that the article is no longer available so I can't
have first hand information. But the listings on the subject is
clear what the issue is all about. In this part of the world where
open source software is yet to make its impact, the language war
does a lot of damage to our cause here: promote open source
software. I take comfort from the words in Sriram's book
(APP) that man went to the moon amidst the language wars
between two of the dominant programming languages of that era.

So I take the view that it's all about getting a job done. I had a
problem with the computing environment here, looked for a
solution, found perl and have not looked back. In fact, there is
much the language has to offer for me. I take pride in knowing that
the regex of perl is super, and other languages emulate it and
that's one of the reasons why I stick with Perl. I'm aware of what the
other languages have to offer and in fact, standard perl references
such as OOP (Conway) or MRE (Friedl)
all contrast some feature of perl with other languages. That doesn't mean
that
I have to suddenly abandon perl. If I need to do a job, I will find out
first how it's done in Perl and if it can't be done, then explore solutions
from other languages.

Perl for Power, Elegance, Robustness and Longitivity.


Alfred Vahau
Perl Advocate
Uni. PNG

Jeff Stuart wrote:

> <soapbox>
> Ok, I've been watching the list for most of the day and watching
> "bashing" of PHP (which IMHO is idiotic and immature but again, JMHO).
> I have ALWAYS said, use the right tool for the right job.
>
> PHP has it's place.  IMNSHO, it's place is web interfaces.  It's GOOD at
> that.  That's what it ORIGINALLY was designed for.
>
> Perl on the other hand was not ORIGINALLY designed for that (I
> REMEMBER.  I used Perl 4 way back when.  I REMEMBER (VAGUELY) the
> changes between the last 4.X and 5.0 and all the work I had to go
> through with it. :)).  Perl was originally designed for text
> manipulation.  IE PERL = Practical Extraction and Reporting Language.  I
> started out with Perl and C.  Then migrated to mod_perl about 2 years
> ago.  At that time, PHP wasn't up to snuff IMHO for serious work.  It is
> now.
>
> I now use both PHP AND PERL!  IE I have 3 tools in my toolbox instead of
> 1.
>
> I use PHP for the front end web interface.  I use mod_perl for the
> backend work.  IE doing DB manipulations, text manips, sending out
> emails, etc.  I also use straight perl scripts for the above when those
> actions need to happen via cron.  And if I have to, I DO dip down into C
> for those times when I ABSOLUTELY need speed.
>
> I am VERY excited about mod_perl 2.0.  I am looking forward to hopefully
> being able to use it with SOAP to create application servers that ARE
> EASY to work with/write.  (Not like java IMHO :)).
>
> As far as security holes go, ALL languages have em.  Just that more
> people use PHP than mod_perl.  So it's security holes are more
> noticeable.  ANYONE can write insecure apps in ANY language.
>
> </soapbox>
> --
> Jeff Stuart <[EMAIL PROTECTED]>
>
>   ------------------------------------------------------------------------
>                        Name: signature.asc
>    signature.asc       Type: application/pgp-signature
>                 Description: This is a digitally signed message part

Reply via email to