in reply to Re^4: Should I come back to Perl?
in thread Should I come back to Perl?

Perl6 has the potential to be amazing and could include cross-compilation and such. It's not baked yet. Pretend it doesn't exist. Serverside JS is a bigger threat to Perl than Perl6, Python, and Ruby combined; it's the only full-stack high-level language and its tools are constantly improving.

Perl5 has had various speed and minor feature enhancements in 10 years but the ecosphere/CPAN (especially web stuff) has changed dramatically in the last 10 years.

Replies are listed 'Best First'.
Re^6: Should I come back to Perl?
by Anonymous Monk on Sep 14, 2015 at 15:34 UTC
    but the [Perl 5] ecosphere/CPAN (especially web stuff) has changed dramatically in the last 10 years.

    Could you please elaborate about what's changed?

[reply]

      Short version: there was no Moose, no Moo, Catalyst was still new and relatively unknown, no PSGI, no Dancer, DBIx::Class was just forking from Class::DBI, no Mojolicious, the template space was completely stalled, the file handling space was old school File::Find, tools like Proc::Daemon were fairly sucky and unlikely to work on your platform (it’s an *excellent* tool today), CGI.pm had been the defacto standard for 15 years (counting cgi-lib). Circa that time, the core Perl team was in disarray and regular releases were a fantasy. Best practices was a fairly foreign cultural concept still—it’s often in stark contrast to TIMTOWTDI—and just gaining traction. There is hardly any generic code from 2005—not talking custom algorithms, one-offs, etc—that couldn’t be better written with the CPAN and generally accepted practices of today. Perl had one foot solidly in the grave around 2003. Soon thereafter it started to experience a renaissance that is still in progress.

[reply]

        Thank you! Informative summary.

        It had also occurred to me that there's metacpan now. And cpanm.

[reply]

In Section Meditations