P::C is not useful to get accustomed to a wide variety of idioms, patterns and ways of expression, because it reduces the set.... P::C isn't useful to achieve any of those goals.

You keep saying this, and I keep not understanding what you mean. What do you think there is about P::C that makes people turn off their brains and keep generating oatmeal-bland code? Is it the default ruleset (which I agree is definitely not perfect for all purposes, but is highly customizable)? Or is it the idea that someone might criticize code that's not bog-standard shop-standard baby Perl and rewrite it that way?

I've seen code reviews so nitpicky and wrong-headed that they rewrote nice Perlish for-style loops into C-style for loops and missed important things like meaningful, domain-specific names for identifiers and quality of algorithm. Those happen with or without P::C.

I agree that using it to make everyone use the abysmal if (!something...) construct where postfix unless makes more sense is stupid. I've seen people arguing for that based on PBP, and they're wrong.

However, I haven't seen anyone seriously arguing that anyone should use P::C to detect and stamp out deviations from the coding standards across the organization except you and BrowserUk, and that in the negative. That kind of passive-aggressive behavior is actually harmful to development teams, and I agree with both of you that it's counterproductive.

So I really don't understand why you say there are so many people promoting dangerous things with it, at least anyone worth listening to.

Update: Rephrased based on Re^11: Modern Perl and the Future of Perl, as I didn't write what I meant and wrote exactly the opposite of what I meant.


In reply to Re^10: Modern Perl and the Future of Perl by chromatic
in thread Modern Perl and the Future of Perl by chromatic

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.