I don't really use many of your criteria at all. I tend to judge based on if its standard distro (AS distro not Std distro), the modules reputation amongst the community at large, and my colleagues and friends here. But the key is usually the test suite it comes with. (I was suprised that automatic testing was not in your list at all.) If it comes with a comprehensive set of challenging tests and succeeds them all I am usually confident enough to use it in dev/test and if I like it and it meets my needs I will use it in production.
BTW, IMO Annonymonk wasn't a troll. If he hadnt said a few of the things he did I probably would have as well.
Cheers, and I hope this thread provides some good nodes, the subject is slightly controversial but also thought provoking. ++ to you.
---
demerphq
<Elian> And I do take a kind of perverse pleasure in having an OO assembly language...
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
