Perl5 releases in the 200x years were rare because everybody was expecting Perl6 to arrive.
My memory is that the porter list was already bogged down to a near standstill and it had little to nothing to do with Perl 6 because there was already a complete schism of attitudes and a growing abandonment of Perl 5, not because of the promise of Perl 6 but the lack of agreement on features and backcompat and the open road of Ruby and Python and the corporate enforcement of Java. It was a small handful of devs who sparked the renaissance around 2005 and the following years and—not to take away from the amazing, crucial, gracious work and dedication of folks like dave_the_m—it was entirely framework based. Even a piece of crap like PHP will thrive with useful, easily deployed, applications/frameworks.
Yahoo and Amazon both decided to abandon Perl completely independently of Perl 6. I was at Amazon when it happened and it was a year, maybe 18 months, before Jon Orwant threw those mugs.
Perl 6, to me, is about 10th on the list of Perl 5 problems (with PHP, Ruby, Python, Java, and others taking all top slots) while still in the top set of things that helped it survive. Even today, infighting over Perl 6 is worse than Perl 6 ever was… ECMAScript is the most likely candidate to relegate Perl 5 to permanent maintenance mode.
In reply to Re^13: Ovid's take on the renaming of "Perl6" (updated)
by Your Mother
in thread Ovid's take on the renaming of "Perl6"
by 1nickt
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |