Modules vs. Applications
While still drawing the differences between programmers, language practices and behaviors, I stumbled upon another major issue. Our tendency to write modules instead of applications.
This is a touchy subject, I'm sure, and I hope not to offend anyone.
Since the majority of Perl programmers are actually sysadmins by day [and superheroes by night], we're accustomed to writing pieces of software, "modules". We have CPAN to host all these modules. Occasionally we might write a program, an App, a small cute frontend to some module that we have. CPAN supports that.
This is all fine and dandy but when making an effort to market our kickass language, we need to tackle different approaches of marketing. One of them is the impression of producing something to the general public. A concept that is strong in marketing, but illusive to understand and tackle.
The illusiveness of it is mostly due to the way people judge and calculate your general public donation. If I'm a non-Perl programmer, and I wish to see how Perl contributes to the general public (me, for instance), I do not look at modules.
For the general public, the best way to view contribution is with applications. Applications give the impression of contribution greater than modules because they can be used by anyone: programmers, non-programmers and definitely non-Perl programmers. Sure, you could showcase a few technologies that would make their work much easier and many would appreciate it, but nothing scream "hell yeah" like a program someone likes.
People are busy creating programs while most of us (including myself, of course) are busy writing modules that could theoretically (or in practice) be used by applications. An important take on marketing is showing power, finesse, flexibility and beauty. The easiest way to show this (or perhaps, the most difficult way) is using actual application people can use without needing to write a CLI/GUI wrapper for it in Perl.
It might seem absurd for a lot of hardcore oldschool Perl programmers (and I expect a mirage of flames in the comments) but telling a friend that IMDB is written in Perl does hell of a lot more than saying "look at Catalyst, it's a really good MVC!" And it's absurd, I know, because that's merely the interface, but if there's one thing I learned from my offline activism is that what makes sense isn't what necessarily makes marketing.
Let's start writing programs, applications, things everyone can use!