in reply to Migrating Perl to Java or .NET

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

Replies are listed 'Best First'.
Re^2: Migrating Perl to Java or .NET
by Jason Hollman (Novice) on Mar 24, 2005 at 21:22 UTC
    Yes, this can be an issue. But again, it has been considered. by knowledgable people and a determination has been made and those costs are considered acceptable given the benefits.

    --Jason

[reply]

      And the benefits of migrating are what? The benefits would have to be pretty spectacular to offset the costs involved (which will be astronomical when you consider all aspects of this venture).

      Update: It's sounds an awful lot like Smiling Man or Stef Murky have had a hand in this.

[reply]
        And the benefits of migrating are what?

        I don't mean to be disrespectful by avoiding the question but that information is proprietary to the company, having to do with our overall strategy. Ask me in a year when it's all said and done and hopefully I can give you the reasons then.

        --Jason

[reply]

In Section Seekers of Perl Wisdom