221
[DISCUSS] IBM using LLMs to convert COBOL to Java (techcrunch.com)
submitted 2 years ago* (last edited 2 years ago) by to c/technology@lemmy.ml
115 comments fedilink hide all child comments
 

It's not the 1st time a language/tool will be lost to the annals of the job market, eg VB6 or FoxPro. Though previously all such cases used to happen gradually, giving most people enough time to adapt to the changes.

I wonder what's it going to be like this time now that the machine, w/ the help of humans of course, can accomplish an otherwise multi-month risky corporate project much faster? What happens to all those COBOL developer jobs?

Pray share your thoughts, esp if you're a COBOL professional and have more context around the implication of this announcement 🙏

you are viewing a single comment's thread
view the rest of the comments
[–] 19 points 2 years ago* (6 children)

according to a 2022 survey, there’s over 800 billion lines of COBOL in use on production systems, up from an estimated 220 billion in 2017

That doesn't sound right at all. How could the amount of COBOL code in use quadruple at a time when everyone is trying to phase it out?

  • permalink
  • fedilink
  • source
  • hideshow 12 child comments
    •
  • [–] 18 points 2 years ago (1 child)

    Because it’s not actually getting phased out in reality

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 7 points 2 years ago (2 children)

    But it isn't getting quadrupled either, at least because there aren't enough COBOL programmers in the world to write that much new code that quickly.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 6 points 2 years ago

    That doesn’t sound right at all. How could the amount of COBOL code in use quadruple at a time when everyone is trying to phase it out?

    Because why they're trying, they need to keep adding business logic to it constantly. Spaghetti code on top of spaghetti code.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 2 years ago

    It could mean anything, the same code used in production in new ways, slightly modified code, newly discovered cobol where the original language was a mystery, new requirements for old systems, seriously it could be too many things for that to be a useful metric with no context

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 2 years ago*

    trying

    That's the keyword right there. Everyone wants to phase mainframe shenanigans out until they get told about the investments necessary to do it, then they are happy to just survive with it.

    I'm currently at a company that's actually trying it and it's being a pain

  • permalink
  • fedilink
  • source
  • parent