Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

And here are 11 sometimes rude responses.

  1. LEARNING § this entirely valid point is only entirely valid if the only point is learning; i.e., if this an excuse to do code you expect to be production worthy or vendible, this sloth has a girlfriend, your point is invalid.
  2. PERFECTION § You've confused perfectionism with narcissism. Perfectionist seek the best possible answer, not the best answer they are capable of delivering.
  3. PURPOSE § You don't parse output of things you want to change, you write patches.
  4. APPEARANCE § this is an ideal point for the Kardashians, and businesses bent on irrelevancy.
  5. PORTABILITY § the difference between a file and a folder is insignificant; i.e., everything in one folder is just as "portable" as everything in one file and a bazillion times less confusing for any significant amount of well-written code. Badly written code does indeed tend to be easier to navigate in a single file though.
  6. CPAN ACCESS § see PORTABILITY and a hundred threads on PerlMonks regarding this topic.
  7. COMPILING § see PORTABILITY + pre-compile it on the same system/hardware for binary compatibility.
  8. COMPLEXITY § The instructions for getting non-root local::lib and cpanm are trivial and are basically fix and forget.
  9. SIZE § Without benchmarking, this is bias. Without analyzing which modules vs what code, it might also be upside-down.
  10. LICENSING § Legal issues are outside the scope of dev advice, so, you win this round, Greater Bandicoot!
  11. JOB § Cheating? Installing Moose breaks neither the laws of God nor *man. The laws of tye and BrowserUK however...

Off the soapbox and back to making work less unpleasant for the devs who have to maintain the code I write.

In reply to Re: Top 11 (CAPITALIZED) reasons not to use someone else's Modules by Anonymous Monk
in thread Top 11 (GOOD) reasons not to use someone else's Modules by miketosh

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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 or How to display code and escape characters are good places to start.
Log In?

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

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (4)
As of 2022-01-21 18:43 GMT
Find Nodes?
    Voting Booth?
    In 2022, my preferred method to securely store passwords is:

    Results (59 votes). Check out past polls.