in reply to Choosing modules - community matters or just technical merits?
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.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Choosing modules - community matters or just technical merits?
by Anonymous Monk on Feb 02, 2008 at 17:55 UTC | |
by redhotpenguin (Deacon) on Feb 03, 2008 at 20:37 UTC |