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.
"...Larry has announced that the Perl 6 Developers will attempt to make a development release of Version 1.0 of Perl 6.0 in time for his 61st Birthday this year and a Version 1.0 release by Christmas 2015."
You may register starting today. It would be preferable not to postpone registration to the very last minute as that would give us extra trouble organising catering etc.
You may also submit talks, deadline is 15 March 2015. I am looking forward to many fascinating talks, as those a good workshop do make.
The team of organisers offer this (albeit incomplete) list of wanted topics. Do not hesitate to offer talks on other topics if you prefer.
Even non-perl topics may be worth while, (last year we had a Haskell talk). Sometimes we get our best inspirations when we learn something about seemingly unrelated things.
"If you join the CPAN pull request challenge, then at the start of each month in 2015 you'll be emailed a (somewhat) randomly selected CPAN distribution. You'll have one month to submit at least one pull request. You don't have to be an experienced Perl programmer, CPAN author, or githubber. The goal is to help others, possibly learn something, and hopefully have a bit of fun."
At the 31st Chaos Computer Club Congress, Netanel Rubin (a researcher within Checkpoint) gave a talk about Perl which boils down to misconceptions about lists in perl, which ends with this
Lists are hazardous, bizarre expressions
Perl is a hazardous, bizarre language
Now's the time to stop using Perl!
Stop the write-only code
Stop the miss-functional OOP
Stop the security breaches all over the place
At least know your language "features"
I am absolutely disappointed of the CCC for allowing such a shallow talk which culminates in bashing a language (perl in this case) for documented and expected behaviour of its syntax. The bugs encountered may be spectacular and lurking there for years, but they can easily be fixed from within, without altering the language in any way. How about ditching C and claiming "C programming is harmful" for the existence of the very common pitfall of something called "buffer overflow"?
And, more sadness, Fefe called it brilliant. A strong response from the perl community is due IMHO.
update: the "security breaches all over the place" are located in the small, but important, corner of web applications and the interaction between CGI and DBI. This is in no manner "all over the place". The author did in no way address "miss-functional OOP" nor "write-only code".
And of course you need to know the features of a language you use.
We're up to the point of generating an RPerl abstract syntax tree (AST) from valid RPerl input source code, next there are a few more grammar tests to implement, and then the AST-to-C++ code generator, then that's it!
Sorry it's taken so long, but as usual this software development project turned out to be much more complex than originally anticipated. :-)
Congratulations vroom for creating this fantastic site in the first place, and
to the many thousands of Perl Monks who have contributed useful, interesting,
and sometimes quirky, content over the past fifteen years, making this
site not only a great technical resource for Perl, but also a fun place
to hang out.
It took a bit longer, as Encode and Tk did not work well together just after 5.20.1 had been released. Now that all problems are fixed, I'm proud to be the one to present the depots for perl-5.20.1. The SHA-1 sums are:
I participate in lot on online programming quiz like codeforces, codechef, hackerrank etc. I had observed that very few people code using PERL. It is sometimes as low as 1 in 4000 participants. I have started a blog to encourage people code more in PERL
On the main site there is also a wiki that we will be using for general information such as ground transportation, local restaurants/pubs/businesses, things to do, etc. The wiki is still a work in progress.
If there are any questions, feel free to drop by #yapc or #yapcadmins at irc.perl.org.
While there is a rumor, possibly started by netcraft, that perl is dying, this is definitely not the case, although perl programmers are often busy getting stuff done and not doing advocacy. For those who have not used perl in a while, or have only seen perl that was written just to get the job done, there are now many conventions for writing Modern Perl now that lead to readable, maintainable, code while still allowing for the expressivity and power that perl allows.