Re: Bootcamp

On 7/12/2025 7:52 PM, bill wrote:

On 7/12/2025 1:42 PM, Arne Vajhøj wrote:

On 7/12/2025 1:26 PM, bill wrote:

On 7/12/2025 11:13 AM, Arne Vajhøj wrote:

So again again if you rewrite an application, then you want
to change that logic instead of doing the 1:1 conversion.

>
And this, of course, is where we disagree.  You see rewrites as
normal and the best way to go.  I see them as usually a waste of
time being called on for the wrong reasons.  Because your peers
at a conference laugh at your legacy system is no reason to rewrite
it.  (And, yes, I have seen senior management want to make major
and often ridiculous changes based on something their peers said
over lunch at a conference!!)

>
There is a whole discipline dedicated to determining
if, when and how to modernize IT systems.
>
But mistakes are made.
>
Some systems are attempted to be modernized even though they should not.
>
Some systems are kept even though they should have been modernized.

 It's funny to see someone say that here. The whole IT world has been
saying that about VMS for a very long time.  I would have thought here
was the last bastion of "If it ain't broke, don't fix it."

Based on previous discussions then there are several "If it ain't
broke, don't fix it." people here.
But I do not consider myself one of them.
You evaluate benefits, cost and risk of upgrade projects
and decide based on that analysis.
And long term it is not so much a question about IF but more
a question about WHEN and HOW. Is it now or in 3 years or in
10 years? Just add functionality or rewrite some old parts
or rewrite everything?

The second is probably more common than the first.

 "Being common" .NE. "right" .OR. "even necessarily a good idea".

I don't see how one mistake being more common than another
mistake relates to right or good idea.
Arne