8 ms·
> The spectre of perl6 stopped bothering us about 2006 From a practical usage standpoint, sure. But wouldn't you agree that an effective major version freeze h
by bashcoder 13y ago
> The spectre of perl6 stopped bothering us about 2006
From a practical usage standpoint, sure. But wouldn't you agree that an effective major version freeze has had a chilling effect on the progression of the language?
I'd argue it's had a deleterious effect to varying degrees, even since 2006. It's not enough for a community to be not bothered. They need to be energized, and it's tough to make the argument that the perl6 snafu has been helpful to the perl movement.
> CPAN uploads have been up every year since.
CPAN traffic was down over 10% last year, according to Alexa. In fact, many perl popularity metrics were down at least 10% in 2013. [0]
My experience, admittedly anecdotal, is that CPAN packages in general are not maintained with the same vigor as in years past. But why would they be, if people are moving their focus to other languages?
Regarding Moo, thanks - I'll definitely have a look.
[0] http://szabgab.com/the-popularity-of-perl-in-2013.html http://szabgab.com/the-popularity-of-perl-in-2013.html
- mst 13y ago> They need to be energized 2006 is when the energy around perl5 / new wave of cpan development became palpable to me. Have a look at Task::Kensho - you'll find a fair chunk of the stuff mentioned in there originates from 2006-2009 or so (and has been actively developed since). > My experience, admittedly anecdotal, is that CPAN packages in general are not maintained with the same vigor as in years past. But why would they be, if people are moving their focus to other languages? That or the CPAN packages you've been using have been superceded but you've not found the replacement. We're fairly terrible as a community at communicating when that happens.