#guile — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #guile, aggregated by home.social.
-
-
-
-
-
-
man, #guile #scheme is v cool, v v good.
(but also, i really really struggle with the absensce of nil punning. instead of nil everywhere have '(), \#f, and the dreaded \#<unspecified>. why on earth would i want my when clause to return the latter when it could just return nil? i can't fathom it.)
e.g. this bit of the manual i find glaringly, demonstrably false:
"When you go to write an ‘if’ without an alternate (a “one-armed ‘if’”), part of what you are expressing is that you don’t care about the return value (or values) of the expression."
but guile v cool, v v good.
(now i'm gonna turn into one of those folks dreaming about guile emacs, coz it if worked out you'd imaging writing all your extensions and packages and hacks in this elegant motherfucker of a lisp...)
-
man, #guile #scheme is v cool, v v good.
(but also, i really really struggle with the absensce of nil punning. instead of nil everywhere have '(), \#f, and the dreaded \#<unspecified>. why on earth would i want my when clause to return the latter when it could just return nil? i can't fathom it.)
e.g. this bit of the manual i find glaringly, demonstrably false:
"When you go to write an ‘if’ without an alternate (a “one-armed ‘if’”), part of what you are expressing is that you don’t care about the return value (or values) of the expression."
but guile v cool, v v good.
(now i'm gonna turn into one of those folks dreaming about guile emacs, coz it if worked out you'd imaging writing all your extensions and packages and hacks in this elegant motherfucker of a lisp...)
-
man, #guile #scheme is v cool, v v good.
(but also, i really really struggle with the absensce of nil punning. instead of nil everywhere have '(), \#f, and the dreaded \#<unspecified>. why on earth would i want my when clause to return the latter when it could just return nil? i can't fathom it.)
e.g. this bit of the manual i find glaringly, demonstrably false:
"When you go to write an ‘if’ without an alternate (a “one-armed ‘if’”), part of what you are expressing is that you don’t care about the return value (or values) of the expression."
but guile v cool, v v good.
(now i'm gonna turn into one of those folks dreaming about guile emacs, coz it if worked out you'd imaging writing all your extensions and packages and hacks in this elegant motherfucker of a lisp...)
-
man, #guile #scheme is v cool, v v good.
(but also, i really really struggle with the absensce of nil punning. instead of nil everywhere have '(), \#f, and the dreaded \#<unspecified>. why on earth would i want my when clause to return the latter when it could just return nil? i can't fathom it.)
e.g. this bit of the manual i find glaringly, demonstrably false:
"When you go to write an ‘if’ without an alternate (a “one-armed ‘if’”), part of what you are expressing is that you don’t care about the return value (or values) of the expression."
but guile v cool, v v good.
(now i'm gonna turn into one of those folks dreaming about guile emacs, coz it if worked out you'd imaging writing all your extensions and packages and hacks in this elegant motherfucker of a lisp...)
-
man, #guile #scheme is v cool, v v good.
(but also, i really really struggle with the absensce of nil punning. instead of nil everywhere have '(), \#f, and the dreaded \#<unspecified>. why on earth would i want my when clause to return the latter when it could just return nil? i can't fathom it.)
e.g. this bit of the manual i find glaringly, demonstrably false:
"When you go to write an ‘if’ without an alternate (a “one-armed ‘if’”), part of what you are expressing is that you don’t care about the return value (or values) of the expression."
but guile v cool, v v good.
(now i'm gonna turn into one of those folks dreaming about guile emacs, coz it if worked out you'd imaging writing all your extensions and packages and hacks in this elegant motherfucker of a lisp...)
-
Command line argument processing is always going to be a messy business, being at the human-machine interface. Guile software developers have a plethora of tools available to address the problem, but usually with some outstanding issue or other. Here is my take on the matter in the context of #mcron.
-
Command line argument processing is always going to be a messy business, being at the human-machine interface. Guile software developers have a plethora of tools available to address the problem, but usually with some outstanding issue or other. Here is my take on the matter in the context of #mcron.
-
Command line argument processing is always going to be a messy business, being at the human-machine interface. Guile software developers have a plethora of tools available to address the problem, but usually with some outstanding issue or other. Here is my take on the matter in the context of #mcron.
-
Command line argument processing is always going to be a messy business, being at the human-machine interface. Guile software developers have a plethora of tools available to address the problem, but usually with some outstanding issue or other. Here is my take on the matter in the context of #mcron.
-
Command line argument processing is always going to be a messy business, being at the human-machine interface. Guile software developers have a plethora of tools available to address the problem, but usually with some outstanding issue or other. Here is my take on the matter in the context of #mcron.
-
This recent thread;
https://mas.to/@acallegaro/116515233665083041
inspired an idea that's been bubbling around in my head for a while. I simply added an aggregator for RSS/Atom planets to my Haunt-based site.
Here is the result: https://lovergine.com/planet/
Not bad, isn't it? The list of feeds is here:
https://lovergine.com/planet/sources.html
And thanks to Ray Miller @ray for https://codeberg.org/guix/planet-guix/, where I shamelessly stole some ideas...
PS: just added a daily generation.
-
This recent thread;
https://mas.to/@acallegaro/116515233665083041
inspired an idea that's been bubbling around in my head for a while. I simply added an aggregator for RSS/Atom planets to my Haunt-based site.
Here is the result: https://lovergine.com/planet/
Not bad, isn't it? The list of feeds is here:
https://lovergine.com/planet/sources.html
And thanks to Ray Miller @ray for https://codeberg.org/guix/planet-guix/, where I shamelessly stole some ideas...
PS: just added a daily generation.
-
This recent thread;
https://mas.to/@acallegaro/116515233665083041
inspired an idea that's been bubbling around in my head for a while. I simply added an aggregator for RSS/Atom planets to my Haunt-based site.
Here is the result: https://lovergine.com/planet/
Not bad, isn't it? The list of feeds is here:
https://lovergine.com/planet/sources.html
And thanks to Ray Miller @ray for https://codeberg.org/guix/planet-guix/, where I shamelessly stole some ideas...
PS: just added a daily generation.
-
This recent thread;
https://mas.to/@acallegaro/116515233665083041
inspired an idea that's been bubbling around in my head for a while. I simply added an aggregator for RSS/Atom planets to my Haunt-based site.
Here is the result: https://lovergine.com/planet/
Not bad, isn't it? The list of feeds is here:
https://lovergine.com/planet/sources.html
And thanks to Ray Miller @ray for https://codeberg.org/guix/planet-guix/, where I shamelessly stole some ideas...
PS: just added a daily generation.
-
This recent thread;
https://mas.to/@acallegaro/116515233665083041
inspired an idea that's been bubbling around in my head for a while. I simply added an aggregator for RSS/Atom planets to my Haunt-based site.
Here is the result: https://lovergine.com/planet/
Not bad, isn't it? The list of feeds is here:
https://lovergine.com/planet/sources.html
And thanks to Ray Miller @ray for https://codeberg.org/guix/planet-guix/, where I shamelessly stole some ideas...
PS: just added a daily generation.
-
Published some of the code that I'm eventually going to turn into physics simulations on my website (once I figure out Hoot). Right now it's some physics functions (and the corresponding math) in Scheme.
-
Published some of the code that I'm eventually going to turn into physics simulations on my website (once I figure out Hoot). Right now it's some physics functions (and the corresponding math) in Scheme.
-
Published some of the code that I'm eventually going to turn into physics simulations on my website (once I figure out Hoot). Right now it's some physics functions (and the corresponding math) in Scheme.
-
Published some of the code that I'm eventually going to turn into physics simulations on my website (once I figure out Hoot). Right now it's some physics functions (and the corresponding math) in Scheme.
-
Published some of the code that I'm eventually going to turn into physics simulations on my website (once I figure out Hoot). Right now it's some physics functions (and the corresponding math) in Scheme.
-
#wisp 1.0.13 and wisp-mode 0.4.1 released.
wisp 1.0.13 (2026-05-04): https://hg.sr.ht/~arnebab/wisp/rev/v1.0.13
- add r7rs benchmark graph example with split geometric std
- fix: wisp.py missed escaping \ — thanks to leah2! (scheme IRC)
- may the 4th be with youwisp-mode 0.4.1 (2025-11-09): https://hg.sr.ht/~arnebab/wisp/rev/wisp-mode-0.4.1
- fix linting errors: custom, deprecations, and docstrings.
- fix: remove the default to *shell* to avoid sending commands to an unexpected process -
#wisp 1.0.13 and wisp-mode 0.4.1 released.
wisp 1.0.13 (2026-05-04): https://hg.sr.ht/~arnebab/wisp/rev/v1.0.13
- add r7rs benchmark graph example with split geometric std
- fix: wisp.py missed escaping \ — thanks to leah2! (scheme IRC)
- may the 4th be with youwisp-mode 0.4.1 (2025-11-09): https://hg.sr.ht/~arnebab/wisp/rev/wisp-mode-0.4.1
- fix linting errors: custom, deprecations, and docstrings.
- fix: remove the default to *shell* to avoid sending commands to an unexpected process -
#wisp 1.0.13 and wisp-mode 0.4.1 released.
wisp 1.0.13 (2026-05-04): https://hg.sr.ht/~arnebab/wisp/rev/v1.0.13
- add r7rs benchmark graph example with split geometric std
- fix: wisp.py missed escaping \ — thanks to leah2! (scheme IRC)
- may the 4th be with youwisp-mode 0.4.1 (2025-11-09): https://hg.sr.ht/~arnebab/wisp/rev/wisp-mode-0.4.1
- fix linting errors: custom, deprecations, and docstrings.
- fix: remove the default to *shell* to avoid sending commands to an unexpected process -
#wisp 1.0.13 and wisp-mode 0.4.1 released.
wisp 1.0.13 (2026-05-04): https://hg.sr.ht/~arnebab/wisp/rev/v1.0.13
- add r7rs benchmark graph example with split geometric std
- fix: wisp.py missed escaping \ — thanks to leah2! (scheme IRC)
- may the 4th be with youwisp-mode 0.4.1 (2025-11-09): https://hg.sr.ht/~arnebab/wisp/rev/wisp-mode-0.4.1
- fix linting errors: custom, deprecations, and docstrings.
- fix: remove the default to *shell* to avoid sending commands to an unexpected process -
Just heard in an AI-fan video: "if you create a detailed state machine, the AI produces near perfect code."
If you create a detailed state machine, don’t you already *have* code?
Also see the #Guile State Machine Compiler:
https://memory-heap.org/~avp/projects/guile-smc/No AI involved and not just "near perfect", but guaranteed correct (modulo bugs).
-
Just heard in an AI-fan video: "if you create a detailed state machine, the AI produces near perfect code."
If you create a detailed state machine, don’t you already *have* code?
Also see the #Guile State Machine Compiler:
https://memory-heap.org/~avp/projects/guile-smc/No AI involved and not just "near perfect", but guaranteed correct (modulo bugs).
-
Just heard in an AI-fan video: "if you create a detailed state machine, the AI produces near perfect code."
If you create a detailed state machine, don’t you already *have* code?
Also see the #Guile State Machine Compiler:
https://memory-heap.org/~avp/projects/guile-smc/No AI involved and not just "near perfect", but guaranteed correct (modulo bugs).
-
Just heard in an AI-fan video: "if you create a detailed state machine, the AI produces near perfect code."
If you create a detailed state machine, don’t you already *have* code?
Also see the #Guile State Machine Compiler:
https://memory-heap.org/~avp/projects/guile-smc/No AI involved and not just "near perfect", but guaranteed correct (modulo bugs).
-
There’s now an #epub version of Naming & Logic: #programming essentials with #Guile #Scheme:
https://www.draketo.de/software/programming-scheme.epubIf you have an #ereader it would be great if you could test whether it works for you!
(ideally a hardware one; calibre worked fine for me)
It’s also linked from the book’s website:
https://www.draketo.de/software/programming-scheme -
There’s now an #epub version of Naming & Logic: #programming essentials with #Guile #Scheme:
https://www.draketo.de/software/programming-scheme.epubIf you have an #ereader it would be great if you could test whether it works for you!
(ideally a hardware one; calibre worked fine for me)
It’s also linked from the book’s website:
https://www.draketo.de/software/programming-scheme -
There’s now an #epub version of Naming & Logic: #programming essentials with #Guile #Scheme:
https://www.draketo.de/software/programming-scheme.epubIf you have an #ereader it would be great if you could test whether it works for you!
(ideally a hardware one; calibre worked fine for me)
It’s also linked from the book’s website:
https://www.draketo.de/software/programming-scheme -
There’s now an #epub version of Naming & Logic: #programming essentials with #Guile #Scheme:
https://www.draketo.de/software/programming-scheme.epubIf you have an #ereader it would be great if you could test whether it works for you!
(ideally a hardware one; calibre worked fine for me)
It’s also linked from the book’s website:
https://www.draketo.de/software/programming-scheme -
Been working on porting my physics simulations to the Web with #WASM via #Hoot.
Something like they did here: https://spritely.institute/news/building-interactive-web-pages-with-guile-hoot.html
I've been having to thoroughly read the examples, documentation, and hit my head against the wall, but I'm making progress! Still can't seem to get canvas drawing to work though.
-
Been working on porting my physics simulations to the Web with #WASM via #Hoot.
Something like they did here: https://spritely.institute/news/building-interactive-web-pages-with-guile-hoot.html
I've been having to thoroughly read the examples, documentation, and hit my head against the wall, but I'm making progress! Still can't seem to get canvas drawing to work though.
-
Been working on porting my physics simulations to the Web with #WASM via #Hoot.
Something like they did here: https://spritely.institute/news/building-interactive-web-pages-with-guile-hoot.html
I've been having to thoroughly read the examples, documentation, and hit my head against the wall, but I'm making progress! Still can't seem to get canvas drawing to work though.
-
@goose #guix was always meant to be a general purpose package manager from the get go. It did not start as a package manager for scheme code, suffered from an endless cycle of feature creep, and ended up being a Frankenstein's Monster project, if that is what you are asking.
Guile projects tend to use it because it is written in #guile. If you need a package manager for scheme code only, you can try Akku:
