Conversation

Notices

1. Embed this notice
   Pat (mostlypat@mastodon.sdf.org)'s status on Wednesday, 25-Dec-2024 12:36:19 JST Pat

   26 years done, another 26 to go :)

   • Embed this notice
     screwlisp (screwtape@mastodon.sdf.org)'s status on Wednesday, 25-Dec-2024 12:36:18 JST screwlisp

     in reply to

     @mostlypat
     CLIM-USER> (progn (setq *print-circle* t) '#1=("just five more years" . #1#))
     #1=("just five more years" . #1#)
     CLIM-USER> (cdr *)
     #1=("just five more years" . #1#)

     Thanks for dropping by the show! The new year's episode is going to be all the errata for my mistakes in the christmas show ;p

   • Embed this notice
     Pat (mostlypat@mastodon.sdf.org)'s status on Wednesday, 25-Dec-2024 17:53:47 JST Pat

     in reply to

     • screwlisp

     @screwtape Thanks for the show, I'm glad I could finally catch one live, even if it was 1am on Christmas day for me! I'll need to investigate LambdaMOO and CLIM on something other than Termux on my smartphone...

     MOOs seem like quite an interesting programming problem. A lot of different objects dynamically interacting with each other. What you were saying about high-level logic was cool, I wonder if there is a hard mathematical limit to what you can "simulate" in a MOO

   • Embed this notice
     screwlisp (screwtape@mastodon.sdf.org)'s status on Thursday, 26-Dec-2024 04:58:32 JST screwlisp

     in reply to

     @mostlypat
     I think for functional code (functions of functions), in my lisp moo thing I can do forward simulation, but simulating the whole world only works for a very small search space.

     In contrast, sitcalc with occlusion can search through lots and lots of sequences of logical actions to satisfy intents, but it can only really work with first order logic (no functions of functions). So I thought beliefs can be 1st order sitcalc, but the real simulated world can be higher order.

   • Embed this notice
     screwlisp (screwtape@mastodon.sdf.org)'s status on Thursday, 26-Dec-2024 05:01:43 JST screwlisp

     in reply to

     @mostlypat In terms of the real, historical MOOs such as the extant lambdaMOO, while the MOO language is part of the C implementation of lambdaCORE (read *server-hackers in-MOO), the MOO is grown by programming more MOO in MOO. So when you first connect, your player class is $player from 1990, but the-usual player class is sharpc, decades of gradual MOO-language object oriented improvement on top of $player by generations of people.