News for hackers. Stuff that matters.
Re:The persistence of COBOL: why a 60-year old language is s... by ape4 on Thursday October 22, 2020 @09:15AM (#24857642)
Did somebody think the code would somehow disappear.
Re:The persistence of COBOL: why a 60-year old language is s... by rbanffy on Thursday October 22, 2020 @09:44AM (#24857898)
I can tell you from first-hand experience people expected the systems would be gradually migrated to new languages (and out of mainframes) at some point in the 1990's.

A lot of those migrations failed miserably. Others failed spectacularly.

Re:The persistence of COBOL: why a 60-year old language is s... by commandlinefan on Thursday October 22, 2020 @11:34AM (#24859114)
That was the mindset that got us the Y2K bug 20 years ago.

I remember seeing a lot of fixes for the Y2K bug that looked like this, too:

    if (year > 50) {
        year += 1900;
    } else {
        year += 2000;
    }
So expect another Y2K crisis in about 30 years.
Re:The persistence of COBOL: why a 60-year old language is s... by rbanffy on Thursday October 22, 2020 @01:22PM (#24860525)
Using two digits for years is not a language issue. You can migrate your systems from 2 to 4 digits without having to rewrite your code in Java 1.2.

This was, in fact, how most of it was done.

Re:The persistence of COBOL: why a 60-year old language is s... by ape4 on Thursday October 22, 2020 @04:28PM (#24862947)
Hopefully code like this is marked with a standard comment for future grepping.
Re:The persistence of COBOL: why a 60-year old language is s... by GoblinSlayer on Thursday October 22, 2020 @01:13PM (#24860401)
s/50/70/