I am following lots of Perl related blogs, including most of those posted on blogs.perl.org, and share many of those posts on the various social channels of Perl Weekly.
Both Facebook and the Google Page fetch the images embedded in the post and offer them as thumbnails. If you look at the pages, I think the ones with images stand out more and are probably read by more people.
We will have a lot of books at the venue: Liz and Wendy will bring their incredible Perl library to the venue. If you want to know which Perl books exist, you should have a look at the library. As far as we know they have all Perl books ever written.
And there will be a booth where you can buy books. That booth is run by "Gutenberg-Buchhandlung".
I would like to announce two new CPAN distributions of mine: App-Notifier-Service and App-Notifier-Client. These are derived from a few simplistic scripts I've written in shell and Perl, to allow me to notify when a task has finished (e.g: make ; finish-client) or a certain time has elapsed (e.g: sleep 240 ; finish-client), and I decided to create something more serious as CPAN modules.
App-Notifier-Service implements an HTTP service (using Dancer), which listens for requests, and once one arrives, implements a callback, which notifies the user on the localhost that the event occured. App-Notifier-Client complements it by implementing a client that connects to the service and sends the event.
Currently documentation may be lacking, and there are almost no automated tests in the distributions, but it appears to work nicely. To get started, read the documentation and you may wish to peruse some of these files from my home directory. First of all, the .app_notifier.yml file:
I've published a review of CPAN modules for making HTTP requests. This covers 20 different modules from 19 distributions. I focussed on making GET and POST requests, whether the module supports https and redirects, and some other features.
As ever, I've no doubt missed a couple — let me know if you're aware of one not on the list. Also happy to hear if there are other aspects you think should be included in the comparison.
Did you know that 22/7 is actually a better approximation of pi than 3.14 is?
use DateTime;
use Math::Trig qw(pi);
use Test::More tests => 1;
my $today = DateTime::->now;
my $dm = sprintf '%d/%d' => ($today->day, $today->month);
cmp_ok(
abs( eval($dm) - pi ),
'<',
0.0015,
)
or diag("this test only passes on 22/7")
BinGOs will give a talk at YAPC::Europe 2012 described as
Perl. Windows. The two are often seen as incompatible.But they aren't.
I will distill and present 13 years or so of experience of
running Perl on the Windows operating system.Topics covered will include:
- Strawberry Perl
- ActivePerl
- Cygwin Perl
- Building Perl from source
- Active Directory manipulation with Perland much more.
I've previously written about Any::Moose and suggested using it instead of Mouse in order to provide interoperability in code. You get Mouse unless Moose is needed and in that case you get Moose.
However, there are a few problems, mainly having some incompatibilities between Moose and Mouse (which has been drastically reduced to have as little side-effects as possible) and the load order being tricky. My original post relates to that specifically.
We now have Moo! Moo is very small, yet maintains much compatibility by simply not getting into the whole "metaclass protocol" thing, and giving you Moose-like attributes. Moo can also inflate properly into Moose objects, giving you what Any::Moose does, but correctly.
mst has written a very compelling post explaining how Mouse was started and how Any::Moose was designed in contrast to Moo, and why you should use Moo instead of Mouse or Any::Moose.
Moo is so awesome, I've started moving many of my modules to Moo. Dancer 2 is also based on Moo.
So, "can we have a smaller faster implementation of the basic parts of Moose?" - Yes, we can, it's called Moo.
In tandem with the creation of perl4science.github.com, gizmo_mathboy created a new google group called The Quantified Onion. Both of these web properties are meant to give greater visibility to Perl's role in science, and to spread the word to newcomers that Perl is a great language for scientific computing and data analysis.
It doesn't take long to realize that The Quantified Onion could easily slip into becoming just another room in the Perl echo chamber, a forum-based extension to blogs.perl.org with a scientific bent. If our goal had been to create a space for Perl scientists to hang out, this might be acceptable. However, I am convinced that Perl needs to get itself out of the lonesome offices and into the halls of academia. We have to grab the interest of undergraduates and graduate students doing science. Heck, I'll even take a postdoc or professor if I can get their attention. How do we achieve this?
We put on workshops for scientists and engineers.
One of the purpose of blogging for me is to record ideas and thoughts. So, here's another series: features I'd like to see on various Perl-related websites (like search.cpan.org, MetaCPAN, cpanratings, blogs.perl.org, etc). There will be future posts.
Uwe Voelker will give a talk at YAPC::Europe 2012 described as
Segfaults are nasty, sometimes they are hard to detect or hard to narrow down.This beginner level talk (in regard to segfaults) will show two ways to narrow them down: Devel::Trace and core dumps plus gdb.
I rarely rant on this board, and I try not to rant whenever I can stop myself. With that in mind I am going to try to phrase this rant as a question and see if people agree with me or not. Note that for the remainder of this post I am going to be speaking in broad generalities and I know that there will be notable exceptions. Ok here goes.
This started while responding to a post from awncorp, but it really isn’t the same topic. I want to know, is the focus on “user-friendly” or “ease of use” or “one-click” hurting users in the end? Not even from a teaching standpoint, but actually in their day-to-day computing? My assertion is that some things in computing are inherently difficult, and that they should be, and people might to well to embrace that.
At $work, our flagship application was recently audited for potential security issues. One of the items which raised a red flag was the fact that we weren't dealing with the threat of CSRF (Cross Site Request Forgery). The solution which we decided to implement was to add a CSRF token to all POST requests. This token should only be known to the app and the end user. Passing it along with a POST request gives some measure of assurance that a POST by the user is intentional and so can help to reduce the risk of CSRF.
Reini Urban will give a talk at YAPC::Europe 2012 described as
address-sanitizer (aka ASan) is a memory error detector for C/C++, superior to valgrind. It comes with clang.It finds:
* Use after free
* Out-of-bounds accesses to
** heap
** stack
** globals
* Use after returnIt is very fast. The average slowdown of the instrumented program is ~2x, it's ~10-20x faster than valgrind. DEBUGGING builds should just use it.
The tool works on x86 Linux and Mac.
How it works, what errors it finds, some tools.
Today is a very sad day for perl: https://twitter.com/Reini_Urban/status/225999360058617856
I had to remove the perl frontend for mosh, being replaced by a C++ script. perl IO::Pty on cygwin and various platforms did not work good enough. mosh was one of the most prominent users of perl.
Accidently some tweet from today says: ": But for some things, #Perl just isn't the optimal choice. (yet) :-) -Larry Wall in 199702221943.LAA20388@wall.org #iFollowBack"
A note to folks reading reddit:
This is not a fork, it's a sanctioned pre-release of 1.3 with a bad version number. It was decided for the next major mosh release 1.3 to use the C++ wrapper by Peter. The new c++ wrapper is also used in the android mosh opkg version. mosh is awsome, 1.3 will be even more awsome.
PS: If you don't know that: I am the cygwin maintainer of perl, and toddr the IO::Pty maintainer sits next to me. It's not my personal decision to remove perl, but I just had to do that also for my port.
Naturally, you'll need to season this to taste, but here's how I've now integrated perlcritic and vim, making it easy to jump to specific errors.
I've previously written about using the Vi::QuickFix module. It takes advantage of vim's quickfix commands.
First, drop this into your .vimrc:
" quickfix for Perl error formats
set errorformat+=%m\ at\ %f\ line\ %l\.
set errorformat+=%m\ at\ %f\ line\ %l
I also have the following mapping:
noremap ,c :!time perlc --critic %<cr>
It's the perlc hack which makes all of this work.
Just noticed from my CPAN feed that Moo 1.000000 is released. Yay. Also wishing mst to reach 1.000000 in recovery soon.
(I remember about a year ago when only my dists were the ones mainly using Moo. It's nice to see the list has grown. Not far behind Mouse and Moose, really.
Matt S Trout will give a talk at YAPC::Europe 2012 described as
A tale of systems introspection, service inference and parallel computing - how we used the Tak systems automation framework to help track a customer's infrastructure.
On my laptop I use perlbrew to keep my system perl separate from my development perl. But I also develop various Perl projects with different dependencies, and would like to keep those dependencies separate if possible. Using a separate perlbrew perl for each project as well would be overkill in terms of diskspace, CPU energy and time so I thought local::lib might be useful.
If I install dependencies for a particular project using "cpanm -l extlib $MODULE" in the top level directory, the function below will automatically setup local::lib for that location when I change into that directory, and unset it when I change out. I use a test for the existence of a "extlib" directory and a Makefile.PL file because that is what I consistently have.
The talk & tutorial evaluations have now been sent out to all the speakers from YAPC::NA 2012 in Madison. If you were a speaker and haven't received your evaluation, please check your spam folder first. If you still can't find it, email me and I'll resend you a copy. However, please note that I will be offline for a week from this Friday, so you may have to wait until i return to get your feedback.
Many thanks to all the attendees who submitted 566 individual talk evaluations. Having read through them all in order to ensure no unpleasantness appeared, I was quite impressed with some of the great comments. And not one had to be doctored either.
I am now working on the main survey results and hope to have those online by the end of the week.
blogs.perl.org is a common blogging platform for the Perl community. Written in Perl with a graphic design donated by Six Apart, Ltd.
