Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Alternative title: Modulism - Code Bigotry

When scanning CPAN in that "Surely there's a better way" mode, I use some heuristics (read:prejudices) which roughly sort modules into the good, the bad and the kooky.

I'll search in the problem area, pop tabs for each module, then kill tabs based on the feeling I get from the docs. I'm talking about modules that do address your problem, but in such a poor way that you're better off without them.

I'm interested other peoples red-flags during this initial appraisal. Obviously, they're not absolute and will vary according to the general problem and specific context.
Update: The answers so far have largely been too sensible and rational. Express your inner bigot.

To start out, here's some I've managed to untangle from that "blargh" reaction.
Red Flags:

  • Any of the usual code red-flags which are noticable from the module's docs: it reinvents wheels, uses globals, magic numbers, ... These have been done elsewhere.
  • Massive, nested structures passed into new().
  • It's callbackwards. Requiring an entire callback architecture when a few more methods would do.
  • It parses pseudo-perl data structures or expressions.
  • big_procedure_names_containing_pseudo_arguments
  • It has a "send email" option.
  • Or more generally, the "but wait there's more..." interface. I can use the Extra::SteakKnife module myself, thanks.
  • It's general purpose templating ignorant.
  • Names like EZBlah, or HTML::* (Well, I am more skeptical in the HTML:: namespace than in B::)
  • Tied tightly to a given architecture/set of modules. Double red-flag if I'm anti the prerequisites.
  • The language is uncomfortable with perl terms: we pass in what is known as a "Hash Reference"...
It's not all bad, the above often have converse green flags. Here's some more:
  • Notes on portablility, standards compliance.
  • Intelligent notes on bugs, limits, caveats, subclassing
  • Version numbers and updates, some features marked still experimental.
  • Super-star author.
  • XS version of some critical routine
So what have I missed?

In reply to CPAN Module Evaluation Red-Flags by bsb

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, 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, 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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others exploiting the Monastery: (7)
    As of 2021-04-21 18:52 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      No recent polls found

      Notices?