Lem is evolving at a good rhythm.
I am reviewing, testing and merging pull requests nearly everydays.
It has a webview interface, multiple cursors, multiple major modes (interactive markdown code blocks), code folding (for Lisp sources), remote file editing (Tramp), a file tree and a directory mode (à la Dired), a transient pop-up window showing all available keybindings, a built-in tutorial, a spell checker, a Git interface (functional but lacking interactive rebase), org-mode support is coming, it supports many programming languages with (or without) LSP and tree-sitter, … and I am not giving a full list of new features. You can follow along on reddit.
Here’s a quicktour in 7 minutes, not even showing everything either:
The day after I recorded my video, cxxxr announced his vibe-coded Common Lisp implementation on WASM (clysm)that is able to run Lem in the browser:
- https://cxxxr.github.io/clysm/ (15MB) (Firefox ±168 and Chrome 137)
So that’s the second implementation of CL on WASM after miricl, or the third, with ECL’s ongoing work.
We also have pull requests, by a regular contributor, adding a SDL3 front-end, also vibe-coded, based on the existing (deprecated) SDL2 front-end.
So is Lem slop?
Depends on your definition I guess. It was developed for 10 years by hand, by cxxxr and the early contributors. Today a certain percent of the code-base was touched or done with LLMs.
I saw that they were first used to add language definitions, a tedious thing, based on the existing hand-designed foundations. Then contributors brought bug fixes and performance improvements. Then came new features. Tramp or the spell checker for example. I reviewed them, they are short and idiomatic. So if that was your concern I am not yet worried by code quality.
However, earth is burning.
- Common Lisp editors:
https://lispcookbook.github.io/cl-cookbook/editor-support.html
including the new
mineeditor and theOLIVEplugin for VSCode, the greatICLREPL, and more.
🕊