Another new project I already abandoned but still am quite proud of: Laliza, classic Eliza AI re-implementation in #CommonLisp: https://codeberg.org/aartaka/laliza

Supports the legendary DOCTOR script, palindrome and some other scripts listed on elizagen. But yeah, it seems to be unsuitable for generic enough programming, so I abandoned it.

Another new project I already abandoned but still am quite proud of: Laliza, classic Eliza AI re-implementation in #CommonLisp: https://codeberg.org/aartaka/laliza

Supports the legendary DOCTOR script, palindrome and some other scripts listed on elizagen. But yeah, it seems to be unsuitable for generic enough programming, so I abandoned it.

OK, here is CL-RemiMatrix, my library for #CommonLisp to interact with the #matrix protocol! This is just v0.1.0 and doesn't cover everything in the Matrix protocol, but it should be usable enough to write bots (I've done a few with it already) and maybe even a basic client. I'll of course keep adding to it as time goes on.

Source code repo, release tarbal, and so on are all here:
https://fossil.cyberia9.org/cl-remimatrix/

It uses my CL-RemiMarshal library internally for all its JSON (de)serialization to/from CLOS. Made it soooo easy to make CLOS classes for the protocol.

New #CommonLisp library: cl-inix, a flexible #DOS/#Linux .INI/.conf file parser and processor, superseding unmaintained and inflexible cl-ini. Allows you to get .INI files parsed in the format you prefer, get values from there, and write them back however you like.

Because .INI files are underrated and deserve more use. No bullshit plaintext configuration format, for once.

https://codeberg.org/aartaka/cl-inix

OK, here is CL-RemiMatrix, my library for #CommonLisp to interact with the #matrix protocol! This is just v0.1.0 and doesn't cover everything in the Matrix protocol, but it should be usable enough to write bots (I've done a few with it already) and maybe even a basic client. I'll of course keep adding to it as time goes on.

Source code repo, release tarbal, and so on are all here:
https://fossil.cyberia9.org/cl-remimatrix/

It uses my CL-RemiMarshal library internally for all its JSON (de)serialization to/from CLOS. Made it soooo easy to make CLOS classes for the protocol.

New #CommonLisp library: cl-inix, a flexible #DOS/#Linux .INI/.conf file parser and processor, superseding unmaintained and inflexible cl-ini. Allows you to get .INI files parsed in the format you prefer, get values from there, and write them back however you like.

Because .INI files are underrated and deserve more use. No bullshit plaintext configuration format, for once.

https://codeberg.org/aartaka/cl-inix

#oop #programming #GUI #commonLisp #McCLIM #softwareEngineering
Article in which I show simple multiple inheritance and method qualifiers in ANSI common lisp's common lisp object system, then show how the McCLIM implementation of the common lisp interface manager 2 specification turns the objects I was working with into rich general user interfaces with a minimal declarative effort presupposing that I was presenting lisp objects.

Rich interfaces pervade lisp's history.
https://screwlisp.small-web.org/clim/basic-principle/

#oop #programming #GUI #commonLisp #McCLIM #softwareEngineering
Article in which I show simple multiple inheritance and method qualifiers in ANSI common lisp's common lisp object system, then show how the McCLIM implementation of the common lisp interface manager 2 specification turns the objects I was working with into rich general user interfaces with a minimal declarative effort presupposing that I was presenting lisp objects.

Rich interfaces pervade lisp's history.
https://screwlisp.small-web.org/clim/basic-principle/

Apropos of nothing, this is a project I started some time ago. Due to the community’s lack of interest and financial support, I kind of stopped…just testing the waters for it again.

https://codeberg.org/IDEmacs/IDEmacs

IDEmacs aims to be a set of #Emacs configurations which provide an out-of-the-box experience similar (if not identical) to popular GUI IDEs and editors.

It is aimed at…

1. Programmers coming to Emacs from other IDEs, or even first-time programmers familiar with only office applications.

2. Beginner #CommonLisp and #Scheme programmers, who need the functionality of Emacs (Sly/Geiser + structural editing) without having to perform unnecessary setup and without dealing with an alien style of keybindings. In other words, similar to Portacle or Guile Studio.

3. Non-programmers who want a fully-featured #Org, #Markdown, or #LaTeX editor with idiomatic shortcuts and mouse-friendly GUI.

It aims to provide…

1. GUI and mouse support, in addition to a keyboard-driven interface.

   • Unlike most starter kits, we do not hide GUI elements by default.

   • We support configuration via the custom GUI, not just Elisp

   • If resources allow, we may implement new GUIs in Emacs

2. Keybindings that follow popular GUI and IDE conventions.

   • CUA mode is just the start - much more keybinding configuration is needed to provide an unsurprising experince. And that’s before we even get to the IDE-specific keybindings.

   • This excludes starter kits that use Evil by default, such as Spacemacs or Doom.

3. A fully-featured, fast, and configuration-free Emacs experience, like any starter kit/distro.

   • The configuration uses idiomatic Elisp and contains a generous amount of comments, valuable to anyone interested in learning to configure Emacs using Elisp.

Perfectly imitating the GUIs and subtle behaviour differences of IDEs is desirable, but not top priority. Given our limited resources, we aim for “good enough”.

We hope this gives new users a comfortable starting point, and make them more likely to stick around to discover the possibilities of Emacs’ malleability, rather than being driven off by the default experience.

#contraCodes #Lisp #EmacsLisp

