• mesa@piefed.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    23 days ago

    I used to work with COBOL. The language isn’t terrible, it’s the 40+ years of no context changes that suck. It even works with SQL… although the most common configuration is using a flat file.

    • Tja@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      23 days ago

      Given that SQL is 50 years old, I’m not surprised they go hand in hand. I’d be more surprised if it integrates seamlessly with Kafka, k8s, MongoDB or lambda.

      • mesa@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        23 days ago

        Try opencobol. You may have more success.

        Some cobols like rm COBOL require a literal custom Linux header in order to work with SQL. Others work with odbcs natively.

    • TeamAssimilation@infosec.pub
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      23 days ago

      I worked with COBOL for a good part of a decade. It’s a joy to see structured and well-commented code from pros, the consistency is such that there’s a point after a few months when you “get it”, and the code base becomes like putty in your hands.

      Never have felt that way with modern platforms, with the exception of maybe Python. Old-school structured programming can be beautiful, and the tooling is super straightforward. Development these days has taken a turn for the worse in terms of sheer complexity for even simple tasks.

      TL;DR: If if pays well in your market, don’t be afraid of COBOL if you’re a capable software developer. You will get it faster than you think.