What reasons did they give for this change? The reason I'm asking is that any change of this magnitude must have been undertaken with the foreknowledge that a) it's a serious chunk of work (time, money, resources) and b) it's going to take some time to get it right.

Possibly -- or it could be that some higher up got caught up by a Java evangelist and has decided to throw away some years of working Perl code in favour of a new solution in Java. It would have made more sense if they'd announced that new development would be done in Java and any Perl projects would be phased out in favour of Java rewrites.

I do remember (during the Internet boom) working on a web site that generated hundreds of graphs a second using mod-perl and gnuplot, running on a pretty plan piece of hardware, while our competitor was running a Java application on some humongous piece of Sun hardware and getting ten graphs per second. Sometimes you just can't beat Perl's performance.

You're going to hear good and bad about just about every piece of technology .. get used to it. For me, the bottom line about Perl is, a) can I quickly develop (and maintain) code, b) is it stable, c) is it extensible and flexible and d) is there community support. Yes, yes, yes and yes.

So I'm not sure how Java is a better choice on any technical grounds .. however, there may well be political or religious angles that we cannot infer from your posting.

By all means learn Java .. it's never a mistake to learn something new while your employer's paying for it .. and in the meantime, keep your eyes open for any other opportunities out there. Who knows, you may end up loving Java .. it's possible, isn't it?

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds


In reply to Re: Should I stay with this company or leave? by talexb
in thread Should I stay with this company or leave? by Anonymous Monk

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.