in reply to Re: Migrating Perl to Java or .NET
in thread Migrating Perl to Java or .NET

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

Replies are listed 'Best First'.
Re^3: Migrating Perl to Java or .NET
by Mr. Muskrat (Canon) on Mar 25, 2005 at 03:53 UTC

    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.

      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

        I'll take a general stab in the dark -- you're planning on selling (leasing, licensing, or whatever the technical term is for letting the person giving you money use it without having any real rights to the program).

        By switching to a language that you can compile, you ensure that people can't just look at the code, and they have to either pay for support to have problems fixed, or do a whole lot of work with a decompiler (which of course, you'd make sure to prohibit in your licensing terms.)

        Am I close?

        (it's the only reason I can think of that you'd spend the effort to take perfectly functional code, and accept the cost to rewrite the whole thing in a different language, and not be concerned with exactly what language you're going to)