#2 is not about Perl, the language, at all, so let's leave it at that. #3 seems closely related to #2 -- it may be true that we, the Perl community, have not needed one else we would have created one.

It's not a Perl thing - it's an open source thing. People write code to scratch their particular itches. In the open source world frameworks tend to bubble up from the bottom, rather than be imposed from above.

However, a lot of us also have noticed how other "communities" have developed such frameworks and we have also acknowledged how they have benefited from this.

Like? I'm really not sure what kind of frameworks/communities you're talking about. In general anything with the label "enterprise" is something a company, rather than a community, has produced. It's a marketing term, not a technical term.

If you're talking about things like Rails and Zope then Perl has many similar projects like Maypole, Bricolage, Catalyst, OpenInteract, etc.

That leaves me with #1 and #5. Yes, single point of contact can be a huge issue. "Now, all those who have successfully and satisfactorily called in BEA/IBM/Microsoft/Adobe/Oracle/<your favorite large software developer> for support, please raise your hands... no one?... I thought so..."

I've had some really excellent support responses from Oracle and Sun in the past ;-)

But, as you say, the actual level of support is largely irrelevant. It's all about perception, and having somebody to blame.

Btw, while Ruby is indeed younger than Perl, Python is of about the same vintage. Even in the realm of opensource, non-commercial, non-officially-supported, high price software, "Zope," "Ruby on Rails," and "JBoss" get more name recognition and mileage than CPAN does, in my knowledge.

Now that's a much more interesting question. Although a more direct comparison would be why Rails and Zope gets more press than OpenInteract, Bricolage, Maypole, Catalyst, Krang, Bivio, AxKit, Mason, OpenFrame, etc.

Some reasons of the top of my head:


In reply to Re^2: Enterprise Perl by adrianh
in thread Enterprise Perl by punkish

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.