Re: PHP vs PERL

The PHP/JSP comment from Zeev the other day rings true here too - anything you can do in one language, you can pretty much do in another. (Well, that wasn't QUITE what was said, but that's the gist!) For performance, PHP as an Apache module is great, and personally we've never had much luck setting up mod_perl under Apache. Biggest benefit I can think of under Perl is CPAN - there are loads of modules to do many things, and installing them is as easy as 'install Bundle::Apache' (or whatever the module is). Dependancies are pretty much taken care of, etc., which is a leg up on the PHP side of things. On the flip side, there aren't that many cases where I've needed to do that sort of thing in Perl OR PHP. require LWP::Simple; Then creating an LWP object, passing arguments, etc. is not as elegant as $f = fopen("http://www.mydomain.com","r"); and reading from $f. As someone else mentioned, a lot of people (and sample code) uses CGI.pm. This is a huge monster, imo, which is a lot of overkill for the limited functionality most people get out of it. PHP does many of the same things as CGI.pm out of the box. I think that, written properly, PHP code will be more maintainable and readable 6 months from now than Perl code. It's a bias, yes, but it's a bias that has grown out of using both for the past few years. Sharon Spurvey wrote: > I am trying to convince someone to go with PHP on a project we are > working on. Their response was what can it do that can't be done in > Perl? Now obviously I know several things and reasons to use PHP, but I > just thought I put the question out there to see what additional > firepower I get back :) > thanks > > mdp > -- ========================== Michael Kimsal http://www.tapinternet.com PHP Training courses http://www.tapinternet.com/php