Define "a lot."

A non-zero amount of unnecessary, repetitive, boilerplate code. You know, the kind we laugh at Java programmers for having to write because they can't say say 'Hello, world!' without creating classes and class methods and conforming to the proper signature of the main() method in a class of the proper name stored in the proper place in a filesystem hierarchy.

If you're dumb enough to write code like that, I don't want to use it.

If you're bad enough at communicating that you have to resort to personal attacks to punctuate your points... well, you're free to use software to which I've contributed anyway, because that's what free software means.

If your code imports random modules into my code....

If my code did that, I wouldn't use it either. Fortunately, it doesn't. It does exactly what the documentation says it does. You're also free to read the implementation to see exactly what it does. It's short. It's simple. It's straightforward. Certainly you're more than capable of verifying for yourself what happens.

If you can't either type out your boilerplate of choice or get your editor to do it for you, you probably shouldn't be a programmer.

If you don't see the value of removing boilerplate and preventing its spread and ensuring that no one—especially a novice‐ ever has to worry about setting up the proper editor or understanding all sorts of crazy black magic to grovel in an attempt to convince Perl to help him when it's perfectly capable of doing so, well, we have very different ideas about what makes a programming language usable.

Note, for example, how much more test code people have written in Perl since the advent of Test::More and the removal of "black magic here... don't edit" at the start of every test.pl file you could find on the CPAN circa 2000. That's no coincidence.

Other people don't want your religion.

Histrionics have no place in serious discussions of programming.

In reply to Re^6: Should Test::Most import strict and warnings? by chromatic
in thread Should Test::Most import strict and warnings? by Ovid

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.