mastodon.world is one of the many independent Mastodon servers you can use to participate in the fediverse.
Generic Mastodon server for anyone to use.

Server stats:

11K
active users

#commonlisp

11 posts10 participants5 posts today
Replied to Jonathan Lamothe

@me You can find here 2 interviews of small teams using CL. One "secretly", one in a great open-source product:

"questions to Alex Nygren of Kina Knowledge, using Common Lisp extensively in their document processing stack"
lisp-journey.gitlab.io/blog/li

"Arnold Noronha of Screenshotbot: from Facebook and Java to Common Lisp."
lisp-journey.gitlab.io/blog/li

Lisp journey · Lisp Interview: questions to Alex Nygren of Kina Knowledge, using Common Lisp extensively in their document processing stack - Lisp journeyBy Lisp journey
Replied to Jonathan Lamothe

@me Personally, as a solo developer, I use CL more and more in my stack, ditching Python the more I can. I wrote about it: lisp-journey.gitlab.io/blog/ru

Instead of extending a Python software I write independent modules in CL. It works well for standalone scripts too (read a DB, process data, send everything to a FTP, to a web service, by email…) It's such a joy.

On Discord, we see some are in big tech©, wrote their personal tool in CL and now it's part of the team's stack.

Lisp journey · Running my 4th Common Lisp script in production© - you can do it too - Lisp journeyBy Lisp journey

Me encanta programar en #Lisp en mi tiempo libre. La programación funcional fomenta la abstracción y me permite construir sistemas complejos a partir de funciones simples. El REPL me abre la puerta a jugar en tiempo real con el código sin tener que reiniciar constantemente el software o forzarme a lanzar un programa de depuración. Para mi es una herramienta poderosa para afinar mis habilidades de programador, probar nuevas ideas, patrones y un espacio para la creatividad. Además tienes sabores en cualquier lugar: #Clojure para JVM, #ClojureScript para #JavaScript, #Emacs Lisp para Emacs, #CommonLisp y #Racket para ejecutar en el equipo... Aunque yo te recomiendo que te quedes en un solo lenguaje y lo domines. No es necesario aprender todos los dialectos de Lisp, pero si es bueno conocerlos para entender sus diferencias y similitudes.
Si quieres aprender más sobre #Lisp, te recomiendo uno de mis libros favoritos: "Land of Lisp" de Conrad Barski. Es un libro divertido que te enseña a programar en Lisp mientras creas juegos y aplicaciones gráficas. También puedes encontrar muchos recursos en línea, por supuesto.

https://tomscii.sig7.se/2025/04/The-Barium-Experiment

TLDR: All guis suck. Xwindows isn't going anywhere anytime soon.
Common lisp is the obvious language to use for reasons.

I agree with this whole blog post, and they have a new gui project:
I especially agree with the shittiness that is gui frameworks
(and other frameworks too i guess) intentionally obsoleting
their stuff before it even catches on. (gtk)
I assume the gui frameworks don't see it that way, but that
logic is pretty inescapable. Another example of my new
phrase "novelty chasers".

https://tomscii.sig7.se/barium/

#commonlisp
#techpost

The port of my music player #Benben to #CommonLisp continues... and as of tonight, the original S-Lang TUI interface is working! ​:happyremi: I even managed to fix a bug with the scrolling text fields and Japanese text.

The only C bindings going on here are:
#libxmp (to play the .xm file), libao (final audio output), ZStandard (VGM decompression), and #S-Lang (TUI). The rest is pure Common Lisp, including the DSP effects and #VGM playback/chip emulation.

Normally you launch this from the command line (which is also working), but I did it with Emacs+Slime just to be fancy.

#LinuxAudio

Replied in thread

@simendsjo @jackdaniel #XMPP has all those features, and there's a fairly big #Lisp / #Scheme / #CommonLisp channel there - xmpp.link/#lisp@conference.a3.

It might not have everything that #Discord does, but it's vastly better than #IRC. And there's a cost to using #proprietary and #centralized services, which people constantly forget about in chasing convenience and shiny features.

Here's a guide to help you get started.
contrapunctus.codeberg.page/th

xmpp.linkXMPP Invitation

Lisp sucks. Tell me what's wrong here:

(DEFVAR x 0) ; GLOBAL BADNESS STAYS

(DEFUN dO-StuFf (NUMBer)
(LET ((rEsUlT 1))
(DECLARE (SPECIAL X)) ; THIS IS LEGAL HERE
(SETQ X NUMBER)
(TAGBODY
StaRT
(IF (< X 1) (GO ENDz))
(SETQ rEsUlT (* rEsUlT X))
(SETQ x (- x 1)) ; NOTE: STILL USING GLOBAL x INSTEAD OF LOCAL X
(GO StARt)
ENDz)
(pRiNt (lIsT 'FACtoRiAl-oF NUMBER 'iS rEsUlT))))

(DEFUN nOW-dO-AlL ()
(LET ((I 0))
(LOOP
(WHEN (> i 5) (RETURN))
(Do-sTUFF i)
(SETQ i (+ i 1)))))

(nOW-dO-AlL)

#commonlisp #lisp #sbcl #clisp @amszmidt @screwtape

Common Lisp - with its open-source implementation, SBCL, offers greater resilience against US tech export controls and sanctions compared to Go. Its stable, long-lived libraries can be easily archived locally. Go, however, undergoes frequent changes and depends heavily on GitHub, which is a US-based service, increasing its exposure to such restrictions. Furthermore, since our project is non-military, encryption algorithm limitations do not pose a concern for our use case.

Here's a new challenge for Lisp folks to figure out.

Why does this fail. And don't give the error message as the answer. WHY does this do what it does?

(defun who-am-i ()
(flet ((x () 'inner))
(labels ((x () (x))) ;;
(x))))

Is the third line calling inner or itself?

Okay you get one second hint: Yes, it overflows. Why?

That is the challenge.

Kinda nice that my port of my music player #Benben from Crystal to #CommonLisp is now far enough along that I can use it as my daily music player. The only caveat is that I currently have to use a new "Minimal UI" that I implemented as an alternative for v0.7.0. But overall, it didn't take as long as I expected to get it in a usable state ​:happyremi:

I'm definitely not ready to release v0.7.0 yet, though. I'm lacking the entire original UI, VGM support is incomplete, and it's missing a few formats still (Opus/Vorbis, SID). Also, I haven't implemented rendering to WAV/AU yet. But that'll all come with time.