Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Sad to hear that the branding exercise turned out so poorly (though not entirely surprising). I suspect that any attempt to work with a marketing agency that is not focused on marketing technology is going to result in something similar.

    There's also lots to be said about the " pinko marketing []" approach, for brands that have such a huge user community: i.e., marketing from the bottom-up vs. top-down.

    I jotted down some thinking on the "branding Perl" question in a recent blog post: "Getting to the root of P []

    Keeping technology simple since 2003
    • I really like the post you linked to and some of the responses. I can agree with the message. Back when I sold cars, I learned a couple of interesting things. First, selling Japanese cars was hard because I didn't give a damn about cars. Customers came in armed with invoice price lists, Consumer Reports, news articles, etc. They really were focused on value. When I switched to selling American cars, many people came in to "buy American" and while the cars were demonstrably a lesser value -- 3 versus 5

      • I must admit, I also like the "Creative power" messaging also. For me it's reminiscent of "Making Easy Things Easy and Hard Things Possible" -- which has always resonated for me when thinking about Perl's strengths.

        But that "creative power" message is probably aimed squarely at developers, and not business executives. And that's where I was going in the post referenced above: There could be -- and probably should be -- different messaging to each potential audience. For developers, Perl is "creative power." For executives, Perl is "ubiquitous and cost-effective." For learners, "Perl makes easy things easy, and hard things possible." And so on...

        I get a sense though that many Perl folks feel that the most important audience is the one you reference: big IT buyers. People at companies that manage large IT budgets and want to buy something secure and reliable. For them, commercial software may appear to have more value at first. However, once they get past that thinking and start to look at the free software options, that's where Perl is experiencing its biggest challenge. Specifically, the relative lack of shiny example projects (or the lack of profile that existing projects get in the Perl community).

        I'm not certain that the myth of TIMTOWTDI is even that relevant anymore. When I look at "Modern Perl," or idle in certain modern Perl Web Framework IRC channels, it becomes pretty clear that there are some consistently and strongly advised approaches to most challenges. Add to that PBP, Perl::Critic, and Perltidy, and you've got a fairly well-defined set of design patterns to apply to almost any problem.

        Perhaps it's time to shift the focus from the Perl we've had in the past (the TIMTOWTDI Perl), to the Perl we have now: creative power that is readable, scalable, maintainable, test-driven, etc.

        Keeping technology simple since 2003