The way its use is being advocated is for some person or core of people to sit around a table and consider each of its gazillion settings in turn and decide, once and for all and in the abstract, which of those all future (in-house, in-dept etc.) code will have to comply with. And that is wrong.... Why those who are advocating the use of P::C are doing so, is because they believe that their style has now evolved to the point of perfection.

It's doubly wrong, not just for the reasons you explain, but because it's exactly precisely not what I suggested. I'm happy to have a discussion with you as long as you read or listen to what I actually say and respond to that. I don't care if you rail against what other people say or write, as long as you're very clear where it's so different from what I say or write.

Now which of them, those king pins in their domains with their overruling authority, would relish writing code under their nearest co-advocates standard profile? Much less that of their most distant co-advocate's?

I wouldn't exactly relish it, but as long as we agreed on a standard profile for the team and reviewed it every now and then to match the current context and needs of the project, I'll do it. I'll even use the GNU coding standards if absolutely necessary.

p5p has coding standards. Parrot has coding standards. The Linux kernel has coding standards. OpenBSD has coding standards. The only major F/OSS project I can think of that doesn't really have coding standards is PHP. Can you seriously tell me with a straight face that PHP's complete and utter lack of consistency frees programmers to their maximal creativity and the result is, on the whole, a wild success for productivity and happiness? If not, can you remember more than three string substitution functions and the order of their arguments without looking them up?

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.