in reply to Re^5: Perl 11
in thread Perl 11

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.

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.


That's nonsense. Easily refuted.

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

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.

Replies are listed 'Best First'.
Re^7: Perl 11
by chromatic (Archbishop) on Oct 25, 2018 at 15:17 UTC
    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.

    Wrong.

    if their critique is completely untrue

    That's not what I wrote.