We're happy to announce that our advance notice about our new ACT design for GPW 2014 now officially reached the production system. Have a look at the German Perl Workshop 2014 homepage and feel free to comment the new design below.
Ok, I took up JT's challenge to build something. Here is the MVP launch of classmith.com it only works on https right now so don't try 80. Mojolicious, DBIx Class (Candy) and a healthy dose of DateTime::Set and a couple of other DT modules with Bootstrap frontend. This app is meant to be a tool for the growing group of tech savvy, [home|un|hack] schooling crowd, with features for those that are location independent. I already have a roadmap of about 30 items to add and to start work on the mobile syncable version. All feedback is welcome. Thanks.
Welcome to Perl 5 Porters Weekly, a summary of the email traffic of the
perl5-porters email list. I'm at OSCON this week, so if you're in town,
please come to one (or both) of my talks. One is about replacements for
LWP::UserAgent and the other is about DTrace in Perl, Python and Erlang.
I really like the idea of a CPAN testing service where individuals volunteer their computers to tests CPAN packages and those results are accumulated and shared.
The accumulated results then are tallied with other result. People can use this information to help me decide whether to use a package or when a package fails if others have a similar problem.
Comparing the CPAN Testers to Travis (which I also use on the github repository), the CPAN Testers covers far more OS’s, OS distributions, and releases of Perl than I could ever hope try with Travis.
And that’s the good part.
The Not-so-Good Part
While there is lots of emphasis on rating a perl module, there is very little-to-no effort on detecting false blame, assessing the quality of the individual CPAN testers, the management of the Smokers, or of the quality of the Perl releases themselves.
Yet the information is already there to do this. It is just a matter cross-tabulating data, analyzing it, and presenting it.
This past May, The Perl Foundation awarded a grant to fund development of a couple features in Pinto. Pinto is a robust tool for curating a private repository of CPAN modules, so you can build your application with the right modules every time. This is my first progress report on that work.
This is my first post to the perl community also if i play with perl since a long time.
In my working environment i choose mojolicious as a framework for my web apps but sometimes happens that a bit of php is needed (not obviously by me).
In have more web-apps in an internal network that needed a virtual name dispatcher, i could use nginx or apache mod_proxy but was very odd to me that wasn't a perl software that do that job easily and less painful.
After a little search i found Mojolicious::Plugin::Proxy but didn't have support for cookie so i was really unhappy :(
So i developed a little reverse proxy using mojolicious (so can leverage the hypnotoad workers management out of the box).
Mojolicious is so fun with a couple of lines you just accomplish your job.
With 6 lines you have your request cloned and dispatched.
Now the software reads YAML files to define configured virtual host and its routes.
The project it's not intended as a Mojolicious::Plugin because i think that with a bit of community effort this software can become a light webapp deployer and manager (that i felt it's missing out there).
If you are interested, and you may find it useful like me, bugfixes and developers are welcome :)
The project is hosted on Github
In the first part of the "Perl Startups" intermittent series of blog posts, I interviewed JT Smith about the Lacuna Expanse. For the next post, I was very interested in Lokku/Nestoria. Many of you probably don't know much about them, but I learned about them when I was living in London and found them to be a great company and nice people. Recently I interviewed Alex Balhatchet (CPAN account, the CTO of Lokku/Nestoria and his company's love of Perl and the Perl community.
I'm using CPAN::SQLite. I don't like it and I'm trying to improve the locking issues with concurrent process all trying to read from cpandb.sql by writing a new CPAN::UnQLite.
But this is something else.
Today I want to smoke whole CPAN in one line to check the new experimental return-or check by Niels Thykier for "Possible precedence issue with control flow", for which we filed several bug reports in the last two days.
See https://paste.debian.net/16932/ and perl #59802. To repro add this patch from Niels to latest blead, if it's not already included.
These days, lots of software development tools are turning into hosted services. GitHub and VCS hosting are the most obvious example, but there are others too. Most recently, I came across http://codeclimate.com which provides static analysis services for Ruby code. I think there are some great opportunities for an enterprising Perl developer to cash in here. Read on to learn more...
I recently started porting Plack to the p5-mop and yesterday I completed the "straight" port of the code. This means I didn't try to refactor anything to take advantage of any p5-mop features, I just converted plain Perl classes to their p5-mop equivalent.
My main reasoning for doing this was that I really wanted to push this prototype in real world scenarios, not just contrived tests and simplistic examples. This is a mistake I believe we made with the first prototype. So that said, I am happy to report that all 1152 of the Plack tests are passing.
Just a quick update. We're not only enjoying the great summer, but also working on a more contemporary design for our website. The current looks were inherited from the late 90s. Granted, we're just the proverbial programmers without much design skill, but the web is full of inspiration.
So look forward to a better-looking and hopefully more user-friendly website in the coming weeks.
We all know that RHEL decoupled perl and real perl is shipped with "perl-core" package. However recently I found that even perl-core is not a real perl sometimes (at leas in CentOS 6 minimal netinstall), and this can cause weird bugs.
I reported this to RHEL, and seems that is going to be fixed!
I'm on a quest to fix up the Changes file for at least 10 distributions on CPAN. For every additional 'like' I get on my quest, I'll fix up another dist. This was inspired by a recent entry on the CPAN Testers blog, which mentioned Brian Cassidy's CPAN::Changes Kwalitee Service. The service shows how many dists have conforming Changes files, and results for recent uploads.
Initially launched as Play Perl, Questhub is now a general place where groups of people can share their tasks as quests, and vote on quests to encourage each other.
Play Perl is now the Perl realm on Questhub.
Contributing to Perl and the Perl community was never so easy.
Last week Questhub gained support for stencils: pre-scripted quests with clear instructions, and bonus points.
The perl realm now has an initial set of stencils, each of which defines a specific way you can contribute to Perl, CPAN or the Perl Foundation. Some of these only require a few minutes, some require a larger commitment of your time.
I hear that perl is dirty, not cool, very loose. Ruby is good, python is good.
But Perl is good language.
Perl have ability to write code clean and beatutiful.
For example, Mojolicious have clean code.
This is perl.
The big reason perl is said dirty is perl very old code which is more than ten years old.
In the old days, non-programer write perl code for CGI script to create Web site.
The old perl code is dirty, but latest perl code is not dirty.
Perl is fast, light, and stable, less-memory.
I think Perl need more understandable tutrial which have examples.
As with other years the selection process was relatively straightforward and this year we offerred places to four candidates, however due to unforseen circumstances only two of them have so far been able to confirm their attendance and book places.
We would like to thank our sponsors for their continued support of this initiative and to those who made donations at the London Perl Workshop and online through the donation system.
If you are attending this year's YAPC::EU::2013 in Kiev I thoroughly encourgae you to seek out the neophytes and welcome them to our community. As always we will be re-starting the initiative in the autumn in anticipation of the 2014 conference season.
Naturally that this snippet of code prints 1. I understand the explanation of "an array in scalar context blah blah blah". But it's so counter-intuitive because many functions are intended to mutate each element in a list. Presumably one should define separate functions depending on whether an array is expected, but that's so non-perlish. There's no elegant way to throw the wantarray operator in that example function. And even if there was, it's awkward to use the same idiom repeatedly.
I'd prefer simply to use a pragma such as the following:
The talk will last about 90 minutes, followed by a Q&A session. If you're within driving range of our venue in Orem, UT, or happen to be in Utah August 1st, -- quoting one of our members -- "Your nerd card will be revoked if you miss this."