New blog post: "So I've Been Quiet Lately..."

https://remilia.sdf.org/blog/2026-02-14-a.html

#benben #pascal #CommonLisp

For my research into building better abstractions, I'm looking at #CommonLisp, and, in particular, #CLOS, the extremely flexible and powerful #OO system that is part of the language. It is probably as powerful as any OO language in existence, given that some of the internal mechanisms can be altered to better fit your problem space. According to the Art of the Metaobject Protocol, CLOS doesn't occupy a point the space of possible OO systems, but a region.

Common Lisp Screenshots is a new gallery of screenshots of GUI applications written in Common Lisp and targeted at end users. A great idea by @vindarel

http://www.lisp-screenshots.org

https://lisp-journey.gitlab.io/blog/lisp-screenshots-todays-common-lisp-applications-in-action

#CommonLisp #lisp #screenshots

Public Lispy Gopher Climate sunday Morning in Europe stream - 2/14/2026, 7:53:54 AM

https://toobnix.org/w/wzDqaQke9raTSTxVDHTemo

#lispyGopherClimate #valentinesDay Morning in Europe #peertube #live #programming #technology #podcast .

#archive https://toobnix.org/w/wzDqaQke9raTSTxVDHTemo

Oldschool versus newschool
#lisp #versus #CLOS in #commonLisp

(basically me monday morning quarterbacking myself from the Tuesday-night-in-the-americas hosted by Ramin)

I will at least try push-button running *this article* which factors into the long-delayed current log I am writing. https://screwlisp.small-web.org/software-individuals/sandewalls-sat-solver-implementation-example/ which feeds into the other topic.

i think a gap buffer is a simpler data structure for a text editor, it's essentially just a dynamic array, and Emacs uses it as well.

#programming #commonlisp #lisp

Common Lisp Screenshots

https://lemmy.ml/post/43143553

“Learn Lisp the Hard Way,” 2nd draft, last updated in 2022.

https://llthw.common-lisp.dev

#lisp #commonLisp

Streaming #McCLIM and #OpenGL things today, 2026-02-13 at 11:30a EST/ 17:30 UTC. (approx 3.5 hrs from now)

https://www.twitch.tv/endparen

I'm going to take stock of where the current work for medium-copy-area with my wayland-ffi backend is, acknowledge I've hit a wall, and then find a different issue to tackle. It feels "good enough" for most cases and I want to keep making forward progress so I can begin planning the move to more modern things like batch rendering or shaders etc.

#CommonLisp #gui

Now that I made my own #CommonLisp named readtable <https://codeberg.org/aartaka/lin-edi-table>, I start to appreciate named readtables. Before, I only scolded about them making libraries dependent on non-standard syntax. But hey, that's the point: using cool syntax, but not polluting the standard language with it! Named readtables are a nice declarative-ish API allowing to granularly reuse syntax much like one can reuse macros or plain functions / classes.

I mean, complaining about someone else's custom syntax library not looking perfect enough and writing one's own is such a First World problem, given how bad it is for custom syntax in non-#Lisp langs. But a person gotta dream, right?

This weeks project is a browser-based editor area for Common Lisp.

Supports most special forms, auto-indents code, can do region indent too.

Backend-assisted, communicates via websocket. Simple html+JS+CL.

Can be used as an embedded CL form editor in other projects.

Grab it at https://git.sr.ht/~hajovonta/cl-web-editor

See screencast below as a demo.

#commonlisp

I’m uneasy about chaining / threading / piping operators, be it #Haskell’s $, #Wisp colon, #Clojure arrows, or my own #CommonLisp #/ operator from <https://codeberg/aartaka/lin-edi-table>.

These seem to restrict the code in what it can do. With dirty imperative or functional code, you can insert new forms literally everywhere. But with these operators you have to come up with strategies to compose things properly.

Which is not a problem with Clojure, because at least built-ins are designed with threading in mind. But it’s much harder in brown field langs like CL.

This post was brought to you by refactoring a complex seven-stage threading in Clojure.

Aperiodic reminder that #commonlisp is awesome!

🎨 #commonlisp in action:

http://www.lisp-screenshots.org/

https://lisp-journey.gitlab.io/blog/lisp-screenshots-todays-common-lisp-applications-in-action/

Send your screenshot!

#lisp

@ramin_hal9001
#archive https://communitymedia.video/w/sBNPeWFJ7NuDVCjkAv7fkX #lisp #climate

@pluralistic essay I mentioned: https://pluralistic.net/2026/02/09/sloppy-steve/#mckinley-fanfic-panic relevant to ramin's polemic.

@mdhughes #scifi authors https://appdot.net/@mdhughes/116049198384873875

#coalton ( #staticallyTyped #DSL macroexpanding to #CommonLisp ) https://coalton-lang.github.io/
A coalton podcast I didn't watch yet: https://www.youtube.com/watch?v=niWimo9xGoI

@kentpitman

#lispyGopherClimate #live #technology #podcast hosted by @ramin_hal9001 https://tilde.town/~ramin_hal9001/articles/ai-cannot-live-up-to-the-hype.html this week!

https://communitymedia.video/w/sBNPeWFJ7NuDVCjkAv7fkX

My guess as to the topic from the main show toot which is

https://fe.disroot.org/objects/88f34eba-ccaf-407e-8505-8a2a3bd1613b <- visit

@kentpitman 's poem

Repudiating the #ai #llm hype!

And #environmental damage #climate

#commonLisp #lisp #typeTheory #coalton common lisp static typing DSL https://coalton-lang.github.io/ ,
#ELS 2025 talk by Robert Smith. Robert emailed a note.

#programming

@ramin_hal9001 well I put all of my power between now and you being live one hour from now in listening to Robert's Coalton talk. What are *you* planning to say about this?

I didn't realize that Coalton was basically exactly like cl-series but where cl-series is a very heavy macro package for pieces of lazy pure common lisp,
Coalton is a very heavy macro package for pieces of purely statically typed common lisp.

(With all the implications of that just for that expansion). #commonLisp

A new #blog post! This time, I’m exposing #CommonLisp #Lisp package-inferred systems as motivating harmful practices and making people’s life worse. Inside:

• Discipline and Wrong :use—it’s too easy to :use too much

• #IDE-less Reading—being impossible with package-inferred systems and their symbol mixing

• Packaging Hell

• Systems are Metadata, not Data—as a small ontological note

https://aartaka.me/package-inferred.html