home.social

#harlequin — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #harlequin, aggregated by home.social.

  1. 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.
    nhplace.com/kent/History/dylan

    [1] Ralph Conditions (part 1 of 2)
    nhplace.com/kent/History/dylan

    [2] Ralph Conditions (part 2 of 2)
    nhplace.com/kent/History/dylan

    cc @sigue @ramin_hal9001 @screwlisp

    #DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject

  2. 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.
    nhplace.com/kent/History/dylan

    [1] Ralph Conditions (part 1 of 2)
    nhplace.com/kent/History/dylan

    [2] Ralph Conditions (part 2 of 2)
    nhplace.com/kent/History/dylan

    cc @sigue @ramin_hal9001 @screwlisp

    #DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject

  3. 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.
    nhplace.com/kent/History/dylan

    [1] Ralph Conditions (part 1 of 2)
    nhplace.com/kent/History/dylan

    [2] Ralph Conditions (part 2 of 2)
    nhplace.com/kent/History/dylan

    cc @sigue @ramin_hal9001 @screwlisp

    #DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject

  4. 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.
    nhplace.com/kent/History/dylan

    [1] Ralph Conditions (part 1 of 2)
    nhplace.com/kent/History/dylan

    [2] Ralph Conditions (part 2 of 2)
    nhplace.com/kent/History/dylan

    cc @sigue @ramin_hal9001 @screwlisp

    #DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject

  5. 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.
    nhplace.com/kent/History/dylan

    [1] Ralph Conditions (part 1 of 2)
    nhplace.com/kent/History/dylan

    [2] Ralph Conditions (part 2 of 2)
    nhplace.com/kent/History/dylan

    cc @sigue @ramin_hal9001 @screwlisp

    #DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject

  6. #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é).

  7. Harlequin is Launching Romance Titles into Mobile-First Serialized Video

    The collaboration comes at a time when short-form serialized video is rapidly emerging as a new global entertainment format, with growing demand for high-frequency, mobile-first storytelling.
    The post Harlequin is Launching Romance Titles into Mobile-First Serialized Video first appeared on Good e-Reader.
    goodereader.com/blog/digital-p

    #dashverse #Harlequin #microdramas

  8. His Girl Friday "There has only ever been one man for young Danetta Marist . . . but he's the one she can never have." Sale: $7.99 to $0.99 by Diana Palmer Rating: 4.4/5 (683 Reviews) #Romance #WorkplaceRomance #SmallTown #Harlequin #BeachRead #Books #BookSky

    His Girl Friday

  9. I’m participating in a miniature exchange on a 40K podcast discord. By luck, my draw is just beginning to collect Eldar, and one of his requests was a psyker.

    As it happens, I have an older farseer sculpt that was unassembled. I already own three painted ones, so this extra has been sitting in a box for some time.

    But as a bonus I think I’ll send a Shadowseer and a Harlequin, since I also have extras of the old metals lying around.

    I’m excited.

    #40k #WH40k #Painting #Eldar #Harlequin

  10. The Future of Translation: AI and the Greater Good

    Two stories this week highlight how AI is impacting the role of translators and what that may mean for the future of translation in publishing.
    The post The Future of Translation: AI and the Greater Good appeared first on Publishing Perspectives.
    publishingperspectives.com/202

    #AI #ATLF #AuthorizedBooksofJapan #France #Harlequin

  11. Awww these two are to shy to share their routine with us... It's ok babies, you can wait until the rest are done <3 

    Harlequin stream commission done for Marlow and Devon!!

    #babyfur #babyfurart #clowncore #harlequin

  12. INKTOBER Día 12 #shredded

    Pues hice a mi querida amiga Roky, cuando trabaja en @lanarizroja #lanarizroja y revienta cosas con su fuerza incontrolable. Y la imagino siempre como el clon de Stan de South Park, diciendo "todo rompo, todo jodo, eso rompo, eso jodo".

    #inktober2025 #inktober2025shredded #art #mastoart #fediart #circus #illustration #doodle #sketch #drawing #juggler #jester #harlequin #tempvsfrangit

  13. Consider that just like many Speccy alike are out there still working with minimal repairs after 43 years (38-43 years varying depending on the model), one of Superfo's (Harlequin and others) that you buy today based on discrete components could comparably last until around the year 2065.

    #ZXSpectrum #Spectrum #Speccy #Harlequin #retrocomputing #retrofuture

  14. In essence, you’d have a hybrid machine:

    • Electronic control from retrocomputing hardware.

    • Symbolic storage in textile knots (khipus).

    • Cultural continuity with both Jacquard and pre-Columbian computing.

    Tried and true. At least the last 500 years or so.

    #permacomputing #retrocomputing #rc2014 #harlequin #ZxSpectrum

  15. A Harlequin or RC2014-based Khipu-weaving symbolic persistence device would do three things at once:

    #permacomputing #retrocomputing #rc2014 #harlequin #ZXSpectrum

  16. Going ready for an apocalypse sized game on Saturday.

    My army consists of:

    4 mounted
    4 vehicles
    4 monsters
    85 infantry

    Harlequins and Wraiths all the way.

    #40k #WH40k #Warhammer40k
    #Eldar #Harlequin #Wraithguard

  17. Getting ready for an apocalypse battle next weekend. I recently got some used Eldar models but some needed to be equipped. Luckily I keep all my spare bits. One is getting a sword from the avatar kit, for extra fun.

    Going have a lot of wraiths and harlequins on the table.

    #40k #WH40k #Warhammer40k #Eldar #Harlequins #Wraithlord #Harlequin

  18. It's February 2 so it's yet time to once again repeat an encore of our commedia dell'arte short "The Harlequin's Shadow"!

    Happy Groundhog's Day, everyone!

    #CommediaDellArte #Commedia #Improv #Improvisation #Theater #Harlequin #CommediaTok #GroundhogDay #GroundhogsDay

  19. It's only taken me 30 years but I finally got around to reading the original version of the novel, #Inquisitor, by Ian Watson. I found it to be a decent enough adventure story with plenty of that early #RogueTrader weirdness that I enjoy more than recent #Warhammer40000 stuff.

    Time to move on to its sequel, #Harlequin.

    #Warhammer #Warhammer40k #WH40k #Books #Reading #Reading2025

  20. 𝗡𝗮𝘁𝗮𝗰𝗵𝗮 𝗛𝗮𝗿𝗹𝗲𝗾𝘂𝗶𝗻 𝗸𝗲𝗲𝗿𝘁 𝗱𝗲𝗳𝗶𝗻𝗶𝘁𝗶𝗲𝗳 𝗻𝗶𝗲𝘁 𝘁𝗲𝗿𝘂𝗴 𝗶𝗻 𝗦𝗵𝗼𝘄𝗻𝗶𝗲𝘂𝘄𝘀

    Advocaat Natacha Harlequin zal definitief niet meer te zien zijn als expert in het programma Shownieuws. Een woordvoerder van Talpa heeft donderdag een bericht hierover van De Telegraaf bevestigd.

    rtl.nl/boulevard/artikel/54837

    #Natacha #Harlequin #Shownieuws

  21. 𝗡𝗮𝘁𝗮𝗰𝗵𝗮 𝗛𝗮𝗿𝗹𝗲𝗾𝘂𝗶𝗻 𝗸𝗲𝗲𝗿𝘁 𝗱𝗲𝗳𝗶𝗻𝗶𝘁𝗶𝗲𝗳 𝗻𝗶𝗲𝘁 𝘁𝗲𝗿𝘂𝗴 𝗶𝗻 𝗦𝗵𝗼𝘄𝗻𝗶𝗲𝘂𝘄𝘀

    Advocaat Natacha Harlequin zal definitief niet meer te zien zijn als expert in het programma Shownieuws. Een woordvoerder van Talpa heeft donderdag een bericht hierover van De Telegraaf bevestigd.

    rtl.nl/boulevard/artikel/54837

    #Natacha #Harlequin #Shownieuws

  22. 𝗡𝗮𝘁𝗮𝗰𝗵𝗮 𝗛𝗮𝗿𝗹𝗲𝗾𝘂𝗶𝗻 𝗸𝗲𝗲𝗿𝘁 𝗱𝗲𝗳𝗶𝗻𝗶𝘁𝗶𝗲𝗳 𝗻𝗶𝗲𝘁 𝘁𝗲𝗿𝘂𝗴 𝗶𝗻 𝗦𝗵𝗼𝘄𝗻𝗶𝗲𝘂𝘄𝘀

    Advocaat Natacha Harlequin zal definitief niet meer te zien zijn als expert in het programma Shownieuws. Een woordvoerder van Talpa heeft donderdag een bericht hierover van De Telegraaf bevestigd.

    rtl.nl/boulevard/artikel/54837

    #Natacha #Harlequin #Shownieuws

  23. 𝗡𝗮𝘁𝗮𝗰𝗵𝗮 𝗛𝗮𝗿𝗹𝗲𝗾𝘂𝗶𝗻 𝗸𝗲𝗲𝗿𝘁 𝗱𝗲𝗳𝗶𝗻𝗶𝘁𝗶𝗲𝗳 𝗻𝗶𝗲𝘁 𝘁𝗲𝗿𝘂𝗴 𝗶𝗻 𝗦𝗵𝗼𝘄𝗻𝗶𝗲𝘂𝘄𝘀

    Advocaat Natacha Harlequin zal definitief niet meer te zien zijn als expert in het programma Shownieuws. Een woordvoerder van Talpa heeft donderdag een bericht hierover van De Telegraaf bevestigd.

    rtl.nl/boulevard/artikel/54837

    #Natacha #Harlequin #Shownieuws

  24. Forget Hogwarts Houses,
    what’s your specific Clown Club? 🤡🎪✨

    Riso printed clowns for everyone!
    _
    #Clown #art #jester #harlequin #pierrot #clownCore #risoprint

  25. been feeling really frazzled lately, just wanted to draw my objecthead in some harlequin-y outfits and some brainless chibis for fun
    --
    #ctangleart #MastoArt #CreativeToots #DigitalArt #harlequin #objecthead #QueerArtist #art #artist