I can understand there being discussion about the language at the start of a project, but you seem to be saying that the project has already started and the client wants to rewrite code in Java. Rewrite, do again. A case of "if it ain't broke then fix it anyway".

Or maybe the client just wants the rest of the project in Java, so now you have language compatibility problems. Switching languages for no good reason mid-project just does not make sense, these must be something more to it, surely?

There are non-technical reasons for choosing Java (or any other language), maybe the client is Sun or Oracle, in which case it would be understandable. I have seen some clients, commercial and state, that only employ programmers with some certification track qualification. Java has that and Perl does not. More likely though the client has a skewed view of Perl as a language. In some quarters Perl still has a reputation for not being a serious language, but more a hacking tool. Google "Perl success stories" might find what you are looking for.

Java is backed by a big corporate with pots of money, which makes the suites more comfortable. That's a completely false sense of security (as the current banking crisis shows) but its hard to fight.

In reply to Re: Reasons to hate Java? by cdarke
in thread Reasons to hate Java? by paragkalra

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.