blogs.perl.org

Welcome to Perl 5 Porters Weekly, a summary of the email traffic of the perl5-porters email list.

Topics this week include:

• perl 5.18.1-RC3 is now available
• perldoc perlre does not appear to mention /r
• Perl 5.18 and Regexp::Grammars
• "\c\" is a syntax error
• Apologies and good news
• postfix dereference syntax
• Cuckoo packages aren't listed in Module::Corelist

I’m giving a talk at MadMongers on Tuesday night about how to write command line tools in Perl. It’s a fairly unsexy topic, but I’ll be covering enough techniques to make it interesting at the very least. Sign up to join us on Tuesday night at 7pm.

[From my blog.]

I love open source programming. I’m continually humbled to see even the small impacts that my contributions to the Perl community have made for fellow programmers around the world. Mostly my use of Perl has been to write a complex simulation and the tools that it uses to simulate the dynamics of electron bunches in an Ultrafast Electron Microscope column, which is the subject of my recent Ph.D. thesis. So while I have enjoyed sharing my work both here and at the 2012 YAPC::NA I never would have expected that my name would mean too much in the greater Perl world.

By Jonathan Schiefer

Last Sunday I went to Code Crew's Collaborative Coding meetup.

The event takes place every Sunday at Alley NYC. The midtown venue is a shared office space open between 12-4pm with room for 100+ hackers, power, wifi and kitchen facilities. A youngish crowd and a relaxed, friendly vibe, there are no presentations or planned activities - just turn up and hack solo or chat with people and code together. Most people I met were budding Ruby programmers from a local college. I really enjoyed it and will be heading back there frequently (including tomorrow). If you're heading down to Alley NYC drop me an email if you'd like to chat / hack Perl.

N.B. Hacker Hours are another meetup group that uses the Alley NYC space on Sunday at the same time. I didn't notice any distinction between the two groups.

I release TaskDeal(alpha version). Setup or deploy multiple environments from web browser.

TaskDeal

This is ruby chef alternate. Chef server and client is very difficult to install. Taskdeal is simple and easy.

You can send command from server to each clients.

This is example

Example(User: admin, Password: test)

You can send only echo command in this example for security.

I want to create Web applications more, because ruby web development is active, but Perl is not. I want many people to use Perl. so Web applications which is created by Perl is needed.

I had an idea for the Benchmarking chapter of Mastering Perl but I don't have time to implement it. But, with many of my ideas, someone probably already has.

The DBI::Profile module hooks into DBI calls to monitor database queries. The autodie replaces some built-ins so they error-out differently.

Could we do the same thing with the low level networking calls to measure octets read and sent? Of course, there would be a performance hit (as with the those two modules), but that's what we expect when we benchmark. Maybe it would work like Devel::Cover where it writes intermediate data files that another program analyzes to create the report.

I've been looking around for extra-script solutions to this, and they tend to be uniformly linux-specific and wrong. I also want something that handles the entire process group, so child processes count.

As far as I can see, the various network tools aren't process aware; they can see ports and IPs, but per process stuff. A process can have a local port to itself, but that doesn't mean it keeps it, letting another process use it for a bit.

I like CPANMeta fav++ this is nice than cpanratings.perl.org.

my opinion the "like" rating is better and well working than "5 stars" rating because 5 stars system often is used to report bug (sad.. but true).

so today I wrote small cpanmeta-fav.pl script inspired by Dagolden's this entry.

I just fav++ed too many modules help me to get things done.

perl and cpan eco system help me a lot. I must say thank you <3

let's fav modules helps you.

fav++ is a part of perl-cpan eco system!

Recently I released version 1.00 of WWW::betfair. It provides an OO Perl Programming interface to the betfair API.

betfair is a sports betting services provider best known for hosting the largest sports betting exchange in the world. The sports betting exchange works like a marketplace: betfair provides an anonymous platform for individuals to offer and take bets on sports events at a certain price and size; it is the ebay of betting. Unfortunately betfair is not available in all countries including the US. I hope that will change in the future.

