You actually proved exactly what the orginal author tried to say - the opposite of what you thought you were proving, perl is not mission critical, but only as a tool - in your case, a building tool.

Is building a serious step of the process? yes, but is it a serious part of the actual application system that delivers the functionality? you didn't indicate, but most likely no, otherwise you would have emphasized.

Perl is not enterprise class, that even lots of Perl guys, like me see it crystal clear.

Go back to one of the point in the original post, which he added after reading some of the replies - that with proper project management, any language can deliver enterprise class system. Look at this from a different point of view: if the management of the project choose Perl for enterprise class system (not as a tool, but as the core), then the management failed right there. No need to go further, I tell you, they failed miserably.

Perl was sexy, as it was and is free, but free is no longer the point any more, java is free, ruby is free, the list goes on and on. Even .Net IDE is now free.

How many people will start a new project with CGI? maybe a handful. Perl was the only sexy girl in the class during the CGI era, but now, even I agree that Perl is not ugly, there are also many other pretty girls, why has to be Perl?

Agree or not, Perl has a bad reputation for being not enterprise. What perl can deliver is unique, and none other languages can deliver? nothing, okay if that's the case, why should I not choose something that has a good reputation? is it not true that one key point of project management is to control the risk? Put in this way, Perl might be a vigin, however quite a few people saying that Perl is a prostitute, do you still want to marry Perl. Remeber there is a chance that she is really a vigin, but the key point is why take the risk? is she the last girl on earth?

In reply to Re^2: Perl in the Enterprise by Anonymous Monk
in thread Perl in the Enterprise by Scott7477

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.