79 comments

log in to comment.

  • @yukichigai@kbin.earth · 22 Oct 2026

    When I first saw this comic I was a relatively new COBOL programmer. It felt accurate.

    I am now my employer's senior COBOL dev. It still feels accurate.

    • @Madagaskar_sky@lemmy.world · 22 Oct 2026

      What’s the biggest hurdle to porting old systems written in COBOL to newer languages? Besides the glaring conflict of interest for you.

      • @Fmstrat@lemmy.world · 22 Oct 2026

        Hahaha port. Get a load of this person thinking COBOL is being ported! I bet they like the number 4.

      • @Lyrl@lemmy.dbzer0.com · 22 Oct 2026

        I think just the size of the projects. My employer has had a team of ten-ish people working full time on porting a piece of our COBOL program (the full thing was deemed not possible to port to a single modern application, so it’s getting split up) for about a year now. I was peripherally involved in four rounds of increasingly integrated testing environments. Go live was yesterday. They rolled it back three hours in.

        It’s hard for a company to invest multiple people’s salaries for many years on reworking software that currently mostly works.

      • @yukichigai@kbin.earth · 22 Oct 2026

        Mostly it's two things:

        1. COBOL is very good at some specific things that other languages can't do as well. Not that other languages do them badly, not at all, but COBOL is absurdly efficient for certain operations. You need to do basic math operations on millions of rows of data every minute? COBOL can do that easily. Many other languages can get close to that speed - maybe a few seconds off - but COBOL is often used in environments where a hundred millisecond delay can mean everything breaks. Are there other languages which can match that speed? Absolutely. Are they any of the languages every company wants to upgrade to? No.

        2. COBOL's best practices are sometimes the literal opposite of what every other language expects, especially when it comes to optimizing code for efficiency. You ever seen Evaluate, COBOL's equivalent of a switch statement? Rather than being used to Evaluate a variable to check its values, its most commonly used to "EVALUATE TRUE" and then use the WHEN clauses (basically case statements) to check statements or variables that you want to be true. That can be converted to another language directly, yes, but it absolutely will not be efficient best-practices code. Most likely you're going to need someone - not an AI, not an automated process - to do one-off rewrites to keep the code performance the same. As it is I have never seen any automated tool (LLM or otherwise) convert COBOL without falling victim to this issue.

        There's also a third issue in that COBOL has some specific minor capabilities that other languages just do NOT, or not to the level of flexibility and efficiency COBOL has. The most common one is COBOL's "88" picture type (variable) definitions. Think of it like being able to set an automatic evaluation on a variable that returns true if the condition is met, e.g. the variable "05 WS-ERROR-STAT PIC X." with an 88 of "88 FATAL-ERROR VALUE 'F'." would mean you could check "FATAL-ERROR" anywhere in your code to see if the value of WS-ERROR-STAT has been set to "F". The thing is, this is done basically for free (resource wise) as part of allocation, and furthermore it can be used to get or set, i.e. "SET FATAL-ERROR TO TRUE" will change the value of WS-ERROR-STAT to "F". You can also use 88s for ranges, e.g. "88 ANY-ERROR VALUES 'F' THRU 'N'.", though you can't use them for set operations that way.

        Bottom line: there's nothing that perfectly recreates its efficiency, the specific way it performs efficiently, and some of its more esoteric capabilities. Anything still running COBOL probably depends HEAVILY on one or all of these things.

      • @WhyJiffie@sh.itjust.works · 22 Oct 2026

        the cobol system was already tested for years or decades, important bugs are already fixed, it’s other quirks have became part of the workflow for people using it, and for other systems interacting with it, some of them likely also cobol. if you write a new system, it has to work the exact same way. same features, same bugs, same everything. but realistically it will have brand new bugs, it will miss some functions and do some others differently enough that it sometimes causes problems, and nobody knows why.

  • @OwOarchist@pawb.social · 22 Oct 2026

    Needs a python horse in there.

    Probably something about “why build a horse when you can just import horse from field?”

    • @MoffKalast@lemmy.world · 22 Oct 2026

      “The horse turns out perfectly average, but boy it can’t run”

      • @Diplomjodler3@lemmy.world · 22 Oct 2026

        But it still gets there faster than all the other horses on account of how easy it was to implement.

        • @Axolotl_cpp@lemmy.dbzer0.com · 22 Oct 2026

          Sadly, it gets so long to go from point A from B that you wish you made the horse in something else…

          • @Neverclear@lemmy.dbzer0.com · 23 Oct 2026

            It was so easy to make the first horse that you decide your field is big enough for three more horses, but somehow the second horse says it needs three more pastures to function properly.

    • @muhyb@programming.devOP · 22 Oct 2026

      horse()

    • @fxdave@lemmy.ml · 22 Oct 2026

      But it’s built 10 years ago using conda so the installation process is more complicated than building a new horse.

    • @ttayh@lemmy.zip · 22 Oct 2026

      from field import horse*

  • The LISP parentheses are not equally balanced. There are more ( than ).

  • @Diplomjodler3@lemmy.world · 22 Oct 2026

    Python:

    from horses import Horse 
    
    my_horse = Horse(color="brown")
    

    There. Done.

    • @marcos@lemmy.world · 22 Oct 2026

      horses was last released in 2024, and can only run on python up to 3.12.

      horses depends on iron-making, that is up to date. That means the current version of iron-making depends on python >= 3.14, and that all the versions prior to 2025 were taken offline due to a CVE where if you run the library as root in a web backend that uses the make_nail function, people can open your barn doors without authorization when inside it.

    • @surewhynotlem@lemmy.world · 22 Oct 2026

      You built a horse in Python. There’s too much space between you and the horse so it dies.

  • @GardenGeek@europe.pub · 22 Oct 2026

  • @db2@lemmy.world · 22 Oct 2026

    The assembly one isn’t fair.

    kolibrios.org/en

  • @ohshit604@lemmy.halstead.host · 22 Oct 2026

    As a non-programmer, TIL Java and JavaScript are two different languages.

    • @BCsven@lemmy.ca · 22 Oct 2026

      Person1: I built a script in Java.

      Person2: So Javascript?

      Person 1: NO!

    • @Nowtayneicangetinto@thelemmy.club · 23 Oct 2026

      When JS was being developed, Java was all the rage and it merely was riding it’s coattails. At the time of its creation it was nothing like Java either.

  • @tetris11@feddit.uk · 22 Oct 2026 · edited

    The Fixed Point Expression / Y Combinator expressed in horses:

        Y = (λ f. (λ x. f(xx))(λ x. f(xx)))
        ;; so then, give Y a horse argument with apple parameters:
        Y🐎️ = (λ f. (λ 🍎.  f(🍎🍎)) (λ 🍎. f(🍎🍎))) 🐎️   ;; [1]
            =       (λ 🍎. 🐎️(🍎🍎)) (λ 🍎. 🐎️(🍎🍎))      ;; [2]
            = 🐎️(   (λ 🍎. 🐎️(🍎🍎)) (λ 🍎. 🐎️(🍎🍎))   )  ;; [3]
            = 🐎️(Y🐎️)                                       ;; [4]
    
    Explanation

    * 1: x is 🍎, but could be anything. It’s just a function parameter nested within another. * 2: λf gets executed and vanishes from the left, substituting f internally with 🐎️. This is now a new function, with left group as the function body, and right group as the function argument, despite being identical. * 3: λ🍎 gets executed and vanishes from the left, substituting 🍎 with (λ 🍎. 🐎️(🍎🍎)) * 4: Everything within the main brackets at [3] has been seen before at [1], but with f being 🐎. Thus we have bred a new horse. We can breed infinite horses this way

  • @gnuplusmatt@reddthat.com · 22 Oct 2026

    Rust builds a unicorn

    • @muhyb@programming.devOP · 22 Oct 2026

      ho-rs

      • @lord_ryvan@ttrpg.network · 30 Oct 2026

        Goddamnit I actually snorted really loud at that one!

        • @muhyb@programming.devOP · 4 Nov 2026

          Glad to be of service. :)

          I just saw this message by the way, probably an intance sync issue.

          • @lord_ryvan@ttrpg.network · 5 Nov 2026

            I didn’t get any notifications for a few days, until half a day ago, so probably on my instance’s part, no worries

            • @muhyb@programming.devOP · 5 Nov 2026

              Ah I see. It seems there was a version update for Lemmy so could be on both sides as well.

    • @ulterno@programming.dev · 24 Oct 2026

      It is perfect and will run for a million years.
      Dodges all traps and jumps over all ditches whether you see them or not.
      But you are already too old to ride it.

  • @somegeek@programming.dev · 22 Oct 2026

    But notice that lisp was the only one where you actually built a horse.

  • @LodeMike@lemmy.today · 22 Oct 2026

    That’s a little reductive but but… sure.

  • @dasrael@lemmy.zip · 22 Oct 2026

    This is no time for joking around…I just wanna know if I can turn my webserver back on yet?! Hello?!? Anyone?!

    • @NotAnOtter@lemmus.org · 22 Oct 2026 · edited

      If you keep it off, it’s significantly harder to get hacked.

      Until your hosting service gets pwned…

  • @Tja@programming.dev · 22 Oct 2026

    Ctrl-F “rust” - > 0 matches

    I sense a pertubance in the force

  • @merc@sh.itjust.works · 23 Oct 2026 · edited

    C: You build a horse. Well, it’s not really a horse, but it can do almost all the essential horse-things. It’s incredibly fast and compact. Your horse is named “Blue\0\0\0\0\0T~31wsXEi]DiMGW8mh^3”. Oh, and now someone else owns it.

  • @_stranger_@lemmy.world · 22 Oct 2026

    That’s because it’s already so old, it can’t get older.

  • @Null42x86@lemmy.world · 23 Oct 2026

    you could say that it aged well

  • @j_z@feddit.nu · 22 Oct 2026

    Is it a dig against C# only being good when using it from F#, i.e. OCaml for .Net or am I overthinking this?

    • @ElDuderino@lemmus.org · 23 Oct 2026

      I don’t know. I thought it was a dig with certain C# dev products trying to mimic how other technologies behave, like WebForms.

  • @heartSagan5@lemmy.zip · 22 Oct 2026 · edited

    And here I am glad that I try to avoid phpMyAdmin too, whenever possible.

  • @GreenKnight23@lemmy.world · 23 Oct 2026

    ruby: you built a horse that builds a horse to build your horse. your barn is too small. it crashes. everyone is dead.

  • @MonkderVierte@lemmy.zip · 22 Oct 2026

    [deleted]