Why charcterize criticism as an "attack"? Naming and shaming subjects of criticism is a venerable intellectual tradition. An attack implies something quite violent, or unreasonable, but these are merely critiques. He's like the Yelp of p5p.

---

the toolchain is typically the gathering place for all the important people too incompetent to do core

That's an attack, backed up by... what exactly?

That's an attack? It sounds like truth to me. When I first read that statement it was like looking in a mirror, because I would definitely be gathering on the toolchain with my fellow incompetents wrt the core.

---

p5p refuses to take bug and security reports

That's nonsense. Easily refuted.

But that's not the only fork of Perl done for the same reasons:

"Here it finally is, stableperl, an attempt to restore perl stability and compatibility to the level mentioned in the official perl policy."

"It is also an attempt to fix some of the more obvious bugs that affect many programs and which the perl 5 porters refuse to fix, foremost hash performance and data corruption during global destruction."

"Lastly, and most theoretically, it is a safeguard against perl 5 porters breaking perl 5 to the point where it is no longer usable - when or if that happens, stableperl can be use to achieve independence."

blog.schmorp.de/2015-06-06-a-stable-perl.html

---

I think it's more likely that volunteers don't want to take abuse from someone who refuses to communicate with anything other than abuse. There are only so many patches I'm likely to review if every comment is answered with "you're too stupid and incompetent to ask questions, just merge the patch or you're deliberately destroying something".

If that was indeed the case then we're on the same page. I just find it odd that "the bad guys" who left p5p to fork Perl are fixing bugs and innovating far beyond what p5p offers, if their critique is completely untrue. I curse p5p every time I have to fix something they broke, and Larry's own son had to roll his own too: github.com/quietfanatic/notebook/blob/master/lib/cgi.pm

Thank you for taking the time to fill in some of the blanks.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.