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.
Thanks to our generous sponsors we can provide free breakfast, lunch, live band
and social event for every attendee of the Perl::Dancer conference in Hancock, New York.
Attendees and speakers from USA, Canada and Europe are coming to have lots of fun at
the marvelous venue.
There are still tickets available both for the training and presentations days, please
go to registration to purchase your ticket.
Recently I tried the Atom editor which is very trendy now.
I was happy to find it uses Exuberant Ctags and the rules in my ~/.ctags file just worked.
Then I just made a pull request to https://github.com/atom/symbols-view. The pull request got finally accepted and the extended support for Perl is available since version 0.65.0.
Exuberant Ctags can be used with Vim, jEdit, Sublime Text, Ultra Edit... any IDE/Text Editor that uses it natively or has a plugin for it. I use it to quickly jump around in my Ado project.
Keymaps: ctrl/cmd+r to see current file symbols; shift+ctrl/cmd+r for project symbols.
When dealing with elasticearch, one has to consider how they want to manage the analysis of the content that is ingested. The use of templates is a way to ease this burden of managing analyzer settings. Let's learn by example...
Catalan Stemmer
Here's a template that defines an analyzer, cat_stems, which utilizes the built-in catalan stemmer. For example, both singular: porro and plural: porros will be reduced to porr when analyzed by the stemmer. Moreover, this template will be applied to any index created with a name that starts with cat.
Now I call DBD::SQLite 1.43_08 a release candidate of the next stable DBD::SQLite. Please test it with your modules/applications and let me know if you find anything. Due to some change(s) in the upstream SQLite library (since SQLite 3.8.5), this release candidate is known to break older versions of DBIx::Class (prior to 0.082800 released on 2014-09-25). If you use older versions of DBIx::Class, you might also want to upgrade it, or keep DBD::SQLite 1.42 (bundled with older SQLite 3.8.4.1 library) for now. Other major O/R mappers seem not affected by this upgrade. If there's no blocker nor request to wait, I'll release 1.44 in late October, hopefully on 26th.
Other notable changes since the last stable release follow:
This release candidate contains new modules to support custom virtual tables written in Perl (by DAMI).
If you set sqlite_unicode to true, SQL statements will be upgraded to avoid inconsistency between embedded params and bind params (RT #96877) (by DAMI)
See Changes file in the distribution for other fixes and improvements.
Just in case you're curious, I'm still hacking on Veure, though the last month has kept me busy on a bunch of other things (our daughter just started school, so that's a big one!)
I've been building so much of the infrastructure that you might be surprised to realize that I've only just gotten around to being able to equip weapons and armor:
The other developer has been working on the cockpit view. If you travel from system to system in your own ship, the experience should be different than if you take public shuttles. I haven't actually seen his work yet, so no screenshot on that one.
Update: OK, I have some of the initial screenshots for the cockpit work. They look great, but not sharing until some things are settled.
As you may be aware, I'm writing a book which will eventually become a free e-book. (Oh how I'm beginning to hate the e- prefix on everything vaguely related to computers. Or should I call them e-machines?) This is my initial report on how I'm getting along.
Firstly. @preaction CPANTS != CPAN Testers. They are two very different projects.
Secondly, this is a conversation that has cropped up before, and I'm still in two minds about it. Short answer: I tend to side with brian. The tester platform shouldn't be doing any testing with the trial/development releases of pre-requisities, unless the tester is going to manually filter the results and send to the pre-requisite author if appropriate. I do understand Ether's perspective too, and there is merit in having these reports, but they more often target the wrong author.