While working on #GRASP, I occasionally try analyzing #Interlisp's #SEdit (because I'm curious about its internal representation), but I always end up not being able to understand literally anything from that code base.
And that makes me wonder: are the sources of GRASP so much easier to understand to me because I'm their author, or do the programming practices that I use (such as type definitions and plenty of examples) actually make things easier to read?
(A while ago, I did have a look at implementations of some things in #Emacs. The "undo" mechanism is understandable, but it owes this understandability to comments which make up for a missing type system. On the other hand, I've found Emacs' implementation of window splits much more difficult thant in GRASP -- in large part because GRASP is written in #Kawa#Scheme, and has a Java-like OO system, and I feel that classes and objects do a really good job at grouping related things together.)
I just opened up registration for the March iteration of the "Hands-On Guile Scheme for Beginners" course!
This is an 8-week course that is a mixture of on-demand learning content, live Q&A sessions, practical exercises, and a private forum where I answer all your questions. We had a great time in the February iteration so I'm looking forward to running it again!
Come learn Scheme and functional programming with us!
@rml did you see the #spritelyInsitute#scheme#hoot#wasm shindig? Tbh when I think of a scheme hacker with a lot of web creation experience who isn't @Sandra or @chris (or Christine herself) I think of you. @cwebber
In the early 1990s PC Scheme for MS-DOS was my very first Lisp system.
It was a rich, fast, and surprisingly capable compiled environment with features such as a Lisp-aware editor, first class continuations and environments, engines, OOP extensions, text windows and graphics support, and more. Here's the excellent manual:
Plan to stream about management of elixir projects with Guix in one hour and a half.
Will talk about transitive package management in general and why it's better not to package language-specific packages with Guix, will learn by example and clean up some tools we've made during the last month for Elixir in particular.
I am very inclined to start learning #Guile / #Scheme solely for this dream:
With the introduction of an FFI, you can now implement nearly your entire web frontend in Scheme; the examples we've looked at today are but a glimpse of what's now possible!
In the future, we hope the Guile community will join us in developing a colorful variety of wrapper libraries for commonly-used web APIs, so that building with Hoot becomes increasingly fun and easy.
I don't know about you but a Lisp (or a Scheme) directly on the web is flat out sick as hell. Writing web UI programs directly in Lisp? Sick as hell. Lisp WASM compiler? Sick as hell.
I now have two reasons to be learning Guile/Scheme: Guix and Hoot.