Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

Dear monks,

What would be considered as the present day, state of the art, cutting edge, poster child applications to showcase the Perl language nowadays? In the web arena, most of today's popular applications are written in PHP, from Mediawiki to Joomla, from PHPBB to Wordpress. Meanwhile, the Perl projects that are still around are those that were started years ago. Newer projects seem to be seldom written in Perl, but in other languages like Ruby and Python and Java. Examples include control panels (cPanel vs Plesk, Ensim), accounting/business (SQL Ledger vs Compiere, Tiny ERP), bug-tracking/development assistance (Bugzilla vs GForge, Trac, Redmine) and of course the above-mentioned Perl->PHP web apps.

Replies are listed 'Best First'.
Re: Poster child applications?
by BrowserUk (Patriarch) on Jul 19, 2007 at 03:39 UTC
    A reply falls below the community's threshold of quality. You may see it by logging in.
Re: Poster child applications?
by Cody Pendant (Prior) on Jul 19, 2007 at 07:20 UTC
    I was considering asking a question somewhat like this -- there don't seem to be many big-name applications out there, but I think at least part of the issue is that those applications need to be, as much as possible, write-once-run-anywhere, and run-easily too. PHP is everywhere and doesn't require people to chmod their files to be executable.

    So in the area of "just ftp your files and go", Perl isn't as widely represented (although MovableType and its variants are all Perl and a very big in the blogging world).

    What you'll get in the Perl side of things is powerful, detailed, much-tested modules and frameworks, and you build your own application on them.

    Last year I spent a lot of time fiddling about with Joomla and Drupal and Wordpress, hoping to adapt them for a site I created. They had many features, but most of them I didn't want, and the ones I did want were fiddly and complicated with hundreds of little files twenty levels of "include" deep, so I gave up on the world of "applications" and I wrote my own. I used DBD, CGI and HTML::Template. The files are small, the code separates display and programming completely, and the application does only what I need to and nothing more.

    I would probably think about using CGI::Application or something next time, but still, I wouldn't get a PHP application and try to wrestle it into submission. I'd get the powerful tools I already know how to use and build up.

    So even if there aren't many monolithic apps out there branded "Made With Perl", I bet there are thousands of smaller ones which quietly do exactly what their creators want.



    Nobody says perl looks like line-noise any more
    kids today don't know what line-noise IS ...
Re: Poster child applications?
by perrin (Chancellor) on Jul 19, 2007 at 05:06 UTC

    Amazon.com. Ticketmaster.com. Slashdot.org. Livejournal.com.

Re: Poster child applications?
by wfsp (Abbot) on Aug 26, 2007 at 10:08 UTC
    The website I maintain has a dozen or so 'daughter' websites. Half a dozen of those are active - updated a few time a week. These all use PHP engines and the others would if they could get backsides into gear.

    I was fortunate enough to meet up with some of the other website admins earlier this month. None of them were geeks of any description. They had been asked to do the job and they were doing the best they could. These websites are important but not core business. They're as interested in the hows and why fors of their websites as they are intrested in which press the printers use to print their newspapers.

    Uploading a new article to their website is relatively straight forward and the task is shared out with little trouble.

    My site owners ask "why can't we have that?" I've held them off but if, for any reason, they find themselves with a new siteadmin they will.

    I've been asked to help out with any new sites that come along or with existing ones that are relaunched and I had to agree that they would use Drupal. The arguments lost.

    This is all at the low/small end of the market, shared hosting, no mod_perl ("Have you restarted the web server?" "What?!"). There is a gap before you get to the enterprise stuff mentioned in this thread and I think it will get wider.

    A year ago I had a go at writing a trivial "hello world" CGI::Application that could be used as a basis for a new website. It was a failure (no one felt inspired to comment on it) but it did reveal, to me at least, how much work/skill was necessary to even get that far.

    If you're starting out now on a small scale and deciding what to use would you start with Perl?

    Does it matter? Should anyone care? No. The OP asked a reasonable question: "what are the poster child applications now a days?" Due to the nature of the beast there aren't any.