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.

In reply to Re: Poster child applications? by wfsp
in thread Poster child applications? by Anonymous Monk

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.