If you have a Perl-related news item you'd like to share, you may post it in the Perl Newssection.
Please try to avoid duplicating news; but pointers (with summaries) to important stories on other sites are acceptable here.
The stock system perl on RHEL7/CentOS7 has been 5.16.3 since these OS versions were launched back in 2014. Now a much newer perl (5.26) is available to install as a package via SCL. See today's announcement for more details.
We'll start with a hands-on tutorial covering the basics including the new grammar matching system and some of the newer object-oriented features, and work our way up to creating our own Perl 6 modules. I've run similar hands-on workshops at the last two European TPCs, a 3-hour version at OSCON 2 years running, and DevDays in Vilnius.
Another interesting navel-gazing (from the community perspective) bit of data built on a thousand respondents to a survey. I will assume that citing and referencing are sort of built in once you get to the page, so won't waste the bytes here.
Those of you who stayed to the end of last year's London Perl Workshop may remember Davorg's lightning talk, available at YouTube. I had written 20 pages of documentation for Martin Berends to deliver as a workshop. Dave & I agreed that this would be an appropriate subject to expand and publish. It's over 3 times the length of the handout we gave to people at the LPW and, Dave says, over twice the length of his Perl Taster. I'm also entertaining fantasies of it leading a few people to PerlMonks.
Hi all, the latest version (0.30) of Crypt::OpenSSL::RSA was released this week. Notable among other improvements is the addition of support for OpenSSL 1.1.0.
This is great news because many platforms are installing OpenSSL v1.1.0 by default (e.g. the aptitude package manager I use on Ubuntu), which leads to the familiar XS header file incompatibilities that prevent XS-based modules from installing. These include Crypt::OpenSSL::RSA, which is required by Crypt::LE, the wrapper around the free certificate issuer Let's Encrypt's API, which was what I was trying to set up. Since LE certificates expire in 90 days, automatic renewal is important, and I was really wanting to manage that with Perl. Thanks to Todd Rinaldo that's possible again.
The way forward always starts with a minimal test.
"But what about Perl? Till 2005 it was the most dominating scripting language in the world. In 2008 we said in an interview with Dr. Dobb's Journal that Perl would go extinct based on the trend we saw in the TIOBE index at that time. After this a religious war started with Perl diehards who claimed that this won't happen and that the TIOBE index was being gamed. Stevan Little gave a ground-breaking talk in 2013 called "Perl is not dead, it is a dead end" indicating that once software engineers leave the Perl language they will never come back. Personally I think that the fork of Perl 6 (and its delays for decades) together with the unclear future of what was going to happen to the language was the main reason for engineers to look for alternatives such as Python and Ruby. And still today the Perl community hasn't defined a clear future, and as a consequence, it is slowly fading away."
-- TIOBE Index for April 2018 (retrieved on 2018-05-01)
There is a difference between knowing the path and walking the path. -- Morpheus
Up to 2016, this event was known as Perl QA Hackathon - PQAH.
The PTS is a free of charge coding workshop for people involved in Quality Assurance, testing, packaging, CPAN, and other projects related to quality assurance. The workshop is not necessarily exclusive to Perl projects, however, many of the attendees will be planning to work on projects that have a direct benefit to the Perl language.
This was the 11th event that focuses solely on the QA of perl testing and the toolchain (Configure, CPANTESTERS, Build systems, MetaCPAN, PAUSE, authorizations, modules, dependencies etc etc)
It started in Oslo back in 2008, when we needed to define things like parallel testing and focus slowly shifted since then towards the complete CPAN ecosystem, form starting a module to describing the requirements for authors maintaining modules "up-river". It was very productive again and I want to specifically thank all the sponsors for enabling this event (and op cause Salve, Philippe, Neil, Laurent, and Stig for organizing it)!