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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||