Perlceptions

Call me a curmudgeon (and many do), but I just can't understand why intelligent folks make the choice to completely ignore Perl…

I got a great e-mail from Gabor earlier this week that proposed a simple challenge: Let's not get distracted trying to promote Perl itself, but -- instead -- let's focus on promoting projects written in Perl…

A couple weeks back, I asked the question Where is the big 'Explore Perl' button? and followed up last week with a short demo of the kind of thing I was thinking about…

This isn't really a post…

How can we make Perl more explorable? That's the question I've been wrestling with since my last post about Getting to the root of Perl's perception problems. (By the way, thanks for all of the feedback -- very helpful)…

Following on the last post about Prettier Perl Web sites and taking Sebastian Riedel's Don’t explain what you think would look better, just make a mockup and show us! challenge to heart, I spent some time looking at Perl's existing design patterns…

In doing a bit of background reading for this post, I stumbled on Sebastian Riedel's Perl Monk post from 2008 titled Prettier Perl websites. The discussion on that post is a fun read, as it highlights the polarization in the Perl community around Perl's (rather lousy) public image…

Given the active conversation unfolding around the perceptions of Perl, I wanted to follow-up with what was originally part of my previous post on the Perl community's multiple personality problem…

I got a great e-mail from Gabor earlier this week that proposed a simple challenge: Let's not get distracted trying to promote Perl itself, but -- instead -- let's focus on promoting projects written in Perl…

This isn't really a post…