It isn't about the configurability; but rather, the default configuration.

Facebook offers secure messaging, but the default is insecure; and to use it, you have to reconfigure it every time. Why? Because they don't want you to use it.

And so it is for the Critic. The defaults are such that they neuter Perl, rendering it verbose, stilted and gutless; Java with sigils.

But far worse; it gives a stick to those, without the knowledge or judgement to make informed decisions, with which to beat those who could. It sets an arbitrary and capricious standard by which those, without the capacity and drive to learn the language, can hamstring those who have taken the time and effort to do so.

And worst of all, it implies without stating, some utopian view that compliant code will be good code; and non-compliant code is "bad code".

Yet, it is easily demonstrated that you can take code that doesn't work and make it fully compliant; and it still won't work.

And equally, take thoroughly tested and exercised working code; and it will flag up a gazillion red-herrings.

It is dumb pretending to be smart; rote pretending to be intelligence; it is the failed writer turned film critic; the failed sportsman yelling advice to the professional and berating the referee/umpire.

It has done more harm to Perl -- by confirming and legitimising every uninformed and malicious opinion of the write-only language -- than any other single thing barring only PBP.


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^3: perlcritic compliant way to eval? by BrowserUk
in thread perlcritic compliant way to eval? by KeighleHawk

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.