Community is big. I've seen one major Perl ORM and one major framework get temporarily shut down because of people problems. In one case, a CPAN administrator stepped in to mediate the problem. When the ORM project was shut down temporarily, my first thought was "What will I use if this never comes back?".

I think everyone has had their ego involved with their code at some point or another in their career. I know I have, but I try to make conscious efforts to become detached from it. This is a problem with coding teams, egos clash, and the code goes to shit. That ORM I mentioned hasn't really recovered from the meltdown. I try to keep an open mind, but I'll let you draw your own conclusions.

Be careful of a community with too many zealots and not enough level headed individuals. Enthusiasm is great, but when it turns predatory, or I might even say cannibalistic in the event the predation is towards other Perl modules, people end up looking like idiots and the Perl community as a whole suffers. We're all members of the Perl community.

In reply to Re: Choosing modules - community matters or just technical merits? by redhotpenguin
in thread Choosing modules - community matters or just technical merits? by zby

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.