Today on #SystemCrafters Live, we'll experiment with Spritely Goblins, a Guile Scheme library that provides a distributed programming model for writing secure, asynchronous code that can be called either locally or across a network.
Let's try it out to see if it might be a good fit for the Spring Lisp Game Jam next week!
Join us here:
- https://youtube.com/live/rs1xyXquFKE
- https://twitch.tv/SystemCrafters
- https://systemcrafters.net/live
in your time zone: https://time.is/compare/1800_in_Athens
#BSI IT #Grundschutz (with #Guile):
https://www.draketo.de/software/bsi-grundschutz
Plain language English summaries of the most important points (as I see them) by the German IT security agency for #software developers.
With short practical answers how to implement them in your work when using #GNU Guile #Scheme.
This is absolutely non-official. Read the original document if you want to know details or assure your legal department.
It’s a work in progress. See the TODOs:
https://www.draketo.de/software/bsi-grundschutz#todo
The accidental exploration of today: I can prevent auto-setting of non-removable procedure-name in let/define binding by wrapping lambda call into identity or some other function.
I still don't know how procedure name is set and why it's non-removable.
Fibers in #guile provides a nice way to compute a function up to a timeout:
https://git.sr.ht/~afmoreno/limiter/tree/main/item/main.scm
Comments/critiques welcome
There is a handy comment macro. It ignores the body and returns #<unspecified>.
I use it often during development, I wrap some code in it, which I re-eval from time to time, but don't want to be evaluated during whole module eval/reload.
I came up with the idea that it's handy to re-run tests after every eval. This tremendously reduces the feedback loop.
It's useful for TDD: you just write a few failing tests, modify the code that doesn't work yet and get the immediate feedback if they became green or still failing.
I bet it has much more use cases.
Later I realized that it's called Continuous Testing. This is a so good fit for Lisp and similar languages with highly interactive development environments.
After a few month of RnD, the testing library I work on is finally got to the point, where the design seems reasonable and settled. Now the easy part - carefully implement all the missing bits and integration with IDE.
https://git.sr.ht/~abcdw/guile-ares-rs/tree/75b3004/src/guile/ares/suitbl.scm#L445
Sonic Boom, baby.
Acrylic paint on 11 x 14 stretched canvas.
Custom design by 8-Bit Acrylic.
Grr using guix as a package manager on #Archlinux isn't the most fun, so I added the guix guile modules path to an emacs instance then called emacs in a guix shell. Geiser-guile REPL sees the modules*.scm but the modules don't run ... hmm ... #guix , #guile
Paris: Guix@Paris, Le jeudi 17 avril 2025 de 19h00 à 22h00. https://www.agendadulibre.org/events/32363 #guix #guile #logicielsLibres #rencontreMensuelle
Una scusa per provare "Framamèmes"
https://framamemes.org/
#meme #dev #scheme #racket #guile #guilescheme
Streaming about testing library for Scheme, NLnet grant, its integration into Arei/Ares Guile IDE and some library architecture design thoughts in a couple hours. It's inspired by clojure.test and junit, but still quite schemy.
The next time libcucks start defending NixOS, read this, dipshits. NixOS is associated, and some way or another, backed by Palantir and Anduril.
I find it a bit ironic: I can't write a Scheme macro, which pre-evaluates arguments for arbitrary form. Because I can't determine if form is a macro or procedure application and thus can't handle those use cases differently.
The #guile #lsp server just landed to #guix.
https://codeberg.org/guix/guix-mirror/commit/ed325ce878
guix install guile-lsp-server
Happy hacking !