You seem to be saying that given a set of very unusual requirements which Perl is obviously ill-suited for, you would use a specialized tool instead. I don't see how anyone could disagree with that. But the original poster didn't have these specialized requirements. He was concerned about using Perl to build a high-quality system. There is no problem with using Perl to do that.
I also believe that the Java project you refer to stands a good chance of spending millions, taking years, and producing something unsatisfying, regardless of the language chosen. I don't think Perl is going to make it any harder to write than Java. (Java in a totally fault-tolerant system? That's madness.)
-
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.
|
