News for hackers. Stuff that matters.
Re:Perl 6 Optimism by rurban on Tuesday January 23, 2018 @09:15AM (#16213658)
Because parrot development was mismanaged and ran into ground. Similar to perl5 management in the last 15 years.
Re:Perl 6 Optimism by vgy7ujm on Wednesday January 24, 2018 @04:19AM (#16221417)
Is there any hope of seeing your cperl efforts in mainstream perl? Would you be able to disregard recent history with p5p if you were welcomed back?
Re:Perl 6 Optimism by ribasushi on Thursday January 25, 2018 @04:40AM (#16229806)
> be able to disregard recent history with p5p if you were welcomed back

It is essentially impossible to do so, as the problems are systemic and run extraordinarily deep.

Would you honestly consider any possibility of working on a "level" with people like this: https://www.nntp.perl.org/group/perl.perl5.porters/2018/01/m...

So I can't fault rurban for walking away. The project still has merit. Its current leadership - none.

Re:Perl 6 Optimism by rurban on Friday January 26, 2018 @01:59AM (#16237485)
I never walked away. I was banned with trumped-up charges.

Their former pastime was that my criticism had no technical merits, they now changed course and claim that my criticism is uncivilized. Well, this is a good strategy to hold the community together. Create a common enemy. Get him fired. Collect the angry mob and give them powers.

Re:Perl 6 Optimism by lizmat on Thursday January 25, 2018 @08:31AM (#16230612)
Re:Perl 6 Optimism by apag on Friday January 26, 2018 @07:51AM (#16238733)
More of a self-flagellation than an apology, frankly… it was actively uncomfortable to read, unlike even his initial angry mail. I have yet to respond to him because I didn’t know what to say after that.
Re:Perl 6 Optimism by rurban on Thursday January 25, 2018 @01:32AM (#16229208)
You have to ask them. They are the ones refusing any changes and cooperation, and are still actively destructive. In parrot the destructive people eventually burned out, and I could fix much stuff, but the big changes from around 2.7, the calling convention and the jit and runloop removal was eventually too much.