714
top 50 comments
sorted by: hot top new old
[-] heartSagan5@lemmy.zip 1 points 14 minutes ago* (last edited 14 minutes ago)

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

[-] dasrael@lemmy.zip 4 points 2 hours ago

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 7 points 2 hours ago* (last edited 2 hours ago)

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

Until your hosting service gets pwned..

[-] Tja@programming.dev 3 points 3 hours ago

Ctrl-F "rust" - > 0 matches

I sense a pertubance in the force

Well duh, Ctrl f doesn't work on pictures!

[-] heartSagan5@lemmy.zip 1 points 17 minutes ago

...yet. Then again, that's literally what "alt" on images is for.

[-] Diplomjodler3@lemmy.world 37 points 8 hours ago

Python:

from horses import Horse 

my_horse = Horse(color="brown")

There. Done.

[-] marcos@lemmy.world 8 points 53 minutes ago

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.

[-] anewfox@lemmy.zip 3 points 34 minutes ago

and also the most recent horses release on pypi includes a crypto miner and credential stealer.

[-] thebardingreen@lemmy.starlightkel.xyz 1 points 26 minutes ago

I cannot up vote this enough.

[-] surewhynotlem@lemmy.world 35 points 8 hours ago

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

[-] StabbingSky@lemmy.zip 4 points 3 hours ago

Or you accidentally used spaces instead of a tab on one line

[-] surewhynotlem@lemmy.world 3 points 3 hours ago

Your horse is now an upside-down zebra

[-] Diplomjodler3@lemmy.world 9 points 6 hours ago

I'll just instantiate a new one.

[-] tetris11@feddit.uk 5 points 6 hours ago* (last edited 6 hours ago)

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
[-] GardenGeek@europe.pub 13 points 8 hours ago
[-] MehBlah@lemmy.world 7 points 5 hours ago

Looks big enough to me.

[-] Axolotl_cpp@lemmy.dbzer0.com 13 points 7 hours ago

This might be a client issue, eg: when images are too big, Thunder pixelate 'em

[-] victorz@lemmy.world 2 points 5 hours ago

Good to know. ๐Ÿ™

[-] GardenGeek@europe.pub 4 points 7 hours ago

It is indeed, thank you!

[-] muhyb@programming.dev 6 points 8 hours ago

Well, this is the original as it gets, direct from the source.

[-] GardenGeek@europe.pub 5 points 7 hours ago

All right. Sorry if that came across the wrong way: I wasn't actually trying to complain, I just used the meme because I noticed the low resolution. I don't know if I'm getting too old for this crap, but back in the day, that meme used to pop up all the time as a response to low-resolution images. ^^

[-] Bazoogle@lemmy.world 5 points 6 hours ago

The resolution is great on my end. That might be where the confusion was

[-] muhyb@programming.dev 4 points 7 hours ago

Nah, that's ok. Though you have to click on the image for full resolution. On Lemmy it shows small for some reason.

[-] GardenGeek@europe.pub 3 points 7 hours ago

Oh, didn't realize that, thank you!

[-] muhyb@programming.dev 3 points 6 hours ago

No problem!

[-] OwOarchist@pawb.social 57 points 14 hours ago

Needs a python horse in there.

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

[-] fxdave@lemmy.ml 9 points 8 hours ago

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

[-] MoffKalast@lemmy.world 32 points 12 hours ago

"The horse turns out perfectly average, but boy it can't run"

[-] Diplomjodler3@lemmy.world 9 points 8 hours ago

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 11 points 7 hours ago

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

[-] muhyb@programming.dev 17 points 13 hours ago
[-] yukichigai@kbin.earth 99 points 15 hours ago

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 9 points 7 hours ago

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

[-] WhyJiffie@sh.itjust.works 3 points 2 hours ago

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.

[-] Fmstrat@lemmy.world 31 points 7 hours ago

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

[-] Lyrl@lemmy.dbzer0.com 14 points 7 hours ago

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.

[-] somegeek@programming.dev 9 points 10 hours ago

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

[-] MonkderVierte@lemmy.zip 8 points 9 hours ago* (last edited 9 hours ago)

Also assembly. And the dangling parts.

[-] DreadPirateShawn@lemmy.blahaj.zone 57 points 15 hours ago

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

[-] muhyb@programming.dev 38 points 15 hours ago
[-] sneezycat@sopuli.xyz 44 points 12 hours ago

)))))) There, the horse is contained now.

[-] caseyweederman@lemmy.ca 7 points 6 hours ago

You thought so, but there was a teleporter

[-] sneezycat@sopuli.xyz 6 points 5 hours ago
load more comments
view more: next โ€บ
this post was submitted on 22 Oct 2026
714 points (98.4% liked)

Programmer Humor

33724 readers
2951 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 3 years ago
MODERATORS