Well, I am currently developing a web application for our helpdesk. It relies on a MySQL-database and the frontend is done in PHP. The app is (at the moment) used for customers mail queries. Right now, I consider porting it to Perl, and this is what came my way:
- PHP is much faster than plain Perl/CGI. (No wonder, it's an Apache module.)
- Mod_perl might be as fast as or faster as PHP (I'm currently figuring out.)
- Developing in PHP is quiet easy: besides the already mentioned automatic variable creation, I find it very handy, that you can put your PHP code directly into the HTML page. You don't have to wrap all your HTML into print() calls.
- I really miss a PHP-CPAN. Because the app is more or less an email client, I have to deal with attachments and stuff. Finding a working, MIME-handling PHP class was really a pain, Perl has great MIME modules.
- PHP can natively do HTTP Authentication. Simply send a 401 header and find username and password in special variables.
- If you need database support, you have to recompile PHP (which is rather annoying). Perl just needs the proper DBD-module.
Just my .02 cents.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|