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.
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.
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!
This might be a client issue, eg: when images are too big, Thunder pixelate 'em


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.
On the boost app there's a tiny HD button you can click that should sharpen things up a bit.
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'm really having trouble recognizing if @marcos@lemmy.world started talking bullhoreseshit, or if the post by @Diplomjodler@lemmy.world is the first to be just trolling...
You built a horse in Python. There's too much space between you and the horse so it dies.
The assembly one isn't fair.
Why not? KolibriOS is pretty basic for a OS. But boy is it fast.
But notice that lisp was the only one where you actually built a horse.
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
λ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.λ🍎 gets executed and vanishes from the left, substituting 🍎 with (λ 🍎. 🐎️(🍎🍎))As a non-programmer, TIL Java and JavaScript are two different languages.
Person1: I built a script in Java.
Person2: So Javascript?
Person 1: NO!
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.
This is no time for joking around......I just wanna know if I can turn my webserver back on yet?! Hello?!? Anyone?!
Rust builds a unicorn
Goddamnit I actually snorted really loud at that one!
Glad to be of service. :)
I just saw this message by the way, probably an intance sync issue.
I didn't get any notifications for a few days, until half a day ago, so probably on my instance's part, no worries
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.
Ctrl-F "rust" - > 0 matches
I sense a pertubance in the force
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.
That's because it's already so old, it can't get older.
That's a little reductive but but... sure.
In Horse64:
import horses from horses.horse64.org
func main {
var my_horse = horses.Horse(color="brown")
}
And in Horse64 Root:
import horses from horses.horse64.org
func main -> bool {
var my_horse <- horses.Horse
my_horse.init("brown")
if failed(my_horse.init) {
return no
}
defer my_horse.destroy()
my_horse.run()
if failed(my_horse.run) {
my_horse.stop()
return no
}
my_horse.stop()
if failed(my_horse.stop) {
return no
}
my_horse.eat("hay")
if failed(my_horse.eat) {
return no
}
return yes
}
ruby: you built a horse that builds a horse to build your horse. your barn is too small. it crashes. everyone is dead.
Is it a dig against C# only being good when using it from F#, i.e. OCaml for .Net or am I overthinking this?
all 73 comments