On 8/29/06, Frank Wiles <[EMAIL PROTECTED]> wrote:
On Tue, 29 Aug 2006 20:27:02 +0200 Based on what I've read recently performance is comparable. They are both free so I'm not sure what you mean by cost.
I meant cost with respect to the machine resources: mainly, memory and processor time. Thanks a lot for the various references that I am going to absorb.
Personally, I avoid many applications written in PHP due to their past security histories. I know this is a broad generalization, but I do tend to look over a PHP application much more closely than applications written in other languages. It isn't so much the language itself, but the programmers PHP tends to attract I would wager.
About security (as an example), I remember to have read somewhere that Apache::DBI can be dangerous because of the sharing of the DB connections and the openness of Perl - a malevolent user could try (and succeed) to access connections of other applications as they are running in the same interpreter. But, there are no such issues in PHP as well?
Apart from being entirely different languages, the biggest difference is that PHP is only useful in the response phase of the Apache cycle, where mod_perl can be used to actually configure and completely control the Apache webserver from Perl.
Alright. That's one main distinction for me to remember: it sums up points to Perl (at least to those who can take advantage of that). Regards, Adriano.
