home.social

#lispygopherclimate — Public Fediverse posts

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

  1. @screwlisp I have Wednesday morning off this week, which means I can attend the #LispyGopherClimate show!

    @jamesendreshowell
  2. @screwlisp I have Wednesday morning off this week, which means I can attend the #LispyGopherClimate show!

    @jamesendreshowell
  3. @screwlisp I have Wednesday morning off this week, which means I can attend the #LispyGopherClimate show!

    @jamesendreshowell
  4. @screwlisp I have Wednesday morning off this week, which means I can attend the #LispyGopherClimate show!

    @jamesendreshowell
  5. Joined the Lispy Gopher Climate crew in Paradise Sushi in LambdaMOO for the first time today (as "radfish") ! I didn't have anything to say but I enjoyed hearing the banter in the restaurant during the show. LambdaMOO (or I guess MOO/MUD in general) is really unique as someone who didn't grow up with text adventures and the like. It's been a great experience so far; thank you @me for the hospitality.

    #LispyGopherClimate #LambdaMOO

  6. Joined the Lispy Gopher Climate crew in Paradise Sushi in LambdaMOO for the first time today (as "radfish") ! I didn't have anything to say but I enjoyed hearing the banter in the restaurant during the show. LambdaMOO (or I guess MOO/MUD in general) is really unique as someone who didn't grow up with text adventures and the like. It's been a great experience so far; thank you @me for the hospitality.

    #LispyGopherClimate #LambdaMOO

  7. Joined the Lispy Gopher Climate crew in Paradise Sushi in LambdaMOO for the first time today (as "radfish") ! I didn't have anything to say but I enjoyed hearing the banter in the restaurant during the show. LambdaMOO (or I guess MOO/MUD in general) is really unique as someone who didn't grow up with text adventures and the like. It's been a great experience so far; thank you @me for the hospitality.

    #LispyGopherClimate #LambdaMOO

  8. Joined the Lispy Gopher Climate crew in Paradise Sushi in LambdaMOO for the first time today (as "radfish") ! I didn't have anything to say but I enjoyed hearing the banter in the restaurant during the show. LambdaMOO (or I guess MOO/MUD in general) is really unique as someone who didn't grow up with text adventures and the like. It's been a great experience so far; thank you @me for the hospitality.

    #LispyGopherClimate #LambdaMOO

  9. Joined the Lispy Gopher Climate crew in Paradise Sushi in LambdaMOO for the first time today (as "radfish") ! I didn't have anything to say but I enjoyed hearing the banter in the restaurant during the show. LambdaMOO (or I guess MOO/MUD in general) is really unique as someone who didn't grow up with text adventures and the like. It's been a great experience so far; thank you @me for the hospitality.

    #LispyGopherClimate #LambdaMOO

  10. I was able to finish reading all of “The Genius of Lisp“ by @cdegroot and the whole book was as good as the free preview (chapter 8). I was able to speed-read through the detailed explanations of concepts I already knew, like tail recursion, garbage collection, the Y-combinator, Currying functions, and so on. But there were parts where I slowed down and read carefully, like the section on the Universal Turing Machine, and some of the details of the IBM-704 system architecture. Also the story of how the first Lisp implementation was created when one of McCarthy’s grad students implemented an M-Expression calculator, this was described in slightly more detail than what I recall McCarthy himself explaining in his 1960 paper — that or I had just forgotten those parts of the story.

    The tone of this book reminds me a lot of popular physics books like Stephen Hawking’s “A Brief History of Time,” which was aimed more at general audiences than professionals. That said, there is a lot to enjoy about this book for professionals like myself as well. There are many good stories about the principals designers of Lisp throughout. The sections on the commercialization of Lisp for the first AI boom of the 1970s and it’s subsequent “AI winter,” were very interesting to read. And if you are a teacher, you might like how some of the concepts in the book are explained.

    And I would definitely recommend this very strongly to 3rd-year high school students, or 1st and 2nd year college students, who are more genuinely curious about how computers work and want to know more than just how to make the next billion dollar app.

    The next #LispyGopherClimate show with @screwlisp I look forward to talking about this book some more.

    #tech #software #Lisp #ProgrammingLanguages #SchemeLang #Scheme #Clojure #Emacs #EmacsLisp #RetroComputing #LispyGopherClimateShow

  11. I was able to finish reading all of “The Genius of Lisp“ by @cdegroot and the whole book was as good as the free preview (chapter 8). I was able to speed-read through the detailed explanations of concepts I already knew, like tail recursion, garbage collection, the Y-combinator, Currying functions, and so on. But there were parts where I slowed down and read carefully, like the section on the Universal Turing Machine, and some of the details of the IBM-704 system architecture. Also the story of how the first Lisp implementation was created when one of McCarthy’s grad students implemented an M-Expression calculator, this was described in slightly more detail than what I recall McCarthy himself explaining in his 1960 paper — that or I had just forgotten those parts of the story.

    The tone of this book reminds me a lot of popular physics books like Stephen Hawking’s “A Brief History of Time,” which was aimed more at general audiences than professionals. That said, there is a lot to enjoy about this book for professionals like myself as well. There are many good stories about the principals designers of Lisp throughout. The sections on the commercialization of Lisp for the first AI boom of the 1970s and it’s subsequent “AI winter,” were very interesting to read. And if you are a teacher, you might like how some of the concepts in the book are explained.

    And I would definitely recommend this very strongly to 3rd-year high school students, or 1st and 2nd year college students, who are more genuinely curious about how computers work and want to know more than just how to make the next billion dollar app.

    The next #LispyGopherClimate show with @screwlisp I look forward to talking about this book some more.

    #tech #software #Lisp #ProgrammingLanguages #SchemeLang #Scheme #Clojure #Emacs #EmacsLisp #RetroComputing #LispyGopherClimateShow

  12. I was able to finish reading all of “The Genius of Lisp“ by @cdegroot and the whole book was as good as the free preview (chapter 8). I was able to speed-read through the detailed explanations of concepts I already knew, like tail recursion, garbage collection, the Y-combinator, Currying functions, and so on. But there were parts where I slowed down and read carefully, like the section on the Universal Turing Machine, and some of the details of the IBM-704 system architecture. Also the story of how the first Lisp implementation was created when one of McCarthy’s grad students implemented an M-Expression calculator, this was described in slightly more detail than what I recall McCarthy himself explaining in his 1960 paper — that or I had just forgotten those parts of the story.

    The tone of this book reminds me a lot of popular physics books like Stephen Hawking’s “A Brief History of Time,” which was aimed more at general audiences than professionals. That said, there is a lot to enjoy about this book for professionals like myself as well. There are many good stories about the principals designers of Lisp throughout. The sections on the commercialization of Lisp for the first AI boom of the 1970s and it’s subsequent “AI winter,” were very interesting to read. And if you are a teacher, you might like how some of the concepts in the book are explained.

    And I would definitely recommend this very strongly to 3rd-year high school students, or 1st and 2nd year college students, who are more genuinely curious about how computers work and want to know more than just how to make the next billion dollar app.

    The next #LispyGopherClimate show with @screwlisp I look forward to talking about this book some more.

    #tech #software #Lisp #ProgrammingLanguages #SchemeLang #Scheme #Clojure #Emacs #EmacsLisp #RetroComputing #LispyGopherClimateShow

  13. I was able to finish reading all of “The Genius of Lisp“ by @cdegroot and the whole book was as good as the free preview (chapter 8). I was able to speed-read through the detailed explanations of concepts I already knew, like tail recursion, garbage collection, the Y-combinator, Currying functions, and so on. But there were parts where I slowed down and read carefully, like the section on the Universal Turing Machine, and some of the details of the IBM-704 system architecture. Also the story of how the first Lisp implementation was created when one of McCarthy’s grad students implemented an M-Expression calculator, this was described in slightly more detail than what I recall McCarthy himself explaining in his 1960 paper — that or I had just forgotten those parts of the story.

    The tone of this book reminds me a lot of popular physics books like Stephen Hawking’s “A Brief History of Time,” which was aimed more at general audiences than professionals. That said, there is a lot to enjoy about this book for professionals like myself as well. There are many good stories about the principals designers of Lisp throughout. The sections on the commercialization of Lisp for the first AI boom of the 1970s and it’s subsequent “AI winter,” were very interesting to read. And if you are a teacher, you might like how some of the concepts in the book are explained.

    And I would definitely recommend this very strongly to 3rd-year high school students, or 1st and 2nd year college students, who are more genuinely curious about how computers work and want to know more than just how to make the next billion dollar app.

    The next #LispyGopherClimate show with @screwlisp I look forward to talking about this book some more.

    #tech #software #Lisp #ProgrammingLanguages #SchemeLang #Scheme #Clojure #Emacs #EmacsLisp #RetroComputing #LispyGopherClimateShow

  14. @screwlisp @kentpitman I’m just reading up on the MIT-Scheme condition system. Recent efforts to standardize this are defined in SRFI-255: “Restarting conditions”.

    An older standards condition systems in Scheme was defined in SRFI-35: “Conditions”. And #Guile users can use the Guile implementation of SRFI-35 to make use of it.

    I wish I had known about this two weeks ago when we first started talking about it on the #LispyGopherClimate show, but better late than never, I guess.

    #tech #software #Lisp #CommonLisp #Scheme #SchemeLang #R7RS #MITScheme #Guile #GuileScheme

  15. @screwlisp @kentpitman I’m just reading up on the MIT-Scheme condition system. Recent efforts to standardize this are defined in SRFI-255: “Restarting conditions”.

    An older standards condition systems in Scheme was defined in SRFI-35: “Conditions”. And #Guile users can use the Guile implementation of SRFI-35 to make use of it.

    I wish I had known about this two weeks ago when we first started talking about it on the #LispyGopherClimate show, but better late than never, I guess.

    #tech #software #Lisp #CommonLisp #Scheme #SchemeLang #R7RS #MITScheme #Guile #GuileScheme

  16. @screwlisp @kentpitman I’m just reading up on the MIT-Scheme condition system. Recent efforts to standardize this are defined in SRFI-255: “Restarting conditions”.

    An older standards condition systems in Scheme was defined in SRFI-35: “Conditions”. And #Guile users can use the Guile implementation of SRFI-35 to make use of it.

    I wish I had known about this two weeks ago when we first started talking about it on the #LispyGopherClimate show, but better late than never, I guess.

    #tech #software #Lisp #CommonLisp #Scheme #SchemeLang #R7RS #MITScheme #Guile #GuileScheme

  17. @screwlisp @kentpitman I’m just reading up on the MIT-Scheme condition system. Recent efforts to standardize this are defined in SRFI-255: “Restarting conditions”.

    An older standards condition systems in Scheme was defined in SRFI-35: “Conditions”. And #Guile users can use the Guile implementation of SRFI-35 to make use of it.

    I wish I had known about this two weeks ago when we first started talking about it on the #LispyGopherClimate show, but better late than never, I guess.

    #tech #software #Lisp #CommonLisp #Scheme #SchemeLang #R7RS #MITScheme #Guile #GuileScheme

  18. @screwlisp @kentpitman regarding the discussion we had after the #LispyGopherClimate show ended, MiniKanren is logic programming language embedded in Scheme (sort-of like a Prolog implemented in Scheme and coded with S-expressions), and you can use machine leaning methods like neural networks to guide the search tree of the goal solver mechanism. This paper is an example of what I was talking about.

    Even before LLMs were invented, MiniKanren was able to do program synthesis using purely symbolic logic. They developed a prototype called Barliman where you would provide example input->output pairs as constraints, and using a constraint solver, could generalize those examples to a function that generates any output for any input. As a simple example, you could give it the following input-output pairs:

    1. () -> ()
    2. (a) () -> (a)
    3. () (a) -> (a)
    4. (a) (a) -> (a a)

    …and the constraint solver could determine that you are trying to implement the append function for lists and write the code automatically — without LLMs, using purely symbolic logic.

    As you might expect, the solver could be very slow, or even diverge (never returning an answer). The paper I mentioned above talks about using neural networks to try to guide the constraint solver to improve the performance and usefulness of the results returned by the solver.

    Now imagine applying this technique to other domains besides code generation or optimization, for example, auto-completion, or cache pre-fetching, and building it into a programmable computing environment like Emacs. You could have a tool like “Cursor,” but instead of using LLMs, it uses classical computing and constraint solvers, while taking a fraction of the amount of energy that LLMs use.

    #tech #software #AI #LLM #MachineLearning #NeuralNetwork #ConstraintLogic #ConstraintSolver #LogicProgramming #Prolog #MiniKanren #Emacs #Lisp #Scheme #SchemeLang #ProgramSynthesis

  19. @screwlisp @kentpitman regarding the discussion we had after the #LispyGopherClimate show ended, MiniKanren is logic programming language embedded in Scheme (sort-of like a Prolog implemented in Scheme and coded with S-expressions), and you can use machine leaning methods like neural networks to guide the search tree of the goal solver mechanism. This paper is an example of what I was talking about.

    Even before LLMs were invented, MiniKanren was able to do program synthesis using purely symbolic logic. They developed a prototype called Barliman where you would provide example input->output pairs as constraints, and using a constraint solver, could generalize those examples to a function that generates any output for any input. As a simple example, you could give it the following input-output pairs:

    1. () -> ()
    2. (a) () -> (a)
    3. () (a) -> (a)
    4. (a) (a) -> (a a)

    …and the constraint solver could determine that you are trying to implement the append function for lists and write the code automatically — without LLMs, using purely symbolic logic.

    As you might expect, the solver could be very slow, or even diverge (never returning an answer). The paper I mentioned above talks about using neural networks to try to guide the constraint solver to improve the performance and usefulness of the results returned by the solver.

    Now imagine applying this technique to other domains besides code generation or optimization, for example, auto-completion, or cache pre-fetching, and building it into a programmable computing environment like Emacs. You could have a tool like “Cursor,” but instead of using LLMs, it uses classical computing and constraint solvers, while taking a fraction of the amount of energy that LLMs use.

    #tech #software #AI #LLM #MachineLearning #NeuralNetwork #ConstraintLogic #ConstraintSolver #LogicProgramming #Prolog #MiniKanren #Emacs #Lisp #Scheme #SchemeLang #ProgramSynthesis

  20. @screwlisp @kentpitman regarding the discussion we had after the #LispyGopherClimate show ended, MiniKanren is logic programming language embedded in Scheme (sort-of like a Prolog implemented in Scheme and coded with S-expressions), and you can use machine leaning methods like neural networks to guide the search tree of the goal solver mechanism. This paper is an example of what I was talking about.

    Even before LLMs were invented, MiniKanren was able to do program synthesis using purely symbolic logic. They developed a prototype called Barliman where you would provide example input->output pairs as constraints, and using a constraint solver, could generalize those examples to a function that generates any output for any input. As a simple example, you could give it the following input-output pairs:

    1. () -> ()
    2. (a) () -> (a)
    3. () (a) -> (a)
    4. (a) (a) -> (a a)

    …and the constraint solver could determine that you are trying to implement the append function for lists and write the code automatically — without LLMs, using purely symbolic logic.

    As you might expect, the solver could be very slow, or even diverge (never returning an answer). The paper I mentioned above talks about using neural networks to try to guide the constraint solver to improve the performance and usefulness of the results returned by the solver.

    Now imagine applying this technique to other domains besides code generation or optimization, for example, auto-completion, or cache pre-fetching, and building it into a programmable computing environment like Emacs. You could have a tool like “Cursor,” but instead of using LLMs, it uses classical computing and constraint solvers, while taking a fraction of the amount of energy that LLMs use.

    #tech #software #AI #LLM #MachineLearning #NeuralNetwork #ConstraintLogic #ConstraintSolver #LogicProgramming #Prolog #MiniKanren #Emacs #Lisp #Scheme #SchemeLang #ProgramSynthesis

  21. @screwlisp @kentpitman regarding the discussion we had after the #LispyGopherClimate show ended, MiniKanren is logic programming language embedded in Scheme (sort-of like a Prolog implemented in Scheme and coded with S-expressions), and you can use machine leaning methods like neural networks to guide the search tree of the goal solver mechanism. This paper is an example of what I was talking about.

    Even before LLMs were invented, MiniKanren was able to do program synthesis using purely symbolic logic. They developed a prototype called Barliman where you would provide example input->output pairs as constraints, and using a constraint solver, could generalize those examples to a function that generates any output for any input. As a simple example, you could give it the following input-output pairs:

    1. () -> ()
    2. (a) () -> (a)
    3. () (a) -> (a)
    4. (a) (a) -> (a a)

    …and the constraint solver could determine that you are trying to implement the append function for lists and write the code automatically — without LLMs, using purely symbolic logic.

    As you might expect, the solver could be very slow, or even diverge (never returning an answer). The paper I mentioned above talks about using neural networks to try to guide the constraint solver to improve the performance and usefulness of the results returned by the solver.

    Now imagine applying this technique to other domains besides code generation or optimization, for example, auto-completion, or cache pre-fetching, and building it into a programmable computing environment like Emacs. You could have a tool like “Cursor,” but instead of using LLMs, it uses classical computing and constraint solvers, while taking a fraction of the amount of energy that LLMs use.

    #tech #software #AI #LLM #MachineLearning #NeuralNetwork #ConstraintLogic #ConstraintSolver #LogicProgramming #Prolog #MiniKanren #Emacs #Lisp #Scheme #SchemeLang #ProgramSynthesis

  22. Lispy Gopher Show

    Don't miss the @lambdacalculus giving us a #preview of the #HOPE and #PhreakNIC talks on the #lispyGopherClimate tomorrow 23 hours from this toot! Deliver questions and comments live as always.

    gamerplus.org/@screwlisp/11485

    #lisp #programming

  23. Morning all! I was supposed to join @screwlisp for their Lispy Gopher Show podcast yesterday but time zone differences meant I had to send a recording instead which they discussed with questions from their mud (yep, it’s a geeky community) :)

    I touched on the history of computing, the current challenge to our human rights and democracy with technofascism, and how the Small Web is one attempt to safeguard our freedoms by creating a peer-to-peer web owned and controlled by everyday people who use technology as an everyday thing. (And the role of design and simplicity in making that possible.)

    Anyway, here’s the full recording I sent (as it skips around a bit in the show):

    vimeo.com/1079992713

    And here’s the recording of the show itself with commentary by screwlisp and the community:

    communitymedia.video/w/kTjUgHS

    Thanks for having me on and sorry I couldn’t be there in person.

    💕

    #LispyGopherShow #lispyGopherClimate #screwlisp #podcast #SmallWeb #SmallTech #Kitten #Domain #Place #peerToPeer #web #HumanRights #Democracy #design

  24. Heard this song on #anonradio https://anonradio.net/ right after the #LispyGopherClimate Technology Live Podcast Radio Show hosted by @screwtape aka #screwlisp and I find it a pleasant listen.

    https://www.youtube.com/watch?v=yczUMaFFCmA

    Kaneko Ayano - Kamitsukitai / カネコアヤノ - かみつきたい - LIVE 2020 + Lyrics

    #Kamitsukitai
    #KanekoAyano
    #かみつきたい
    #カネコアヤ
  25. #LispyGopherClimate #lisp #ai #peertube
    communitymedia.video/w/7KpDL8d

    @kentpitman #haiku

    Resurrected Sandewall's #softwareIndividuals from 2014.

    This episode is dedicated to general purpose interaction in the software individual / #CAISOR paradigm.

    Next will be porting the dynamicwindows zetalisp zwei to McCLIM #commonlisp.

    @prahou #unix_surrealism next #openbsd release art??

    Also @pesco and @dougmerritt on IPE '84

    co guest and join in on #lambdaMOO as always!

    @mdhughes @nosrednayduj @sacha

  26. #lispyGopherClimate #technology #lisp #podcast #tomorrow

    Okay, tomorrow I'm just going to present where I kinda suddenly got to this past week with Sandewall's #Leonardo #SoftwareIndividuals, which is quite far really.

    These are basically the most advanced point cognitive good-old-fashioned-a-i got to in my opinion, concluding with Sandewall's 2 unpublished open access books in 2014. #gofai #ai #cai

    codeberg.org/tfw/pawn-75

    If anyone wants to join the call for whatever topic, let me know.

  27. The #LispyGopherClimate #weekly #tech #podcast for 2025-04-02

    Listen at: https://archives.anonradio.net/202504020000_screwtape.mp3

    This week we will talk about the Unix Philosophy and how it compares and contrasts with whatever one might call the “Emacs Philosophy.”

    The impetus for the discussion is a series of blog posts by @ramin_hal9001 called “Emacs fulfills the UNIX Philosophy”:

    …as well as a fascinating discussion that took place over this past week on ActivityPub on the topic of the Unix philosophy and history of Lisp on Unix in which some very knowledgeable people have contributed anecdotes and facts.

    #technology #programming #SoftwareEngineering #RetroComputing #lisp #r7rs #SchemeLang #UnixPhilosophy

    This weeks #ClimateCrisis #haiku by @kentpitman
    within each of us
    our loved ones, in tiny form,
    caring's innate yield
        company at a distance
        legacy in case of loss

    #senryu #poem #ShortPoem #SmallPoem #SmallPoems

  28. #lispyGopherClimate #live #programming #lisp #podcast
    #archived
    archives.anonradio.net/2025031
    I'll interviews next week everyone, thanks for humoring me this week

    @kentpitman #climateCrisis #haiku

    I'm fasting for some edicalmay rocedurepay so "low energy hangout" please.
    I will throw you some primary journalism on the US/NZ/UK #ai #toTheHilt policy as it is existing now in practice.

    Then I want to talk about programming that matters and why running the same llm again (faster) doesn't matter.

  29. #lispyGopherClimate #live #programming #lisp #podcast
    #archived
    archives.anonradio.net/2025031
    I'll interviews next week everyone, thanks for humoring me this week

    @kentpitman #climateCrisis #haiku

    I'm fasting for some edicalmay rocedurepay so "low energy hangout" please.
    I will throw you some primary journalism on the US/NZ/UK #ai #toTheHilt policy as it is existing now in practice.

    Then I want to talk about programming that matters and why running the same llm again (faster) doesn't matter.

  30. #lispyGopherClimate #live #programming #lisp #podcast
    #archived
    archives.anonradio.net/2025031
    I'll interviews next week everyone, thanks for humoring me this week

    @kentpitman #climateCrisis #haiku

    I'm fasting for some edicalmay rocedurepay so "low energy hangout" please.
    I will throw you some primary journalism on the US/NZ/UK #ai #toTheHilt policy as it is existing now in practice.

    Then I want to talk about programming that matters and why running the same llm again (faster) doesn't matter.

  31. #lispyGopherClimate #live #programming #lisp #podcast
    #archived
    archives.anonradio.net/2025031
    I'll interviews next week everyone, thanks for humoring me this week

    @kentpitman #climateCrisis #haiku

    I'm fasting for some edicalmay rocedurepay so "low energy hangout" please.
    I will throw you some primary journalism on the US/NZ/UK #ai #toTheHilt policy as it is existing now in practice.

    Then I want to talk about programming that matters and why running the same llm again (faster) doesn't matter.

  32. #lispyGopherClimate #live #programming #lisp #podcast
    #archived
    archives.anonradio.net/2025031
    I'll interviews next week everyone, thanks for humoring me this week

    @kentpitman #climateCrisis #haiku

    I'm fasting for some edicalmay rocedurepay so "low energy hangout" please.
    I will throw you some primary journalism on the US/NZ/UK #ai #toTheHilt policy as it is existing now in practice.

    Then I want to talk about programming that matters and why running the same llm again (faster) doesn't matter.