Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
While checking for the latest version of a shopping cart app that I use I came across a post regarding the next revision. They are taking a poll to see if it should be in Perl or PHP. I offer a snippet of their downside to using Perl. I don't mind them moving to PHP, I just want to be sure they aren't spreading falsehoods about our beloved Perl.
"The downside to Perl seems to be it's future more than anything else. Right now the Perl5 codebase has stopped being developed (at version 5.8.0) and Perl6 is in the works. Perl6 should be ready for production within the next couple of years and will be an awesome scripting language. The problem is that Perl5 code will not run on Perl6 without translation (a complete re-write of CCP in Perl6 code). Initially webserver support for Perl6 will be limited and some of the CPAN modules used by CCP will not be available immediately. Windows support may be lacking as well.

Another downside to Perl is it's *apparent* lack of market share when compared to PHP. When looking at resources sites two years ago, Perl scripts numbered around 3,000 and PHP scripts numbered around 400. Now most resources sites show around 3,500 Perl scripts and 5,000 PHP scripts. There are two factors at work here: (1) PHP currently is a much more actively developed language, and (2) The PHP scripts available are generally one-off works that do small specific tasks - there are exceptions in the forum category, whereas the Perl scripts available are robust programs. Perl is still the de-facto language for e-commerce on the Net.

The Perl6 re-write probably will cause migration problems in the future. This *apparent* lack of market share may be affecting the marketability of programs written in Perl like CCP.


In reply to Perl myths ? by trs80

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, 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, 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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Domain Nodelet?
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this?Last hourOther CB clients
    Other Users?
    Others having an uproarious good time at the Monastery: (5)
    As of 2024-09-11 22:52 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?
      The PerlMonks site front end has:





      Results (15 votes). Check out past polls.

      Notices?
      erzuuli‥ 🛈The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.