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
Python:
from horses import Horse my_horse = Horse(color="brown")There. Done.
You built a horse in Python. There’s too much space between you and the horse so it dies.
I’ll just instantiate a new one.
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!
Thanks!
But notice that lisp was the only one where you actually built a horse.
Also assembly. And the dangling parts.
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.
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.
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!
That’s because it’s already so old, it can’t get older.
PHP is a vampire.
The assembly one isn’t fair.
Why not? KolibriOS is pretty basic for a OS. But boy is it fast.
And it runs Doom.
HTML runs Doom.
That’s a little reductive but but… sure.
Sounds like you have a future in network news 😉
deleted by creator
