A survey of the Perl Web Development job market

Having used the Dancer web framework for a year I was so impressed by the simplicity and clarity that in 2011 I started giving an annual Web Development class at the London Perl Workshop . By 2013 I'd noticed that one of the questions which often came up was along the lines of "is this going to get me a job?"

As recently as 2010 while no-one questioned the fact that Perl was still the duct tape holding together the Internet and Catalyst was a well established and comprehensive web framework, there was the sense that people weren't keen to start any new website using Perl. In retrospect though, the Perl Pumpkings had just found a regular release cycle and the community had produced two more cool and trendy web frameworks - Mojolicious (2008) and Dancer (2009).





In preparation for my last class I sent out a survey to collect information on the extent to which learning a Perl web framework will position people to find a job. It's not clear whether the audience of the survey was a representative sample, but I've extracted the definite outcomes from the data as far as possible. As you'll see, on the whole it paints a rosy picture of Perl on the web - but not without its thorns!





* Confession: The stats were collected in late November 2013 and it's taken me this long to read through and analyse them in detail. It should probably be called "Snapshot 2013 - Long Exposure."





Quantitative Analysis





The statistics are derived from information about 121 companies where multiple responses from a single company were averaged. The results I'm extracting from this data should also be taken in context - I sent the survey only to the Perl Monger mailing lists of San Francisco, London and Sydney as well as the LinkedIn Perl group. Gabor very kindly added it to the Perl Weekly bumping the responses up by 50%.









The first surprise was getting more responses from Australia (pop. 23 million) than from the UK (pop. 63 million). I'm willing to bet that Australia does not have over three times the Perl web developers per capita than the UK. This suggests to me that Australian Perl developers have stronger community engagement than their UK counterparts .





Back-end or Front-end or ... hey! what happened to Big and Little Endiens!?





The survey asked whether a company had Perl in the "front-end", "back-end" or both without explaining what I meant by these terms. That said, everyone filled it out so I can now assert:

It is universally accepted that - in reference to a website or web service - a front-end is a component which is accessible to the public while a back-end is only accessible from within the company which owns it.

Of the 121 companies covered in the survey, 120 (99%) use Perl for their back-end and of those, 74% use Perl for their front-end .





Perl Team Sizes and the Lone Ranger





This chart was particularly revelatory. On the left hand side there are 30 companies with a single Perl web developer, and via comments I deduced that a considerable portion of these developers do contract work for large companies. So the good news is that contract Perl developers are in demand . The bad news is that most of these 30 participants didn't provide a separate record for the companies to which they've done contract work. The survey didn't make that easy, but had it done so the orange line may have had its maximum toward the medium team size section of the chart.









Perl Web Technologies - What's Hot





Although I didn't ask which Perl packages were being used, sixteen respondents were kind enough to tell me anyway. In order of popularity the results were: Catalyst (7), Dancer (3), CGI (3), Mojolicious (2) and Template::Mustache (1 - who was not the module's author).





Are Perl teams expanding or contracting?





That's another question I forgot to write. I was informed by fourteen telepathic respondents that 10 of the teams were expanding while 4 were contracting .





These numbers aren't statistically significant so this is a good point on which to focus on the respondents' comments to put all these numbers in context.





The Qualitative Analysis

"Python is taking over Perl very fast and I see very slow development happening towards Perl 6"

"There is also plenty of Java and what not. Unfortunately the use of Perl is rapidly declining [and] most of the Perl devs have already gone."

"Perl presence is mainly legacy support. New developments are in other languages."

"Perl is being replaced by a Java based stack of technologies. It is arguable where this is increased or decreased productivity but it enabled them to use particular Java based technologies."

The comments above reveal that the companies of these respondents treat Perl as dead. As someone who develops and teaches in Perl there's no point defending it and pretending to be objective. However, considering:





Perl 5's regular release cycle since 2010;

the fact that the ratio of expanding to contracting teams was 10:4; and

lots of shiny new packages like Moose, Moo, Catalyst, Dancer, Mojolicious, Starman...





Godot Perl 6' issue. Like Godot, Perl 6 as a project has so many interpretations A more difficult concern to address is the 'Waiting forPerl 6' issue. Like Godot, Perl 6 as a project has so many interpretations in and out of the Perl community that it's a PR nightmare. The facts of the matter are that Perl 6:

is a different language to Perl 5;

positively contributes to Perl 5's R&D (e.g. the Moose OO system);

is a long way from being in production; and

(I'm willing to bet) is decades away from catching up in terms of having a comparable CPAN

The great challenge to the Perl community is to present it in such a way that it doesn't muddy the waters of day-to-day development decisions.