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.