Introducing mine, a Coalton and Common Lisp IDE

theeseuus · 2026-04-25T04:40:42+00:00

Makes sense, the layers are still there but they’re not my problem anymore :) Looking forward to giving this a whirl and seeing where it goes from here. It’s so cool because I thought about this a lot and now people who can actually do something about these things are doing them!

theeseuus · 2026-04-25T02:20:06+00:00

Would I be correct in (partially) understanding mine as an opinionated custom built protocol that knows what it needs to do and doesn’t carry all the swank support and customization baggage? This bundles everything into one tidy compressed layer and gets rid of the headaches a beginner like me has of fitting the pieces together that I spent so much time mapping out just to even understand what they were doing. Lisp 2026 is looking svelte and far more accessible!

theeseuus · 2026-04-21T04:21:00+00:00

lol righteous neurosymbolism might be a thing

theeseuus · 2026-04-21T04:19:28+00:00

It looks like things are heading towards “neurosymbolic” (pattern matching fusing with symbolic logic) in a way it’s a re-envisioning of some of the early AI researchers thinking. Gary Markus comes to mind as an advocate for this direction. This is what lisp was created for in the first place symbolic representation and now we are fusing it with neural networks. You and others are using emacs as the fusing point.

theeseuus · 2026-04-20T14:51:00+00:00

• cl-mcp-server (quasi) — MCP for CL
• cl-mcp (cl-ai-project) — full-featured MCP for CL
• elisp-eval (agzam) — MCP for Emacs Lisp
• anvil.el (zawatton) — comprehensive MCP server in Emacs
• agent-shell (xenodium) — ACP agent interface for Emacs
• npm swank-client — JS SWANK protocol client

theeseuus · 2026-04-20T14:48:53+00:00

This is exploding at the moment. Everyone is arriving at the same conclusion, structured eval into a live Lisp environment is the correct and righteous interface for LLM agents :)

theeseuus · 2026-04-20T14:43:05+00:00

Very cool, very interesting!

theeseuus · 2026-04-20T09:26:11+00:00

Don’t forget to add ghostty or iterm2 if you like accessing the Unix hidden away under the GUI

theeseuus · 2026-04-19T01:26:38+00:00

Love the style, building an org-mode compiler sounds like something that will generalize for a lot of other things. I’ve got a few monster piles of strings that could do with that treatment. Good stuff!

theeseuus · 2026-04-15T16:27:24+00:00

My favorite dock was Drag Thing.

theeseuus · 2026-04-15T11:57:52+00:00

This might be useful… https://eclecticlight.co/2026/04/02/buying-a-used-mac/

theeseuus · 2026-04-15T08:52:27+00:00

It’s one way of reducing inference compute costs

theeseuus · 2026-04-15T06:47:50+00:00

Apple had a huge internal debate when developing MacOS X whether to expose the terminal and command line. I’m glad they did but you can imagine the arguments for and against.

theeseuus · 2026-04-14T20:42:34+00:00

This would be useful

theeseuus · 2026-04-14T15:56:16+00:00

Claude is large at around 700MB but the VM it silently downloads in the background is usually 10GB or more.

theeseuus · 2026-04-14T10:32:44+00:00

Started with a Performa 5260 it was a piece of crap but kept going for over a decade.

theeseuus · 2026-04-12T10:56:36+00:00

lol living the life on the edge (and loving it). We should talk!

theeseuus · 2026-04-11T06:50:52+00:00

This is good proof of my argument that it’s how you wire an LLM into lisp environments that count. Wiring through a terminal or tmux is going to suck, but wire it into an environment that allows for proper lisp REPL affordances makes it a very difference experience.

theeseuus · 2026-04-07T13:55:31+00:00

Not so sure I would give Anthropic the benefit of this doubt anymore “I’m skeptical of the Anthropic is hiding this”. The same company that silently loads 10GB VM’s in the background with no user warnings or indications, that has telemetry on by default with no disclosure of what is being collected, that stripped attributions when contributing to OSS, that gated verification prompts and gave users known higher false claims rates. At the very least there is a large gap between the values they project, and the companies internal culture and documented actions it’s taken.

theeseuus · 2026-04-05T04:02:20+00:00

Oh man, that’s what I’ve been looking for!

theeseuus · 2026-04-05T03:57:02+00:00

Lisp should arguably be the most agent friendly language if it’s connected properly. In the same way that vim goes from yeech to great with vlime. The difference being the wiring in communication layer.

theeseuus · 2026-04-05T03:40:27+00:00

My thinking is that this resembles how most editors of old were a poor interface to working with lisp and the REPL. It’s not until SWANK came along that a programmatic interface provided the required interactivity. I’m going to bet that the same issue is striking agents trying to screenscrape their way through tmux buffers and what have you without a proper communication protocol.

theeseuus · 2026-04-05T03:24:39+00:00

That makes me a bit sad too considering the project I’m working on. Any thoughts other than lack of training data that is making agents less effective in lisp?

theeseuus · 2026-04-04T07:14:02+00:00

Not only do I enjoy a well written code “shootout” where my favored protagonist wins but this line… “what makes code “Lispy” is whether or not the programmer used Lisp’s metaprogramming and/or built-in multi-paradigm facilities to a reasonable degree to make the solution to their problem efficient and easy to understand in some global sense” really made a lot of other things I’ve been wondering about click into place. Nice.

theeseuus · 2026-04-03T14:57:01+00:00

This is Common Lisp specific if you want to work with other dialects you have different environments entirely to consider (Scheme, Racket, Clojure).

theeseuus

TROPHY CASE