I work for a local PHP webshop. Getting them to switch over to Perl is an uphill battle all the way, mainly because my boss thinks that having a PHP code base is more accessible to potential new employees. I don't share the same view, but i do like to get paid, so i don't complain much (coding in PHP is worth not having to sacrifice one or two hours out of my work day driving to the big city).

Personally, i would love a PHP to Perl tutorial, and i have really considered writing one myself (or it's counterpart - PHP for Perl coders). PHP, for those who have not written web apps with it yet, can actually be nice. But ultimately i feel that PHP offers power to those who are not ready for it yet - it is just too easy to shoot your head off with PHP, especially if you have register_globals = 1 in your php.ini file (which i'll wager most sites unknowingly or uncarringly do). It does have PEAR, but PEAR is no CPAN. I can't remember who said it, but i believe that PHP really is not a scripting language ... it is a templating system. The fact that you can write shell scripts in PHP is merely a convenience - PHP was meant for the web.

Like simon.proctor said, PHP enthusiasts are not going to like the slower CGI model - a tutorial would really have to delve into mod_perl to show the real power of Perl over PHP (and hence, graduates the 'tutorial' to a more advanced audience). I feel that the majority of PHP's audience are simply not ready that power or too reluctant to give Perl a fair chance. How many PHP programmers actually use preg instead of ereg? Ugh ... now i am starting to change my mind. :)

Off topic: have you perused the PHP Cookbook yet? Essential for any PHP coder's library.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

In reply to (jeffa) Re: php to perl by jeffa
in thread php to perl by parasew

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.