Apropos of nothing, this is a project I started some time ago. Due to the community’s lack of interest and financial support, I kind of stopped…just testing the waters for it again.

https://codeberg.org/IDEmacs/IDEmacs

IDEmacs aims to be a set of #Emacs configurations which provide an out-of-the-box experience similar (if not identical) to popular GUI IDEs and editors.

It is aimed at…

1. Programmers coming to Emacs from other IDEs, or even first-time programmers familiar with only office applications.

2. Beginner #CommonLisp and #Scheme programmers, who need the functionality of Emacs (Sly/Geiser + structural editing) without having to perform unnecessary setup and without dealing with an alien style of keybindings. In other words, similar to Portacle or Guile Studio.

3. Non-programmers who want a fully-featured #Org, #Markdown, or #LaTeX editor with idiomatic shortcuts and mouse-friendly GUI.

It aims to provide…

1. GUI and mouse support, in addition to a keyboard-driven interface.

   • Unlike most starter kits, we do not hide GUI elements by default.

   • We support configuration via the custom GUI, not just Elisp

   • If resources allow, we may implement new GUIs in Emacs

2. Keybindings that follow popular GUI and IDE conventions.

   • CUA mode is just the start - much more keybinding configuration is needed to provide an unsurprising experince. And that’s before we even get to the IDE-specific keybindings.

   • This excludes starter kits that use Evil by default, such as Spacemacs or Doom.

3. A fully-featured, fast, and configuration-free Emacs experience, like any starter kit/distro.

   • The configuration uses idiomatic Elisp and contains a generous amount of comments, valuable to anyone interested in learning to configure Emacs using Elisp.

Perfectly imitating the GUIs and subtle behaviour differences of IDEs is desirable, but not top priority. Given our limited resources, we aim for “good enough”.

We hope this gives new users a comfortable starting point, and make them more likely to stick around to discover the possibilities of Emacs’ malleability, rather than being driven off by the default experience.

#contraCodes #Lisp #EmacsLisp

#programming #softwareEngineering #programmingLanguage #lisp #commonLisp #tiobe
https://screwlisp.small-web.org/fundamental/is-common-lisp-an-especially-good-language/
I graphed the number of years since each of the tiobe programming language top 25 current versions were created and found only ANSI Common Lisp (and Visual Basic 1998) aren't babies. I look at @nytpu 's article about lisp as a fulcrum for understanding what a current programming language having a long history is like. There are no examples outside of LISP.

Looking forward to your thoughts.

another thought I am interested in @kentpitman 's opinion about might be (re)invigorating, for example, #lispGameJam or #lispGames otherwise. This autumn there were only 20-odd one-week-game-jam submissions and only one in ANSI #commonLisp. Looking at the Tiobe index, lisp as such slid from #2 ("most popular")) in 1985 to #24 "more popular than COBOL" in 2025 https://www.tiobe.com/tiobe-index/ .

#lispGameJam #commonLisp #programming #devlog #commonLisp #mcclim #nicclim #gamedev #itchio in which I play with the make-my-own-level player activity. (It's unix-surrealism-jam not just NicCLIM because it is built around the unique unix-surrealism-jam controls not my preexisting NicCLIM's)

Article: https://screwlisp.small-web.org/lispgames/my-common-lisp-game-jam-self-experience/

Jam submission https://itch.io/jam/autumn-lisp-game-jam-2025/rate/3822491 ,
my fellow jammers:
+
Pixel Outlaw's #interlisp https://itch.io/jam/autumn-lisp-game-jam-2025/rate/4015363
@mdhughes ' MUD https://itch.io/jam/autumn-lisp-game-jam-2025/rate/4002647

This article is #lisp dopamine: basically, the #rust and #java guys sweated in teams big time to beat the old, un-optimized original #commonlisp version in speed and memory use.

https://renato.athaydes.com/posts/revisiting-prechelt-paper-comparing-languages.html

The author released another short "getting started" post yesterday.

This article is #lisp dopamine: basically, the #rust and #java guys sweated in teams big time to beat the old, un-optimized original #commonlisp version in speed and memory use.

https://renato.athaydes.com/posts/revisiting-prechelt-paper-comparing-languages.html

The author released another short "getting started" post yesterday.

Worked 4 hours on the #lisp Cookbook today, from a reader's email full of details, and also for the new PDF rendering (done with the great #typst).

Just so you know 😉 so you can star it and get us to 1k GitHub stars, and to recall you can send pull requests of typos and grammar fixes ;)

https://github.com/LispCookbook/cl-cookbook/commits/master/

https://lispcookbook.github.io/cl-cookbook/

#commonlisp

Now, back to clients work :S

Worked 4 hours on the #lisp Cookbook today, from a reader's email full of details, and also for the new PDF rendering (done with the great #typst).

Just so you know 😉 so you can star it and get us to 1k GitHub stars, and to recall you can send pull requests of typos and grammar fixes ;)

https://github.com/LispCookbook/cl-cookbook/commits/master/

https://lispcookbook.github.io/cl-cookbook/

#commonlisp

Now, back to clients work :S

#tootcoding #commonLisp
(execute-frame-command *nic* '(writef garden))

EDIT:
On disk, GARDEN is now:
(SOIL) (SOIL) (SOIL) (SOIL) (SOIL)
(SOIL) (SOIL GRASS) (SOIL) (SOIL) (SOIL)
(SOIL) (SOIL) (SOIL) (SOIL GRASS) (SOIL GRASS)
(SOIL) (SOIL) (SOIL) (SOIL) (SOIL)