Check out the module's documentation for more information about betfair and the available API methods

You don't see news like this about camels:

http://www.timescolonist.com/four-foot-ball-python-on-the-loose-in-north-vancouver-b-c-1.572484

I was really looking forward to YAPC::Europe next week in Kiev. The talks looked great and I was looking forward to seeing the Perl community. However, for work reasons I won't make it. This sucks.

What conferences should I go to instead?

With a little Win32::FileOp magic, it is easy to whip up a simple (minded?) Windows sudo(1) substitute for Cygwin:

#!/usr/bin/env perl

# ------ pragmas
use strict;
use warnings;
use Win32::FileOp;

Win32::FileOp::ShellExecute( runas => "cmd.exe", "/k " . join(' ', @ARGV) );

Apart from how you start it, a similar approach should work for Strawberry Perl once Win32::FileOp is installed.

Many people talk about TIOBE and how it's bad, or irrelevant, or broken, or many other vague descriptors of why it should be ignored.

All people talking about TIOBE miss one crucial point: It is software, it has an algorithm, and it is not "bad", it is buggy. That means it can be fixed.

So either fix it, or stop talking about it.

Here's why you can fix it

The TIOBE algorithm is to search for "[language] programming" on a number of search engines, then apply a weight to the resulting count, based on the search engine, and sum the results up to get a score.

Welcome to Perl 5 Porters Weekly, a summary of the email traffic of the perl5-porters email list.

Topics this week include:

• perl 5.18.1-RC2 is now available
• Perl 5.18 and Regexp::Grammars
• Empty regular expression does not match in some cases
• Using braces on 'if'
• refactoring of regex execution / calling

The weekly Perl Maven Show continues. This time an interview with Dave Miller, the leader of the Bugzilla project.

Avialable as a YouTube video or as an mp3 file.

Actually, there is even an RSS feed suitable for podcatchers. In case you'd like to listen to the earlier episodes while driving to work, check it out on the Perl Maven TV page.

Today TIOBE roll out his Programming Community Index for August 2013. Since it added many new searching engines perl slide rapidly down from 9 to 11 compared to last year.

I’m not surprised seeing this happened. it’s 2013, not 2003. except regex, I can’t see perl has any unique feature can dominate any common programming field. (yes, we have CPAN, but you can’t ask a newbie can adeptly choose parts in it to assemble in a canon. ;) ) With more knowing perl, I can more an more understand perl’s shortcomings.

It has been said that we need more Perl startups. I agree and have written CloseBargains.com - what better way to get a heapin helpin of local coupons than Perl, Mojolicious, Linux, and some 8coupons API goodness served up by hypnotoad. The frontend is done in jQuery Mobile; another buzzword that needs adding is that Backbone.js needs to be integrated for coolness factor.

While there are many who really appreciate the work of CPAN Testers, and value the feedback it gives, but it would seem there are still several people who are less than complimentary. One recently posted about what they see as wrong with the project, while continually making incorrect and misguided references. What follows is my attempt to explain and clarify many often mistaken facts about CPAN Testers.

(this is the email sent to the Dancer users mailing list, updating on recent releases)

Hey everyone,

I would like to get back into the habit of letting everyone know what's going on with Dancer. This means keeping you up to date on releases and our plans for the future.

Two ways of using a module or perl API function:

First way:

1. Read documentation. Check changelog, check open bugs. Use only "good" modules.
3. Decide which API of module/perl function to use and how.
3. Write code, write tests. Write assertions in production code. Write proper error handling.
4. Test on several perl versions and several module versions.
5. If tests fail somewhere, investigate, change minimum version requirements or workaround problem.
6. Write down strict minimum dependencies in makefile etc.

Second way:

1. Briefly read documentation.
2. Write code
3. Test manually.
4. pin module version
5. always use one version of perl, use perlbrew, never upgrade.

So I think Second Way just introduces a technical debt. You save time during development, but the end
you have no idea how your code works and where.

I see lot's of advices to use perlbrew instead of system perl, because system perl can be broken (it can, indeed), articles about Gemfile-lock-like systems.