Thanks to some pointers by MidLifeXis and Ether it turns out I didn’t need to bump the requirements of Ouch to 5.12 to use overload and parent. Thanks! So this release just goes back to letting you use 5.8 (but you really should upgrade!)
Last night, I gave a presentation for the Madison Perl Mongers group on UAV::Pilot. The video is now up:
This is also the announcement for the WumpusUAV Indiegogo project, which aims to create a new, cheap, hackable UAV platform. More information is on WumpusUAV.com.
In the previous post, we talked about some of the optimizations
that perl performs when conducting string and array operations. This time, we'll be diving into
how perl implements hashes. But first, a brief clarification…
We have released a new version of Brainturk.com . We have changed the look of the application and now have 35 games and most of the games have different levels.
Let's post information about your production and your work to blog. It is important to inform your production and work even if it is not complete. Other people can know your idea, your technique, and your concern.
Even if it is good production, if no one know it, no one use. To spread good production from person to person, we need good communication. blog is good place to inform your production, your module, your work, your application.
Blog is public, rapid, understandable communication compare with face book, twitter, IRC, mailing list.
I think Perl culture is close to IRC and mailing list, compared with Ruby, Python, PHP. I think Perl need more web, more public information.
Continuing my series on underappreciated Perl modules, I introduce Tree::Trie. A Like Hashes, a Trie is a type of dictionary lookup. Unlike Hashes, Tries naturally support sorted return of keys and prefix matching, all while still being fast, even with a million entries.
Maxim Yemelyanov pointed me to this post comparing programming languages based on the number of new GitHub repositories in the first 8 months of 2012 and 2013.
(excluding forks!)
Interestingly the numbers dropped significantly for every language (except JavaScript).
Perl dropped a lot more (in percentage) than other languages (from 48,620 to 15,412).
Some Perl repositories might be miscategorized by GitHub which might add to the low number, but then either it got worse in the last year, or regardless of that Perl has dropped a lot.
Still, there is something strange.
According to the
stats on CPANTESTERS
there were 1,524 new distributins uploaded to CPAN in the first 8 months of 2013.
That's only 10% of the number of GitHub repositories written in Perl.
What are all the other Perl-based projects?
The buzz around XML has passed and we are left with a lot of Perl modules to process XML in different ways. I was surprised to still find a gap for another XML processing module.
Common schema-less approaches to XML processing in Perl seem to use XML-LibXML, to get a full XML DOM or a stream of parsing events, or XML::Simple (better used as XML::LibXML::Simple. XML::Simple transforms between XML and Perl data structures but it was designed for "data-oriented" XML where element order does not matter a lot. With XML::Struct I created something like XML::Simple for "document-oriented" XML.
I’m starting to get serious about real-time web apps. At first I was considering using some of the Perl stuff (Meteor, Twiggy, AnyEvent, etc) to roll my own, but then I started looking around, and found a bunch of other interesting stuff to investigate:
The thing that’s cool about these services is that I can still write my apps using non-async stuff that I love (like DBIx::Class) and still get most/all of the benefits of an async web service.
If you do any kind of programming that extends beyond one-liners, you need to version control your work...even if you are a lone wolf weekend warrior, like myself.
Why? At least three reasons:
The Pittsburgh Perl Workshop is rapidly approaching this October 4th, 5th, and 6th. We are now accepting talk proposals, registrations, and sponsorships. Please consider participating today:
The simple goal of Wx::Perl::Smart (WPS now for short) is to make WxPerl - GUI programing fast, fun and technically sober. By that I mean you still have full access under the hood (like Moose does) to all features of the old ways. Oh, and speaking of OO, I decided using no framework (yet), not even Moo. While sitting on top of Wx, you don't count bytes in memory, but there is no big syntactical gain now, since there are almost no attributes and the ones I have need a special treatment as described further along this article.
While it's still just started, goccy, a Japanese hacker who has been working on rathercoolmodules, has been working on PerlMotion, which allows you to write iOS apps in Perl.
I'm not an iOS guy so I haven't delved too deep into it, but other than the fact that it could use a bit more packaging love, I head that something is actually running on iOS... Although I'm not involved in project, I personally would love to see it get input from a lot more people, so I thought I'd let you guys know.
Welcome back for another exciting episode on the inner workings of
the perl interpreter! Last time we
covered some of the basic optimizations perl performs on SVs, as well as
the consequences of those optimizations. This time, we'll be going over
some of the optimizations specific to strings and arrays. I know I said
we'd be covering hashes too, but this article is already quite lengthy,
and I have enough material on hashes to merit its own article, so look for that
information in the upcoming third part of this series!
Tired of being a Perl script-kiddie? There are three things you must start doing with your code.
Use version control
Write tests
Create distributions
You say, "No need to waste my time, only people who work in teams need that."
Guess what, if anyone besides you will ever use your software OR its output, you're working on a software team.
In 3 months when the boss says, "Hey, can you run that analysis again on the new data?", you will look at the code and say "Who wrote this?". Once again, you're working on a software team, and wondering who hired that one guy anyway.
After the first, two posts about GCL maybe some words about the app I develop it with, because street wisdom says: you should construct any API not only in theory but also use it on some real world stuff before you release it.