comment on

First, even if one of the perlmonks links mentioned Amazon, there are so many links here that you can't be sure that'll be noticed, so you should make that explicit. It'll probably be taken more seriously than /. or pm, which raises a question...
...is your audience going to be suits or coders? If the former, turns of phrase like "aiding and abetting" might not be a good idea if you trying to convince them of Perl's legitimacy.
I know you've got links to spare, but here's an excellent link I found today, surfing the Big Kahuna's home page. It's the only link on his page under "Advocacy":
- The Importance of Perl by Tim O'Reilly and Ben Smith.
It's got a lot about Perl vs. C/C++/Java, including for application development, and includes short versions of the success stories, including Amazon. It might make a good additional link; in any case, it should be worth reading for ideas.

-- Frag.

In reply to Re: Perl advocacy by frag
in thread Perl advocacy by tinman

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.