|
|
Posted by Jonathan N. Little on 10/09/65 11:31
Greg N. wrote:
> mbstevens wrote:
>
>> w3c validator,
>> bringing together the desperate Human Genome Project codes,
>> http://www.stanford.edu/class/gene211/handouts/How_Perl_HGP.html
>> ...and consider these
>> http://perl.oreilly.com/news/success_stories.html
>
>
> These arent't answers to my question "what is it that perl can do so
> much better than PHP"?
>
> - the w3c validator - well that's an app that happens to be written in
> perl. So what?
>
> - How Perl Saved the Human Genome Project - well, that was 1996, there
> was no PHP at that time yet.
>
> - the perl success sories on the oreilly web page - well, oreilly has
> been making a ton of money with perl books for about 15 years now, while
> their business in PHP books is less than a third of that. No wonder
> they put together a web site advocating theitr strongest turnover item.
> PHP is, despite its power, so easy to learn, and so well documented
> on-line, that there istn't that much business there for a book publisher.
>
> The question remains, what is it that perl can do so much better than PHP?
>
Not having a gazillion core functions to remember would be nice! ;-)
Seems the designers of PHP never heard of function arguments, what's it
like 8 separate functions just to sort arrays! I like Perl's sort. The
Perl=>PHP transition been a bit frustrating having to keep PHP function
index open at all times.
With respect to CGI, Perl is more abstract but compact with the CGI.pm
than PHP. But I must say that PHP's ability to intersperse bits of code
thought static HTML with the common namespace has made it a better
choice for dynamic page creation. I still prefer Perl for for the
'behind the scenes' management functions...
--
Take care,
Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
Navigation:
[Reply to this message]
|