($response->{reason} or '')) unless$response->{success};
my$ip= $response->{content};
chomp$ip;
$ip;
}
1;
__END__
It's a one file module, which simply contacts http://curlmyip.com, retrieves the content with HTTP GET request, and finally chomps the result; because there exists an extra new line character which is useless.
A couple of days ago I got a tip that I was very close to being the first CPAN author to upload 1000 releases in a year (989). Today I topped it off:
Thus ends my CPAN numbers ambitions. From now on I will concentrate on -Oquality-Ofun and -Oacmeism. Actually the numbers stuff ended in early September.
The -Oquantity and -Ofrequency flags were fun for a while, and it resulted in my getting a large portion of my modules into an up to date state; but numbers for numbers sake has a limited appeal.
Note: It was ironic that one of my final releases was from a pull request by SHARYANTO++ who leads almost all the CPAN statistics. :-)
Elasticsearch has a builtin scoring algorithm which works quite well in practice, but sometimes you want to roll your own scoring algorithm. Let's examine how to create a custom scoring algorithm using the function score query.
Let's assume we want to search and score Perl job offers based on a set of weighted keywords. To get the score of each offer, we'll multiply the weights of matching keywords where positive keywords have weights greater than one, and negative keywords are weighted less than one. Thus, the positive and negative keyword matches add and take away from the final product (score) respectively.
Define the Qualitative Importance and Their Weights
Qualitative Tags
Instead of assigning weights directly to keywords, let's use qualitative tags of desirability (importance) for each keyword (trait). Borrowing from okcupid's five degree scale of importance:
mandatory
very
somewhat
little
irrelevant
This takes care of the non-negative traits, now let's add qualifiers for negative traits using a similar pattern:
I deal with a lot of modules that promise backwards compatibility with older
versions of perl, usually back to perl 5.8.1. Since I don't regularly use perl
versions that old when developing, accidentally introducing incompatibilities is
always a risk. Having a continuous integration system check this for me makes
it much easier to catch mistakes like this before they get released into the
wild.
Travis CI is a very useful continuous integration
service that is free for any public repositories on
GitHub. There are issues with using Travis CI for the
kind of testing I need though. First, it only provides the last revision of
each perl series. Especially in the perl 5.8 and 5.10 series, there are
substantial enough differences between them that testing only the latest isn't
adequate. Additionally, some of the testing needs to be done on perls built
with threading, which isn't included on most of the versions available on
Travis. It also is sometimes useful to test without any additional modules
pre-installed like Travis does.
Some idiot has just uploaded a purely spam distribution: THEMA-MEDIA. He clearly knows it's idiotic, because his README.md begins with "CPAN-foolishness".
The documentation requires a bit of work, but from my perspective the implementation is effectively complete. If you're using it, then I'd appreciate any feedback you have before it's "stable" and thus too late to change.
Friends,
I have found certain outward challenges in perl and have always found someways to overcome them. Some of the common challenges i found specific in India are:
India being such a large country have a number of software development centers across it like: Noida, Gurgaon, Bangalore, Hyderabad, Pune etc. Though there are excellent developers in perl but they are less in number and find them sparsely located across these development centers , ie. few in each centers which makes connecting with each others rather difficult. Though there are some perl monger and other groups here but still as the developers are geographically sparsed in India, they dont connect well, eg. a developer in Delhi will not want to subscribe to Bangalore group because he may not find any merit at it. Same is with the recruiters .
My idea is to create a all india perl group, and also list profiles of most of the people here. There will be a weekly or monthly mailer from the group with a list of opportunities , I am willing to use the domain perl.org.in for this and use catalyst for the same.
Also we will plan remote sessions / google hangouts.
Any person here want to comment on this, and / or will want to contribute towards the design / anything just comment here or at https://twitter.com/perl_org_in ?
I tried to get co-maintainer bit for Text::MediawikiFormat, but his e-mail does not get delivered. do you know Derek? Could you help me get in touch with him to become a co-maintainer?
I know what you're thinking. You're thinking: "What this world has too few of, is recruiters. The world definitely needs more recruiters". And given that shocking lack of people trying to get you a job, I've launched Perl Careers.
My eventual goal is to try and do something like O'Reilly did back in the day - divert a significant portion of profits back in to the community via paying for high-quality Perl content/articles, sponsorship of conferences, and sponsorship in to TPF and similar organisations. This is going to take me a while to achieve; I'm planning to sponsor November's London Perl Workshop, and I'm flying to London for it, and I hope to start paying for high-quality Perl-related content at the beginning of next year. ORA used to pay $200-$400 for articles on Perl.com, and I think that's where I'll be aiming.
However, in the interim, I'm hiring for some great roles. I'm only willing to take on roles for companies I'd want to work at, so please get in contact: pete@perl.careers.
I gave a talk at NY Perlmongers this past Tuesday. We streamed it -- though didn't really publicize that ahead of time due to me working on my slides up until the last second -- and Devops in the cloud with perl is up on YouTube. The slides are here. I used the excellent reveal.js.
This is my second time giving a talk at perlmongers, and SocialFlow's fifth time hosting. Every time I've attended perlmongers it's been fun, interesting, and worthwhile, so if you're on the fence about going to your local meetup you should give it a shot. And it you're on the fence about streaming your local meetup you should give that a shot as well; it's really not very hard.
The Audio compression came out really bad this time, probably because our upstream speeds were severely limited by being on a cable modem, but I still stand by my HOWTO live stream a talk in pretty much the laziest way possible.
Welcome to Planet Moose, a brief write up on what's been happening in the world of Moose in the past month, for the benefit of those of you who don't have their eyes permanently glued to the #moose IRC channel, or the MetaCPAN recent uploads page.
If you'd like to contribute some news for next month's issue, you can do so on the wiki.
Moose
Moose 2.1212 fixes some warnings under the Perl 5.21 development branch. (See also perl RT#121638.) Moose 2.1213 fixes a memory leak throwing exceptions. If you're already using Moose 2.11xx or 2.12xx, then it's probably worth upgrading to Moose 2.1213. If you're on an older version of Moose, then also consider upgrading but first test that your stuff works with a newer Moose.
Note: I am not a lawyer and the following should not be considered legal advice. Double-check everything and hire a lawyer.
As I continue to work on Veure, I have the added fun of less time spent working on it while I try to understand the legal problems. If you're going to create and publish your own game, you'll invariably hit legal issues. What's worse, you might discuss them publicly and some bright spark will vaguely remember an online article, dumbed down for mass consumption, regarding a complicated libel lawsuit for the print industry and swear up and down that it applies to you. They won't supply a link.
In fact, software games seem to have some peculiar legal issues all their own, compounded by the fact that they're often indie games created by hyper-intelligent, well-read individuals who either don't think of legal issues or assume they already understand them. On the off chance that they're right about a given issue, there's also one tiny detail they often overlook.
After almost a week of adding more and more modules I've got to the 9th revision of
DWIM Perl for Linux
.
It explicitly includes more than 400 CPAN modules, but with their dependencies it is probably a lot more. The idea behind this distribution is to make it very fast and easy to get started with Perl. Without learning how to brew perl and how to install CPAN modules. Without fighting external dependencies or some failure in the latest release of a CPAN module.
I need your help to test-drive the distribution and to fill the holes. The modules that might be really needed but have not yet been included.
It would be of great help if you downloaded the latest distribution. Configured it as described on the website and let me know which additional modules your application might need or if something is broken.