The one time I can think of where I really had to research a bunch of modules to find something I wanted to use in production was finding something to use with XML. I downloaded and tested a whole bunch of modules. I poured over their documentation. I tried using each one in a scaled down prototype of what I would eventually try to do with them. And then I decided.

My basis was everything. How easy was it to use or learn. How complete it was feature-wise (YAGNI-be-damned, I didn't want to wait until I needed it before asking the module author to implement it). How useful it would be in not just this program, but other programs in the same field (learn one technology, reuse that learning in many places). And, how perlish it was. Some of the modules were thin wrappers around underlying C code with the barest of syntactical sugar to at least make it conform to perl (converting char*'s and int's to plain scalars, for example). Others not only believed in TIMTOWTDI, but were, by themselves, MTOWTDI.

I obviously picked XML::Twig. Which of yours you should pick? I don't know. But maybe the above will help you figure out how to pick one.

In reply to Re: Which packet sniffing module should I choose? by Tanktalus
in thread Which packet sniffing module should I choose? by pileofrogs

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.