Advocacy isn't just about shouting from the rooftops. The single greatest piece advocacy that Perl has is the fact that Amazon and CitySearch both run on it, after both evaluated and discarded Java as unable to meet their needs. So, if we have a lot of small businesses choosing to use Perl over some other choice, that is advocacy.
Java's greatest piece of advocacy is "Everyone else is doing it, so you won't be fired when the project fails." Sun can point to hundreds of mid-size companies that have large Java projects. Java projects have hundreds of developers on them. Hence, you have to keep up with the Joneses. That is advocacy at its finest.
Since Perl doesn't require dozens of developers on a single project, that's actually seen as a detriment to some PHB's. So, we need to be able to point to succesful ventures like Flying Car Television as startups that succeed basing their infrastructure on Perl. Otherwise, we lose the advocacy war.
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.