in reply to Migrating Perl to Java or .NET

The directive is to move to Java or .NET. We cannot start from scratch.

I think you need to sit down with your boss and explain very carefully why this isn't possible. Switching programming languages almost always means starting from scratch in some sense. Sooner or later you'll have to rewrite everything you wrote before. There had better be a good reason!

...and of course, it's obvious that there isn't a good reason. If the people asking for this switch don't even care if you use Java or .NET, two completely different systems, then they really have no business telling you not to use Perl!

-sam

Replies are listed 'Best First'.
Re^2: Migrating Perl to Java or .NET
by Jason Hollman (Novice) on Mar 24, 2005 at 18:07 UTC
    I think you need to sit down with your boss and explain very carefully why this isn't possible. Switching programming languages almost always means starting from scratch in some sense. Sooner or later you'll have to rewrite everything you wrote before.

    Yes, we are aware of this and know that eventually everything will be rewritten. If it is technically impossible, e.g. trying to run Windows on Univac, that's one thing, if it's just pain and waste, I need to figure out how much pain and waste. It sounds like it is possible, even if not desirable--or do you disagree with the other replies?

    ...and of course, it's obvious that there isn't a good reason.

    I really don't want to start a flame on this; suffice it to say, the decision is made. There are valid reasons for it (not everyone may agree, but it's not simply religious decision or an uninformed pointy haired boss). There are pro's and con's to choosing Java or .NET and I need to evaluate those, too.

    --Jason

[reply]

In Section Seekers of Perl Wisdom