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.
  • But then he never heard about the Israeli Perl Mongers.

    That's probably why he thinks he's the best :-) He thinks he's the only one :-)

    I've seen that happen quite often, believe me :-) Even where I work :-) There's a guy in the same floor I'm in who's thought to be a real great Perl programmer just because he does the ocasional script for a boss, but he doesn't even know that there are conferences on Perl, he doesn't use strict nor warnings and does some magnificent things I wouldn't wish to my worst ene

  • What you need to realise is that the vast majority of the Perl (or PERL!) programmers in the world have no contact at all with the Perl community. Most programming languages don't have a community like ours so a new programmer won't necessary go looking for it. Most Perl books don't emphasise the community aspect of Perl, many of the most popular ones don't even mention it.

    I'm not at all surprised by the number of Perl programmers who happily exist outside of the community. I _am_ surprised by the number o
    • I would still put a lot more stock in a programmer who is "plugged in" to the community. Anyone who's got six years of experience with Perl or PERL (hey ... I got six years!) could benefit extremely from contact with the community. We all know there are good books and bad books out there. Most programmers do their learning from those books. Those who are in contact with the community have additional sense about how to evaluate those books, as well as the accelerated reinforcement of learning that contac

      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
    • Most Perl books don't emphasise the community aspect of Perl, many of the most popular ones don't even mention it.

      Which means that most of those books were written by people that were not "plugged in" as well. Which means that we probably have more of "blind leading the blind", because they won't be talking about cool things like the mailing lists and Perlmonks and the CPAN.

      And if that's the only place where a person got his "PERL" knowledge, then he's also not a very effective Perl programmer. He

      • Randal L. Schwartz
      • Stonehenge
    • For the French translation of the Camel book (3rd ed.), we conviced O'Reilly France to insert a page long presentation of the French Perl Mongers (it was just Paris, back then). That was easy to do, since the three translators and the reviewer were from

      The text appeared in chapter one, which most people overlook(*) anyway, so I don't know if anybody noticed...

      (*) OK, I do read chapters 1. But then I often overlook most of the other chapters...

  • I just looked at my book shelf, here is what I saw that capitalized it:

    - PERL Black Book
    - PERL Annotated Archives
    - PERL 5 HOW-TO

    Granted, most capitalized the entire title, but most of the older books capitalized just PERL.

    A random look inside the books, however, show all refering to the language as Perl.
    • Capitalization of the title on the cover or home page is a design decision, not an editorial decision. Even if it says "PERL Black Book", that's not the correct rendering of the title, any more than you'd say "GONE with the WIND" just because the cover artist happened to like the way the words fit together with that capitalization.

      Looking inside the books, as you did, is the way to go, so your report actually indicates that none of them used "PERL".