Quote:
Originally Posted by farkedup
When it comes down to being able to serve thousands to hundreds of thousands of pages a day that is where perl becomes a limp dick at an orgy... useless and out of place.
|
You are probably referring to perl cgi. PHP has the same 'limp dick' problems if you use it via the traditional cgi way. If you want to compare apples with apples then you have to compare mod_perl with mod_php and perl cgi with php cgi. If you compare mod_perl with mod_php you'll not only notice that mod_perl is faster than mod_php, it's also a lot more powerful. Mod_perl lets you to directly use all of the apache API in perl. PHP (mod_php) only allows you to control the content (response) phase of the Apache server.
When you request a page from an Apache webserver, the request goes through several processing phases (authentication, logging,... the response phase). The response phase is what you work with when building a perl cgi script or a php script. It is the part of the process that generates the actual HTML page and returns it to the browser. Mod_perl gives you the ability to replace the default behaviors of any of these processing phases with your own phase handlers.
Quote:
Originally Posted by farkedup
Perl is more of a server maintanence type language.
|
Perl is more a do-whatever-you-want-from-webscraping-to-putting-satellites-in-orbit type language.
Quote:
Originally Posted by farkedup
I would worry about learning ruby before bothering going BACK to perl. Perl is something I used a LOT 10 years ago but everything else has moved on and perl hasn't really.
|
Learning perl is hardly going '
back'. LOL