The main benefit that you will get from migrating to PHP from Perl cgi is the same benefit that you would get migrating to mod_perl: speed. I've noticed a certain painful shock that Perl programmers go through when they first have to use other languages such as Java or PHP. Usually it's accompanied by occasional exclamations such as "G___ d___ it, why the f____ is this so f___ing complicated. I could f___ing do this in one mother-f___ing line of Perl. Why the f___ do they have to write this piece of s___ in <INSERT LANAGUAGE HERE> anyway?" etc etc... In calmer moments around the watercooler they attempt to make up for their past public rudeness by extolling to everyone tales of the wonderful things that they did with Perl in the past.
PHP is a lot better compared to my days when they paid me to program in PHP2. It's does, however, still have a long way to go to catch up with the CPAN.
()-()
\"/
`
In reply to Re: php, eh?
by ignatz
in thread php, eh?
by dlink
-
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.
|
