• ExcessShiv@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        1
        ·
        9 hours ago

        That kind of bullshit thinking is why I have to do shitty half-assed solutions because I need to work around unsupported equipment that’s 50 years old and was EOL’ed three decades ago. At some point you absolutely should upgrade even if it isn’t broken.

        • Taldan@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 hours ago

          The absolute #1 priority in aviation is safety. Old, stable systems are safer. Just add new systems in parallel for new features

        • 3laws@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 hours ago

          It fact you just gave us the true answer.

          If it ain’t broke don’t fix it, so now when it breaks it can’t be fixed.

    • cdnk5@piefed.ca
      link
      fedilink
      English
      arrow-up
      5
      ·
      18 hours ago

      Lol I use software every day that was written in COBOL. It would cost billions to replace. So leadership never wants to add that expense to their budget so they just hobble along and leave it for the next people.

      • walden@wetshav.ing
        link
        fedilink
        English
        arrow-up
        1
        ·
        14 hours ago

        I’m pretty sure the software I use for work is written in COBOL too, but they’re currently in a multi-year rollout of a modern replacement. So that’s good, I guess.