comment on

My employers are moving from "some Perl and lots of C CGIs" to basically a complete Java shop. One of their major arguments for not using Perl at all is that "it is not supported." What they meant by that, to the best of my knowledge, is that there isn't any paid support for Perl.

We did a little searching and found that ActiveState has Commercial Support available for Perl (and I am sure there are others).

Now the "powers that be" are reconsidering their stand, especially after my group of three pumped out some quick code to do some pretty involved statistics and data mining, all in less time than it took them to put "formal requirements" around the project.

So, I don't know if "support" may be part of the argument for Java (and possibly against Perl), but it shouldn't be.

In reply to Re: Client prefers java, but wants to hear a case for Perl by Daddio
in thread Client prefers java, but wants to hear a case for Perl by Ovid

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.


"be consistent"
	PerlMonks