I think I see this from a different perspective ( I know nothing about Java or .NET and very little about Perl. ) the powers_that_be are asking for a wholesale change in toolset. How well this works depends on the skillset and training of the workers using the tools.

The programmers who developed the existing Perl code have already spent time learning the application, the existing code base, and the available tools. Some company has paid for their salaries while they did this. The programmers have reached a certain productivity level with these tools.

Now you take all the old tools, set them aside, and put in new tools. Their productivity is going to go to zero. In addition mistakes are going to be made. Even if you were to replace the programmers with ones familiar with Java and .NET they would not be familiar with the application nor the existing code base. They would have to spend time getting familiar with the old code. In addition, mistakes would be made in translating from the old codebase.

I'm not arguing against doing it. Like you said there are very real reasons to do it. I'm just pointing out the potentially huge productivity hit and the need for the company to invest in training and tools. If the company does not invest sufficiently in training and new tools then it risks becoming uncompetitive in it's market.

Yes, it can be done, but it also can be done wrong!

You've got to ask yourself: "Which of many areas are the programmers going to be spending their time on? Learning a new language, learning a new methodology, reviewing old code, rewriting old code, rewriting old tools, building new tools, testing?" They can't do all of it. In situation like this I always recommend the company hire outside help to build tools for the programmers to use. Anything to speed up the adoptation of the new toolset. Also in your case there is going to be a big testing requirement so additional manpower will be needed there too.

P.S. Training; Not just training in the new tools but in training new workers in the old systems.

Authority indeed proceeds from true reason, reason never proceeds from authority. - John Scot Eriugena

In reply to Re: Migrating Perl to Java or .NET by starbolin
in thread Migrating Perl to Java or .NET by Jason Hollman

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.