Alien::Base is a system that simplifies writing Alien modules to provide external libraries via CPAN.
When I first wrote it, I knew that it was going to be a useful project, and I feel even more strongly about that now.
That said, I feel that I have taken Alien::Base as far as I can on my own.
Several others have offered good and useful suggestions and even patches which have unfortunately languished as I attempted to find time to consider their utility or when my knowledge of the situation was lacking.
I have therefore decided to expand the circle to include a few of these contributors.
I will remain on the team, where I will attempt to guide (not dictate) the project to continue along the path that I still envision for this work.
Perl5-Alien is a development organization devoted to the continued development of Alien::Base and the Perl 5 Alien ecosystem as a whole.
I hope that this will be a step in the right direction for the Alien ecosystem.
If you would like to submit your name for consideration to join the team, please contact me either on this post, via irc, or email.
Of course everyone is welcome to contribute via pull requests or by writing your own Alien module for your favorite external library.
I know it has been a while, but I’m finally getting around to posting my reflections on the Dallas-Ft. Worth Perl Mongers Winter Hackathon. Better late than never right? I will talk about my solution, but I also want to comment on the hackathon itself, which I thought was an excellent bit of fun.
This the the third part in an on-going series about using Mojolicious to write non-blockging applications (with an eye towards the web, obviously).
In part 1 I demonstrated the how it can improve the number of requests/clients served when the application uses high-latency backends (in that case a database).
In part 2 I showed how each request can be sped up when that request needs multiple resources from a high-latency service (e.g. external web services).
In each, I showed a blocking example, then a non-blocking example.
I then gave the usual warning that you had to use a Mojolicious server for the nonblocking version.
While its true that you need a Mojolicious server to get the benefits of the nonblocking architecture, in this post I will show how with a little care in construction, you can build your application so that it will run correctly on any supported server and the nonblocking benefits will be evident where possible.
In a recent post, our own Buddy Burden expounds on the relative merits of readability vs flexibility (in the guise of Python vs Perl respectively). While he does not completely concede the point that Python is more readable than Perl, I will go so far as to negate it. In fact, I would say that the prettiness of Python can even mask some real readability issues.
I have been a Perl programmer for several years, but early this summer took a job writing Python. I’m glad I’ve learned it, there are several things that I would love to see added to Perl, most notably a
set type and a proper
in operator (
~~ got close). That said I will absolutely not concede that Python is easier to read than Perl, as all too often is taken as the axiom that many believe it is.
And I have examples.
This post announces the release of Mojolicious::Command::nopaste, a clone of App::Nopaste using the Mojolicious toolkit.
I wrote it mostly as an example of using Mojolicious and its command system, but it has the side benefit of having a much lighter dependency chain than the venerable original (I already have the only required dependency on every box I use).
It also has a few bugfixes that the nopaste author either hasn’t tripped on, or had the time to fix (mostly in the Clipboard interaction on Linux) (sartak if you want to ping me I’d be happy to work with you on it). It has a slightly different list of services, including the very fun MathB.in but lacking Gist for now since the OAuth is something I don’t want to deal with yet. Any other services that people are interested in may be contributed via a PR or even a decent api spec.