Just a reminder that I am running a 2-days long course before YAPC::EU in Granada, Spain.
In the course I am going to teach web application development using Perl Dancer and MongoDB in the back-end, and AngularJS in the front-end.
Actually, we are going to see a version of the front-end code using plain HTML with JQuery and Handlebars, and then another version using AngularJS.
There are still places left in the course.
The compiler now has a small test suite. The main additions in the last 10 days were implementing global variables, better support for references, data structures, string interpolation, and a few new subroutines in the CORE namespace and operators.
A member of The Lacuna Expanse community has built a new client for Android devices. Still in beta, but cool.
[From my blog.]
Please join us tomorrow night, (21st July) at 6pm for our monthly meeting.
Full details including location etc in this post
Fliers can be downloaded here and why not like us on Facebook
Alex aka ASB gave me this proposal:
We (the Perl community) currently do not have a CPAN module that handles OData (cf. odata.org). There seems tob e an attempt to do it here: OData::Client But it's not finished yet, and i fit doesn't get a care taker, it will never be done. Also, there is client and server parts. Let's get both :)
Side node: Eventually, I'm too dumb to see that we don't need one because Perl can do it out oft he box. But if this ist he case, eventuelly, it would be a good idea to put up a grant to create a document describing how to use OData with Perl (like this one)
The Call for Papers for the Perl Dancer Conference 2015 in Vienna is now open!
We are accepting presentations in a wide range of topics, for example Dancer, Modern Perl, DBIx::Class, Perl "products" and security. Of course, we are open for any idea and submission.
The submission deadline is August 31th, midnight CET. Talks are reviewed and possibly accepted as we receive them.
Please use the online form for submitting your talk.
Questions? Feel free to ask! Either put a comment here or send an email to
It is part of our solar system now.
Now that’s legacy.
Maybe the fault is, indeed, not in our stars.
Ever given any thought as to what the expense of catching exceptions with Try::Tiny or even eval might be?
Recently a colleague was having some issues with a legacy codebase that was having requests exceed their nginx proxy timeouts. We discussed increasing those timeouts, but considered that a last resort.
One block of code being executed was along the lines of
eval { do_this() };
if (! $@) {
plan_a()
} else {
plan_b()
}
This week we rolled out the latest version of Alien::Base which includes a new feature and a bug fix. The most important change in this version are the two new avenues of communication that we have adopted, so I will discuss that first.
The first is that we have established the #native channel on irc.perl.org to discuss interactions with native interfaces. This includes Alien in general, Alien::Base specifically, and we also intend it to be a place to discuss FFI (Foreign Function Interface or NativeCall), as there is a degree of overlap for the people involved. You can now click on a big red button from the metacpan page for the project that will log you into IRC and allow you to start asking questions (or complain at us if that is what needs doing).
Every distribution should have a LICENSE file, that corresponds to the licensing information contained in your Makefile.PL.
You can create this file from the command line by installing App::Software::License - e.g. cpanm App::Software::License. Then, just invoke the software-license command.
So we have a new fresh face to our site.
Also there is still time to get a cheap plane ticket to come :).
The system that we are using to make the payment only works on Brazil but you can just drop an email to the organization and we will arrange everything to you.
I have to share with you that just changing the layout of the website the visits grow three times. Kind of obvious but the ugly site works ok with us from the community but not for "outsiders". Even to reach perl programmers that usually does not participate of the groups the "beautiful site" works way better.
When you work on larger projects, you'll often find that database changes are hard. Multiple developers, working on the same project, changing the same tables, can be difficult. Database migration tools often (but not always), come with one or more standard flaws:
DBIx::Class (sucks for the Python devs)There are plenty of other ways database migration tools fail, but the best standard tool I've worked with so far is sqitch. Its documentation needs some work, including more explanations of how to deal with common failure modes, but it avoids the above problems and provides you with a rich set of tools to make database migrations easier for large teams.
However, its common failure modes include:
Somebody asked me:
Is the Foundation mainly interested in grants to help fund work on Perl's own infrastructure -- the language itself, key modules, and other community projects -- or would it also be open to considering funding open-source applications created with Perl, but which don't primarily exist to support Perl itself? (And which, perhaps, might help further Perl's reputation, and provide the world with more high-quality example code?)
Our grants program does not specify such scope. So our official answer is: "just send a proposal for review". I also went through the historical grants, both approved and rejected, and found no grant proposals in this area.
Anyway, even without specific grant proposals, I thought it would be interesting to ask this question to the public. Should we fund application development Perl?
Last week I formulated an interesting problem in text processing while working on one of my hobbies. Since I was only able to devote an hour or two here and there, it took me a few days to get the solution up and running, which indicated to me that it wasn’t as simple as I’d thought it would be at first. And since “not simple” often means “interesting,” I thought I’d share it here with you. (Note that I don’t claim this is the best solution, or the most efficient, or the most elegant. I’m perfectly happy to receive suggestions for improvement if you’re so inclined.)
My June assignment for the CPAN Pull Request Challenge was File::LibMagic. The module had 50 FAIL reports at CPAN Testers, so I decided to start from them.
The CPAN Pull Request Challenge has now been running for half a year. Hundreds of people have done pull requests on CPAN distributions. Many have fallen by the wayside, as life and other distractions caught up with them, but more than 50 are still in the game. If you haven't tried it yet, it's not too late — you can sign up any time before 31st December.
Merijn Brand gave me this proposal. As it’s too long for our grant ideas list, I am posting here.
I've been adding support for Java in Perlito5 in the last few days.
This is what it does so far:
As devops I update a dozens of web application weekly, sometimes I just have no time sitting and wait while dev guys or QA team ensure that deploy is fine and nothing breaks on the road. So I need a tool to run smoke tests against web applications. Not tool only, but the way to create such a tests from the scratch in way easy and fast enough. So this how I came up with the idea of swat.
Keywords - perl, curl, Test::More, TAP, prove, bash
---
https://github.com/melezhik/swat
blogs.perl.org is a common blogging platform for the Perl community. Written in Perl with a graphic design donated by Six Apart, Ltd.
