Re: Migrating from PHP to Perl for the web.

If the task is getting the job done and you can do that with PHP why swap?

If you want to do stuff with Perl and PHP together you already can see this

Translating working code from one language to, by definition, untested, not working, not even written code in another language needs a good reason. I am not reading one.

You do need to use mod_perl if you want speed comparable to mod_php as vanilla Perl CGI is slow.

Comment on Re: Migrating from PHP to Perl for the web.

Replies are listed 'Best First'.
Re^2: Migrating from PHP to Perl for the web. by KurtSchwind (Chaplain) on Dec 01, 2007 at 13:17 UTC
I never even knew that PHP::Interpreter existed! This might very well ease any transistion I make. I'm curious as to any limits I might run into if I ran mod_perl as opposed to perl CGI. Do I loose anything on that front? -- I used to drive a Heisenbergmobile, but every time I looked at the speedometer, I got lost.	[reply]
Re^3: Migrating from PHP to Perl for the web. by tachyon-II (Chaplain) on Dec 01, 2007 at 13:48 UTC
mod_perl does not really impose any limits as compared to vanilla Perl - in fact it lets you get up close and personal with Apache if you want. What you do lose with mod_perl as say compared to vanilla Perl is the ability to write sloppy, poorly structured code. I recommend reading this this from the mod_perl documentation before you read anything else. There are a few traps, some simple and some fascinating/excruciating but you need to use mod_perl to get the same performance as mod_php. http://www.linux.com/feature/55807	[reply]
Re^2: Migrating from PHP to Perl for the web. by andreas1234567 (Vicar) on Dec 02, 2007 at 19:26 UTC
Before you jump up and down on PHP::Interpreter, ensure that the thing even compiles on the platform in question. I recently tried myself (on Ubuntu 7.10) without luck. -- Andreas	[reply]