<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]>
signature.asc
Description: This is a digitally signed message part
