How is Perl fitting for software that is developed by one team and maintained by other teams? What characteristics make it suited for long-term maintainability?

The requirements-for-the-language section is meant to make that tie. It seems I need to be a little less obscure. Also, see below for why some of that was left out.

I think this is a great start, but it's still a little too one-sided to be convincing to those not already convinced.

I agree, this piece isn't advocacy per se, it's sort of a prelude to advocacy. The intended audience was Perl Monks. It's also just a meditation, not really an essay (yet) -- it's meant to sort of foist my thought process into a place where I can get some meaningful discussion on the idea. I had to ramble on a bit about the background so that the couple of paragraphs that represent my point had some context.

I'd love to see a revision based on feedback received here and after you've written the opposite piece. Then it might well be the kind of stuff TPF can use for advocacy more broadly.

If I get some meaningful feedback, I will probably do a few more meditations to flesh out the remaining arguments. Based on the feedback from those, I will consider writing an actual essay, which I suppose I will post here as well.

Thanks for the criticism and encouragement, too!

<–radiant.matrix–>
A collection of thoughts and links from the minds of geeks
The Code that can be seen is not the true Code
I haven't found a problem yet that can't be solved by a well-placed trebuchet

In reply to Re^2: The Enterprise Language Trinity by radiantmatrix
in thread The Enterprise Language Trinity by radiantmatrix

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.