It's Because They Are Telling You Something About Your Code; It's Buggy!!!!
Worse than people of turning 'strict' are the people who don't understand 'strict' or 'warnings'. People who think that 'strict' or 'warnings' issueing warnings conclude the code is 'buggy' don't understand 'strict' or 'warnings'. And are hence not qualified to use it.
Yes, it's good to turn on strictness. It's good to turn on warnings. But it's only useful if you understand the messages it issues. Its messages indicate the code may have a problem spot. But it doesn't have to be, and perl may be wrong to. The conclusion that "oh, it gives messages under strict/warnings, hence the code is buggy" is too shortsighted, and a signal of poor understanding of Perl.
Note that I'm not claiming the code you refer to doesn't have bugs - it probably has. I'm just ranting about your generalisation.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.