modules that are constantly changing are more scary

Not that I don't agree, but let's not generalize. Some modules constantly change and that might be a good thing :-)

what if an interface changes

You can always write a wrapper.

or a bug is introduced

That's what tests are for. If the author doesn't use them, you can write them yourself (and even if the author refuses to include them, you can run them yourself just to make sure everything's OK). And you can also stay a couple of versions behind at all times.

At least with static code, you know exactly what you've got

Presumably... :-)

In reply to Re^2: Is Spreadsheet::ParseExcel dead? by cog
in thread Is Spreadsheet::ParseExcel dead? by glwtta

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.