in reply to Web aps with Perl (6) vs. Longhorn and the Windows API?
where is PHP getting more traction than Perl from?
mod_php is more useful for bulk hosting than mod_perl because mod_php is less powerful. As a system admin, you don't want a user you don't personally know to write a handler, or to be able to do internal Apache things (like play with subrequests and internal redirects). And even though having an eternal interpreter and an API to communicate directly with Apache make mod_perl so fast, not having an eternal interpreter is what makes PHP much easier to work with and much more reliable in case of sloppy programming, and not having that API would comfort sysadmins more. Perl interpreters are very heavy, and that would need to change before a mod_php-ish thing can be made with Perl. The closest thing you can get now is letting the process that handles the request die. You then skip startup overhead by CoW forking, but don't have the risks involved with having your interpreter live on.
Summarized: mod_perl is too powerful to compete with mod_php on the bulk hosting / idiot programmer market, and unfortunately, that's where popularity lies.
Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Web aps with Perl (6) vs. Longhorn and the Windows API?
by theorbtwo (Prior) on Jan 01, 2005 at 10:51 UTC | |
by Juerd (Abbot) on Jan 02, 2005 at 10:55 UTC |