And I'm fine with someone saying, I am going to write an alternative. But there's little I am going to... in the post I was replying to, and there's no and this is what I've already done at all.

Those are great points and shouldn't be missed in what is already tending towards a flamewar.

Even short of having existing code, there's nothing wrong with saying "here is what I plan to do and I want feedback on the idea before I go do it".

Frankly, there's nothing wrong either with someone speculating on how things could be better, or trying to galvanize "the community" to do better. (C.f. Alias' rant about crappy design of perl web sites.)

But between the two sentiments, I'm much more interested in the first than the second. Better ideas are rarely the constraint for improving the Perl ecosystem, but rather it's the time of volunteers to write working, professional, polished code.

So while "show me the code" can come across just as dismissive as "patches welcome", the underlying message is that doing the work ultimately does more to advance the Perl ecosystem than a wishlist does.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re^4: Upgrading CPAN - Yes We Can by xdg
in thread Upgrading CPAN - Yes We Can by jdrago_999

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.