#harlequin — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #harlequin, aggregated by home.social.
-
Oof, dozed off at the end and woke up to Stallone's Cobra. Now that's scary! See y'all next time.
#FullMoonFrights #Harlequin
static.klipy.com/ii/4e7bea9f7a3... -
Oh no!! Did Harlequin take her baby's soul? Is that why he sounded like a girl..?
Oh movie you or I got lost somewhere along the way, but I always appreciate @[email protected]'s esoteric picks!
Have a good night, #FullMoonFrights magician's assistants.
#Harlequin
Cainii Blestem - Rasputin -
David Hemmings's hair is so gray in the last shot! (for a 39 yo)
#FullMoonFrights #Harlequin -
Chinese Checker fu!
#FUllMoonFrights #Harlequin -
Leave the cat alone!
oh no it's too late 😿
#FUllMoonFrights #Harlequin -
Wow, the screenwriter also wrote Long Weekend ('77), Patrick ('78) and Roadgames ('81).
#FUllMoonFrights #Harlequin -
Oh wiki says this is set in the US. Nick Rast is a US Senator...
#FUllMoonFrights #Harlequin -
Man oh man, I sure would NOT like to do time dressed like General Zod.
#FullMoonFrights #Harlequin
static.klipy.com/ii/4e7bea9f7a3... -
It seems like they dubbed all the Australian accents with British and American ones?
#FUllMoonFrights #Harlequin -
And they just start wailing on him immediately hahaha! That's obviously what they wanted from the get-go. Just any excuse to lay on their own hands.
#FullMoonFrights #Harlequin -
Now that you've cut that poor bird in two with a cymbal for no reason, could you treat me too?
#FUllMoonFrights #Harlequin -
Haha, I just got it: Rast ----> Tsar #FullMoonFrights #Harlequin
static.klipy.com/ii/84b4c0b0278... -
"that live-in layabout!"
Hope I can use that some day
#FullMoonFrights #Harlequin -
So... he's giving her everything but the d? is that what's happening?
#FullMoonFrights #Harlequin -
I cannot believe Broderick Crawford ended up in this somehow, in a helluva promotion from the Highway Patrol to boot.
#FullMoonFrights #Harlequin -
Why are they wearing tuxes 😭😭😭
#FullMoonFrights #Harlequin -
what the heck was all that typing about?!
#FullmoonFrights #Harlequin -
Is this set in Australia? But no one has an Australian accent?
#FullmoonFrights #Harlequin -
Joining #FullMoonFrights for #Harlequin. Had to jump in the shower first but I pre-gamed so I don't think I've missed too much....
-
Oh look, an Aussie movie with a Brian May score. I can't believe it.
#FullMoonFrights #Harlequin
static.klipy.com/ii/d7aec6f6f17... -
#NowWatching
#Harlequin (aka Dark Forces, 1980)
Dir. Simon Wincer
Oh, I can't wait to see what all THIS is about. #FullMoonFrights -
‘Heated Rivalry’ Author Rachel Reid Has Advice For Studios Circling Romance Adaptations, Teases ‘Unrivaled’ & Celebrates Harlequin Takeover At Fenway Park
#Books #News #BostonRedSox #ConnorStorrie #CraigSwinwood #Crave #FenwayPark #Harlequin #HBO #HudsonWilliams #RachelReid -
‘Heated Rivalry’ Author Rachel Reid Has Advice For Studios Circling Romance Adaptations, Teases ‘Unrivaled’ & Celebrates Harlequin Takeover At Fenway Park
#Books #News #BostonRedSox #ConnorStorrie #CraigSwinwood #Crave #FenwayPark #Harlequin #HBO #HudsonWilliams #RachelReid -
‘Heated Rivalry’ Author Rachel Reid Has Advice For Studios Circling Romance Adaptations, Teases ‘Unrivaled’ & Celebrates Harlequin Takeover At Fenway Park
#Books #News #BostonRedSox #ConnorStorrie #CraigSwinwood #Crave #FenwayPark #Harlequin #HBO #HudsonWilliams #RachelReid -
‘Heated Rivalry’ Author Rachel Reid Has Advice For Studios Circling Romance Adaptations, Teases ‘Unrivaled’ & Celebrates Harlequin Takeover At Fenway Park
#Books #News #BostonRedSox #ConnorStorrie #CraigSwinwood #Crave #FenwayPark #Harlequin #HBO #HudsonWilliams #RachelReid -
https://www.europesays.com/people/211829/ Leonardo DiCaprio and Jeff Bezos lead $200M project to save 100 of globe’s most threatened species #100 #ap #AssociationFanamby #Attenborough #Bezos #DavidAttenborough #DiCaprio #harlequin #JeffBezos #LaurenSánchezBezos #LeonardoDicaprio #TianaAndriamanana #WesSechrest
-
#visualart #photography #Photo #fotografie #fotografia #NoToWar #couleur #colors #tokyoart #newyorkart #londonart #bilbaoart #barcelonaart #montrealart #baselart #ParisArt #berlinart #fictions #poetics #ficciones #poesia #couleur #colors #colores #arlequin #harlequin
https://pablomartinezcalleja.blogspot.com/2026/02/relato-visual-de-un-arlequin-i-v-recit.html -
#visualart #photography #Photo #fotografie #fotografia #NoToWar #couleur #colors #tokyoart #newyorkart #londonart #bilbaoart #barcelonaart #montrealart #baselart #ParisArt #berlinart #fictions #poetics #ficciones #poesia #couleur #colors #colores #arlequin #harlequin
https://pablomartinezcalleja.blogspot.com/2026/02/relato-visual-de-un-arlequin-i-v-recit.html -
#visualart #photography #Photo #fotografie #fotografia #NoToWar #couleur #colors #tokyoart #newyorkart #londonart #bilbaoart #barcelonaart #montrealart #baselart #ParisArt #berlinart #fictions #poetics #ficciones #poesia #couleur #colors #colores #arlequin #harlequin
https://pablomartinezcalleja.blogspot.com/2026/02/relato-visual-de-un-arlequin-i-v-recit.html -
#visualart #photography #Photo #fotografie #fotografia #NoToWar #couleur #colors #tokyoart #newyorkart #londonart #bilbaoart #barcelonaart #montrealart #baselart #ParisArt #berlinart #fictions #poetics #ficciones #poesia #couleur #colors #colores #arlequin #harlequin
https://pablomartinezcalleja.blogspot.com/2026/02/relato-visual-de-un-arlequin-i-v-recit.html -
https://www.europesays.com/ie/617974/ South American frogs are losing their poisonous skin which keeps them safe from predators: Scientists reveal how they could get it back | #AmphibianChytridFungus #ConservationEffortsForFrogs #Éire #FrogExtinction #harlequin #HarlequinFrogs #IE #Ireland #PanamaAmphibianRescueAndConservationProject #parc #Science #ToxicSkin
-
First artfight drawing this year, for KomorebiNugget ! Warhammer 40k fans should recognise this one :>
#artfight #warhammer #40k #w40k #harlequin #solitaire #art #artwork #krita #gaertan #avian #bird #anthro #furry
-
First artfight drawing this year, for KomorebiNugget ! Warhammer 40k fans should recognise this one :>
#artfight #warhammer #40k #w40k #harlequin #solitaire #art #artwork #krita #gaertan #avian #bird #anthro #furry
-
First artfight drawing this year, for KomorebiNugget ! Warhammer 40k fans should recognise this one :>
#artfight #warhammer #40k #w40k #harlequin #solitaire #art #artwork #krita #gaertan #avian #bird #anthro #furry
-
First artfight drawing this year, for KomorebiNugget ! Warhammer 40k fans should recognise this one :>
#artfight #warhammer #40k #w40k #harlequin #solitaire #art #artwork #krita #gaertan #avian #bird #anthro #furry
-
"HARLEQUIN". Mixed media by A.G. (c) 2026. All Rights Reserved. #historiotheque #artoperations #seasonsoftheheart #springtimeoflife #springtimeofjoyfulbeing #cubism #harlequin
-
"HARLEQUIN". Mixed media by A.G. (c) 2026. All Rights Reserved. #historiotheque #artoperations #seasonsoftheheart #springtimeoflife #springtimeofjoyfulbeing #cubism #harlequin
-
"HARLEQUIN". Mixed media by A.G. (c) 2026. All Rights Reserved. #historiotheque #artoperations #seasonsoftheheart #springtimeoflife #springtimeofjoyfulbeing #cubism #harlequin
-
"HARLEQUIN". Mixed media by A.G. (c) 2026. All Rights Reserved. #historiotheque #artoperations #seasonsoftheheart #springtimeoflife #springtimeofjoyfulbeing #cubism #harlequin
-
"HARLEQUIN". Mixed media by A.G. (c) 2026. All Rights Reserved. #historiotheque #artoperations #seasonsoftheheart #springtimeoflife #springtimeofjoyfulbeing #cubism #harlequin
-
In going through some old papers, I ran across these very interesting documents from long ago that I can't seem to find public reference to. They seem to offer some important historical insight about the Dylan language. This is from back when Dylan was called Ralph as a working title. In those days, the still-being-designed Lisp-like language had not yet moved to an infix syntax, and it looked and acted more like Scheme with an object system similar in spirit to CLOS (the Common Lisp Object System).
My understanding is that there were some fairly deliberate choices made to NOT target the Lisp or Scheme community as users, which is part of why the move to infix. I think they wanted to appeal to a disaffected C++ crowd, but ultimately lost out to Java for that bid, and then having left the Lisp user base behind, ended up with a very small community as a result.
But I still think there could be things the Scheme community would want to glean from this snapshot of history.
I've included a scan of an email proposal I got from Dave Moon while he and I were at Symbolics, with his proposal for how to add conditions to the language. Note that Dylan did eventually go public and did have a condition system, so you could also just study that design directly. But what's useful here is to see how all that looked syntactically in a Scheme-like syntax. But, in that regard, I recommend starting by looking at the language itself.
[0] Ralph: A Dynamic Language with Efficient Application Delivery, by Andrew LM Shalit, July 25, 1991.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
In going through some old papers, I ran across these very interesting documents from long ago that I can't seem to find public reference to. They seem to offer some important historical insight about the Dylan language. This is from back when Dylan was called Ralph as a working title. In those days, the still-being-designed Lisp-like language had not yet moved to an infix syntax, and it looked and acted more like Scheme with an object system similar in spirit to CLOS (the Common Lisp Object System).
My understanding is that there were some fairly deliberate choices made to NOT target the Lisp or Scheme community as users, which is part of why the move to infix. I think they wanted to appeal to a disaffected C++ crowd, but ultimately lost out to Java for that bid, and then having left the Lisp user base behind, ended up with a very small community as a result.
But I still think there could be things the Scheme community would want to glean from this snapshot of history.
I've included a scan of an email proposal I got from Dave Moon while he and I were at Symbolics, with his proposal for how to add conditions to the language. Note that Dylan did eventually go public and did have a condition system, so you could also just study that design directly. But what's useful here is to see how all that looked syntactically in a Scheme-like syntax. But, in that regard, I recommend starting by looking at the language itself.
[0] Ralph: A Dynamic Language with Efficient Application Delivery, by Andrew LM Shalit, July 25, 1991.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
In going through some old papers, I ran across these very interesting documents from long ago that I can't seem to find public reference to. They seem to offer some important historical insight about the Dylan language. This is from back when Dylan was called Ralph as a working title. In those days, the still-being-designed Lisp-like language had not yet moved to an infix syntax, and it looked and acted more like Scheme with an object system similar in spirit to CLOS (the Common Lisp Object System).
My understanding is that there were some fairly deliberate choices made to NOT target the Lisp or Scheme community as users, which is part of why the move to infix. I think they wanted to appeal to a disaffected C++ crowd, but ultimately lost out to Java for that bid, and then having left the Lisp user base behind, ended up with a very small community as a result.
But I still think there could be things the Scheme community would want to glean from this snapshot of history.
I've included a scan of an email proposal I got from Dave Moon while he and I were at Symbolics, with his proposal for how to add conditions to the language. Note that Dylan did eventually go public and did have a condition system, so you could also just study that design directly. But what's useful here is to see how all that looked syntactically in a Scheme-like syntax. But, in that regard, I recommend starting by looking at the language itself.
[0] Ralph: A Dynamic Language with Efficient Application Delivery, by Andrew LM Shalit, July 25, 1991.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
In going through some old papers, I ran across these very interesting documents from long ago that I can't seem to find public reference to. They seem to offer some important historical insight about the Dylan language. This is from back when Dylan was called Ralph as a working title. In those days, the still-being-designed Lisp-like language had not yet moved to an infix syntax, and it looked and acted more like Scheme with an object system similar in spirit to CLOS (the Common Lisp Object System).
My understanding is that there were some fairly deliberate choices made to NOT target the Lisp or Scheme community as users, which is part of why the move to infix. I think they wanted to appeal to a disaffected C++ crowd, but ultimately lost out to Java for that bid, and then having left the Lisp user base behind, ended up with a very small community as a result.
But I still think there could be things the Scheme community would want to glean from this snapshot of history.
I've included a scan of an email proposal I got from Dave Moon while he and I were at Symbolics, with his proposal for how to add conditions to the language. Note that Dylan did eventually go public and did have a condition system, so you could also just study that design directly. But what's useful here is to see how all that looked syntactically in a Scheme-like syntax. But, in that regard, I recommend starting by looking at the language itself.
[0] Ralph: A Dynamic Language with Efficient Application Delivery, by Andrew LM Shalit, July 25, 1991.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
In going through some old papers, I ran across these very interesting documents from long ago that I can't seem to find public reference to. They seem to offer some important historical insight about the Dylan language. This is from back when Dylan was called Ralph as a working title. In those days, the still-being-designed Lisp-like language had not yet moved to an infix syntax, and it looked and acted more like Scheme with an object system similar in spirit to CLOS (the Common Lisp Object System).
My understanding is that there were some fairly deliberate choices made to NOT target the Lisp or Scheme community as users, which is part of why the move to infix. I think they wanted to appeal to a disaffected C++ crowd, but ultimately lost out to Java for that bid, and then having left the Lisp user base behind, ended up with a very small community as a result.
But I still think there could be things the Scheme community would want to glean from this snapshot of history.
I've included a scan of an email proposal I got from Dave Moon while he and I were at Symbolics, with his proposal for how to add conditions to the language. Note that Dylan did eventually go public and did have a condition system, so you could also just study that design directly. But what's useful here is to see how all that looked syntactically in a Scheme-like syntax. But, in that regard, I recommend starting by looking at the language itself.
[0] Ralph: A Dynamic Language with Efficient Application Delivery, by Andrew LM Shalit, July 25, 1991.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
#heatedrivalry #gamechangers2 #rachelreid #harlequin #lecture #roman #vo #romancemm #ebook
Shane et Ilya sont les personnages principaux de la série canadienne Heated Rivalry. Jacob Tierney, le créateur de la série, a retranscris assez fidèlement le roman. C'était chouette de retrouver ces deux personnages mais aussi d'avoir plus facilement accès à leurs pensées (ce qui est plus difficile à retranscrir dans une série télé).
-
Episódio 173 – As novas novidades – Parte B
https://retropolis.com.br/2026/04/22/episodio-173-as-novas-novidades-parte-b/
#Podcast #80386 #8086 #8086CPU #Adafruit #AliExpress #Amiga #AppleIIc #Commodore #Commodore64 #CRASHMagazine #EhBASIC #fpga #Harlequin #IbmPc #Intel #Laptop #Lazarustorm #LCD #microdrive #Minimig #MSX #MSX2 #MSXGoauld #MSXMini #Notebook #Omega #OmniDesktop128HQ #OneChipBook #PCBWay #PiStorm #podcast #Retrocomputao #retrogaming #Retrpolis #sinclair #SMX #Sony #Stargate #
-
Episódio 173 – As novas novidades – Parte B
https://retropolis.com.br/2026/04/22/episodio-173-as-novas-novidades-parte-b/
#Podcast #80386 #8086 #8086CPU #Adafruit #AliExpress #Amiga #AppleIIc #Commodore #Commodore64 #CRASHMagazine #EhBASIC #fpga #Harlequin #IbmPc #Intel #Laptop #Lazarustorm #LCD #microdrive #Minimig #MSX #MSX2 #MSXGoauld #MSXMini #Notebook #Omega #OmniDesktop128HQ #OneChipBook #PCBWay #PiStorm #podcast #Retrocomputao #retrogaming #Retrpolis #sinclair #SMX #Sony #Stargate #
-
Episódio 173 – As novas novidades – Parte B
https://retropolis.com.br/2026/04/22/episodio-173-as-novas-novidades-parte-b/
#Podcast #80386 #8086 #8086CPU #Adafruit #AliExpress #Amiga #AppleIIc #Commodore #Commodore64 #CRASHMagazine #EhBASIC #fpga #Harlequin #IbmPc #Intel #Laptop #Lazarustorm #LCD #microdrive #Minimig #MSX #MSX2 #MSXGoauld #MSXMini #Notebook #Omega #OmniDesktop128HQ #OneChipBook #PCBWay #PiStorm #podcast #Retrocomputao #retrogaming #Retrpolis #sinclair #SMX #Sony #Stargate #
