perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric <>
Subject Re: Why I use mod_perl (PR stuff)
Date Wed, 09 Jun 2004 20:57:03 GMT

This is a very good example of why it is pointless to get into, Perl can do this and PHP can't.

The fact is, much of that is crap if you dig enough. Just like saying C can do something Perl
can't, big deal, Perl can use the C code and move on.

The reason I avoid PHP in particular for big applications is that as soon as I start writing
PHP code I am surrounded by examples and a culture that wants to hack it to finish it, and
who cares if you really understand what is going on or if it is secure. Easy overwhelms all
other considerations.  Yes, of course there are people doing the right thing and trying to
do MVC with PHP, but that is most defiantly the exception. 

In the very near future I am going to be working on a distributed shopping cart system, a
part of it includes PHP, but it only does very lightweight stuff like tracking sessions and
making XML::RPC requests to the local mod_perl app server. This allows me to provide some
PHP candy for the HTML developers, but to keep the major stuff OOP mod_perl.. 

If we ever do need to change to another system, the fact that we have separate content and
code, and mostly :) OOP programming, I expect will make that conversion a lot easier making
the basic system outlive even major changes. If we had been hacking away just solving the
problem of the moment, then if that big change comes, we might as well start all over again.
What a waste that would be.. 



At 01:42 PM 6/9/2004, Chris Shiflett wrote:
>--- James G Smith <JGSmith@TAMU.Edu> wrote:
>> PHPUnit is available, first release was April, 2002.  First
>> production release was mid-March, 2004.
>I didn't say this stuff was old or mature, just that it exists. :-) Truly,
>PHP feels like it is just now reaching the maturity level that Perl
>enjoyed as much as 10 years ago or more. Of course, Perl is much older, so
>this is to be expected somewhat.
>> Didn't find anything for `embedded documentation'
>There is PHPDoc, which is basically the same thing as JavaDoc. Perl's
>options may be much better, but you can poke around on a site that uses
>PHPDoc here:
>> Didn't find anything that indicated I could choose to require
>> variable declarations before referencing them.
>PHP handles this sort of thing with error reporting. A reference to an
>undefined variable throws a notice, and by default, PHP's error reporting
>doesn't alert you to notices (only warnings and above).
>A common recommendation is to develop with error_reporting set to E_ALL,
>and display_errors enabled (and of course to initialize all variables).
>Then, in production, log errors instead of display them (or in PHP 5, set
>up a more professional system altogether). At any rate, using E_ALL is
>basically the same thing as use strict.
>Report problems:
>Mail list info:
>List etiquette: 

Lead Programmer
D.M. Contact Management
250.383.0836 ext 229 

Report problems:
Mail list info:
List etiquette:

View raw message