And here I am glad that I try to avoid phpMyAdmin too, whenever possible.
This is no time for joking around......I just wanna know if I can turn my webserver back on yet?! Hello?!? Anyone?!
If you keep it off, it's significantly harder to get hacked.
Until your hosting service gets pwned..
Ctrl-F "rust" - > 0 matches
I sense a pertubance in the force
Well duh, Ctrl f doesn't work on pictures!
...yet. Then again, that's literally what "alt" on images is for.
Python:
from horses import Horse
my_horse = Horse(color="brown")
There. Done.
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.
and also the most recent horses release on pypi includes a crypto miner and credential stealer.
I cannot up vote this enough.
You built a horse in Python. There's too much space between you and the horse so it dies.
Or you accidentally used spaces instead of a tab on one line
Your horse is now an upside-down zebra
I'll just instantiate a new one.
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:
ฮปfgets executed and vanishes from the left, substitutingfinternally 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

Looks big enough to me.
This might be a client issue, eg: when images are too big, Thunder pixelate 'em


Good to know. ๐
It is indeed, thank you!
Well, this is the original as it gets, direct from the source.
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. ^^

The resolution is great on my end. That might be where the confusion was
Nah, that's ok. Though you have to click on the image for full resolution. On Lemmy it shows small for some reason.
Oh, didn't realize that, thank you!
No problem!
Needs a python horse in there.
Probably something about "why build a horse when you can just import horse from field?"
But it's built 10 years ago using conda so the installation process is more complicated than building a new horse.
"The horse turns out perfectly average, but boy it can't run"
But it still gets there faster than all the other horses on account of how easy it was to implement.
Sadly, it gets so long to go from point A from B that you wish you made the horse in something else...
horse()
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.
What's the biggest hurdle to porting old systems written in COBOL to newer languages? Besides the glaring conflict of interest for you.
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.
Hahaha port. Get a load of this person thinking COBOL is being ported! I bet they like the number 4.
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.
But notice that lisp was the only one where you actually built a horse.
Also assembly. And the dangling parts.
The LISP parentheses are not equally balanced. There are more ( than ).
Exactly 6 more.
)))))) There, the horse is contained now.
You thought so, but there was a teleporter
Shout-outs to enclose.horse!
Programmer Humor
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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.