@leobm @enigma #lisp is something that does this image based thing to. Most of the time you save the current state of your app and deploy it :D. I love the idea too cause its exactly what containers do now. I would love to see stuff like there also more often. I really want to get started in #perl somehow no clue why but the idea of there is more than one way to describe a problem is really nice. And most of the time i get this feeling in #clojure and #lisp to because you can extend the language. I really want to see what #perl does that gives it its nature of beeing expressive and "hard" to read.

My current contract is winding up mid-Jan, so I've got some availability coming up for either contract dev work (#elixir / #clojure / #rustlang / etc) or external dev lead roles.

Please do get in touch if I might be able to help.

Craft software that makes people feel something - Raphael Amorim

Recently, people have been asking me why I’m pausing Boo to work on a programming language. I think it would actually be cool to write down how I feel.

Raphamorim
Day 4 - Advent of Code 2025

map operations

YouTube
Day 3 - Advent of Code 2025

State of Clojure 2025

https://toast.ooo/post/11024522

State of Clojure 2025 - toast.ooo

Lemmy

State of Clojure 2025

https://lemmy.ml/post/40108290

State of Clojure 2025 - Lemmy

Lemmy

State of Clojure 2025

Who uses Clojure and how? Let's find out.

Pondering on the most minimal #Clojure deps.edn / Lein -mimicking setup for #CommonLisp: ASDF and Makefiles.

• Dependencies can be specified in ASDF and augmented by Quicklisp/CLPM/Vend calls. Or the submodule-driven workflow I’ll soon annoy y’all with.

• Aliases/tasks/workflows can be emulated by a Makefile with compiler calls

• Tests are just a call to ASDF:test-system from the same Makefile:

$(LISP) $(LISP_FLAGS) --eval '(require "asdf")' --load cl-minifloats.asd --eval '(asdf:test-system :cl-minifloats)' --eval '(quit)'

• Custom REPLs are… much more fun. I’m thinking something along the lines of:

◦ making a separate ASDF system (sys/repl) depending on Swank/Slynk and the original system

◦ then launching Lisp in Makefile with

$(LISP) $(LISP_FLAGS) --eval '(require "asdf")' --load cl-minifloats.asd --eval '(asdf:load-system :cl-minifloats)' --eval '(slynk:start-server 4006)'

◦ and connecting to it in #Emacs

• Maybe make a custom :perform operation for this sys/repl system?

• This means a hard dependency on Swank/Slynk and Emacs. Clojure has nrepl that’s more editor-independent. Are Alive, Slimv etc. using Swank too?

• Alias composition (dev:test:nrepl) though… Can be emulated with Makefile flags, but how many flags would that be?

• Project initialization and templates are complicated and under-explored. I use a (long forgotten) Quickproject to setup my CL libraries, but it has its drawbacks and should never be used for more general tasks. Some projects (Weblocks IIRC) provide their own templates, which is good already, but it doesn’t scale to all domains. A more general and conventional solution is needed.

• No, I won’t mention Roswell, don’t even ask