I brought a lot of people into the Perl camp a dozen years ago by answering questions in comp.unix.questions with both a shell answer and a Perl answer. The Perl answer was almost always shorter and easier to read, and almost always faster as well.

Perhaps you can do the same. Say "here's how to solve that in $LANGUAGE_X, but the Perl solution looks like this...". Do it enough times, they'll get the hint.

These days, the big winner seems to be the CPAN. So if you're in some $LANGUAGE_X design meeting, and someone mentions some basic task, just mutter "you know, I bet there's a freely available CPAN module for that part of the problem". Even if there isn't, they'll eventually get the hint.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.