++. Nice piece. I like the attempt to frame the problem and break it down. I particularly like the initial cut at a definition. However, in addition to your definition, I'd like to see how you would include the concepts of architecture and scalability.

I tend of think of "enterprise" activities as having to address issues of scale on multiple fronts, including organizational grouping, geographical locations, heterogeneous processes as well as the usual definitions of scalability from a technical sense. These considerations inevitably lead to questions of architecture to integrate disparate parts of the whole.

Perl meets all of the requirements for enterprise languages

You lay out a broad framework for enterprise software, then narrow in on a very specific set of standards for language and conclude that Perl is fitting for enterprise use. What about the rest of your framework? 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?

I consider myself a Perl advocate.

If you want to improve as an advocate and ensure you avoid zealotry, write a convicing essay that makes the opposite points.

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'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.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re: The Enterprise Language Trinity by xdg
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.