@daviwil #systemcrafters #sigil I’m really excited to see what sigil could actually be. I really envision a flutter like UI kit using #scheme and able to compile to wasm. Is there any interest with #prescheme , possibly have sigil compile down to C?
@daviwil #systemcrafters #sigil I’m really excited to see what sigil could actually be. I really envision a flutter like UI kit using #scheme and able to compile to wasm. Is there any interest with #prescheme , possibly have sigil compile down to C?
@timClicks for me the union of subject, lecture and references. A highlight, #Abelson and #Sussman, “Structure and Interpretation of Computer Programs”
#Lisp / #scheme <https://ocw.mit.edu/courses/6-001-structure-and-interpretation-of-computer-programs-spring-2005/video_galleries/video-lectures/>
I just posted a few updates about GNU Mes in the blog:
https://ekaitz.elenq.tech/fasterMes4.html
I hope you enjoy it, let me know if you have comments or questions.
Just ordered the #guile #scheme course from https://systemcrafters.net/courses/hands-on-guile-scheme-beginners/ can’t wait to start this after work. #systemcrafters
I've been wanting to create my own programming language for a while now.
Starting to think that instead of building one from scratch, that maybe I'll start by taking Wisp https://www.draketo.de/proj/wisp/ (basically #scheme with whitespace instead of parens) and figuring out how to make it transpile to #golang. [edit: Doh! TCO support isn't as complete as I'd need]
Then start tweaking and iterating to gradually give it the features I want for "my" language.
🤔 just thinking out loud.
This is a really good intro to #scheme and so far all examples work with #guile. For me this is a great read https://docs.scheme.org/schintro/ #slowdownandread. Quite fun read and understanding.
@sigismundninja @rafa I personally think #fedora is a sweet spot if you like bleeding edge, and modern system, but with widespread usage and well tested. I think community wise #opensuse is not at the same level, and #debian is great, but a bit too conservative for me.
I am making an effort to script and automate everything with #lisp / #scheme / #bash and others and some #guix sprinkles for reproducibility on top of a traditional distro, and it feels good 👍
I have partially resolved the issue I mentioned in my #EmacsConf2025 presentation, regarding the closure of a lambda not correctly capturing it’s environment.
I say “partially” resolved because although my current solution results in correct program behavior, it does not consider let-bound variables inside of the closure. So variables declared locally to the closure using the let keyword will mask variables of the same name in the closure environment. A correct implementation will simply not include those masked variables in the closure environment at all. This can sometimes impact garbage collection, since a closure may be holding a variable which retains a large amount of memory, but that variable not accessible anywhere since it is masked by the let-bound variables in the closure.
However, I am eager to keep things moving, so I am merging this PR and opening a new issue to resolve the let-bindings problem later. To find out more, see issue #62 on Codeberg.
#Gauche Devlog - Alternative external formats for arrays and complex numbers
http://blog.practical-scheme.net/gauche/20251211-alternative-array-complex-format
SchemeCrossReference
https://practical-scheme.net/wiliki/schemexref.cgi
It seems like this is the only wiki-like project that collects cross-implementation and cross-standard-edition infos of Scheme symbols. Sadly not much people being aware of its existence.
I think we as a community should pick it up and make it up-to-date
I regret not including return type/shape check in #Scheme SRFI 253 define-checked. It feels so obvious in the hindsight—typed functions should have return type listed in their definition. But past me didn't consider that for some reason.
Time for a new #SRFI?
Another bucket list item for 253 is having type support built-in, instead of relying on generic predicates. Say, by specifying typed? special syntax. As in
(check-arg (typed? long long) (factorial 23))
instead of using implementation-specific facilities and extending SRFI 253 primitives with them.
But then, providing literal implementation-specific types is not portable, so it's a smart decision I made sticking with standard predicates. Just a bit of extra work making it first-class on every implementation.
Today I'm #live reordering some GNU Mes commits and testing my Garbage Collector changes.
Please distract me with some philosophy.
Share of programming languages used by #GTK3 / #GTK4 applications (2025-12-13):
30% #Python
20% #Rust
19% #Vala
17% #C
6% #gjs #Javascript #Typescript
5% #C++ #Cplusplus
1% #Go
1% #Csharp
2% Other: #Lua #Swift #Kotlin #Perl #Haskell #Crystal #D #Scheme #Clojurescript
71% use GTK4 (92% of them #libadwaita), still 29% GTK3
Method: Source [1] lists 800 awesome #gtk (3/4) #opensource applications and their #programminglanguage
[1] https://github.com/valpackett/awesome-gtk
#GTK #FLOSS #Linux #Gnome
@GTK @gnome
I wrote my nix-let* macro for Pipchix and here it is demonstrated: https://pastebin.com/wuhHM46L
The example actually does not show the utility. It can be used for idioms such as using the same identifier for operation result after operation result, step by step, in OCaml style.
Also demonstrated is multiordinal evaluation of an identifier, ‘c’, translated into Nix as string interpolation. :) This must be a bug. It is what is needed on left sides but not on the right.
Reading about golblins-share from the #spritelyinstitute , Golblins-share is a p2p encrypted sharing application. https://spritely.institute/news/goblinshare-secure-peer-to-peer-file-sharing-with-goblins.html
So far this is a very good article about what can be done with Goblins and #guile #scheme.
Recreational reading: R7RS #Scheme! https://standards.scheme.org/corrected-r7rs/r7rs-Z-H-1.html#TAG:__tex2page_toc
So I guess it makes more sense to create wrappers from rust to C then create #guile bindings from the C code. #niri #guile #scheme, maybe is a great time to learn #prescheme ?
Cleaning up the Tower: Numbers in Scheme
by Sebastian Egner, Richard A. Kelsey, Michael Sperber
https://www.deinprogramm.de/sperber/papers/numerical-tower.pdf