And for prolog I have to use the most expensive opus, which really should be a haiku task. Prolog is so simple. Still didn't get my solvers to work right
Writing Lisp is AI resistant and I'm sad
101–104 of 104 posts
Re: Writing Lisp is AI resistant and I'm sad
#102I have been using AI to write Clojure code this past half year. The frontline LLM has no problem with writing idiomatic Clojure code. Both Codex and Claude Code fix their missing closing parentheses quickly. So I won't say "Writing Lisp is AI resistant". In fact, Clojure is a great fit with AI coding agent: it is token efficient, and the existing Clojure code used for training are mostly high quality code, as Clojure…
But we don't hear of famous AI written in lisp. It's like below the notice-radar.
Lisp was invented for AI development, just the symbolic GOFAI kind.
Re: Writing Lisp is AI resistant and I'm sad
#103If you think lisp is bad try jai. It's even worse. It even makes syntax errors, that too a language looking similar to c.
Re: Writing Lisp is AI resistant and I'm sad
#104Earlier quoted context omitted.
Came to post exactly this, except it’s got me using emacs again. I led myself into some mild psychosis where I attempted to mimic the Acme editor’s windowing system, but I recovered
Yeah, and all the little quirks here and there I had with emacs or things that I wish I had in workflow, I can just fix/have it without worrying about spending too much time (except sometimes maybe). The full Emacs potential I felt I wasn't using, I'm doing it and now I finally get it why Emacs is so awesome. E.g. I work on a huge monorepo at this new company, and Emacs TRAMP was super slow to work with. With help of…
> Emacs TRAMP was super slow to work with. With help of Claude, I figured out [...]
Out of curiosity, did it advise you to configure auto-save and backup such that they write their files under ~/.emacs.d, rather than in the same directory alongside the (with Tramp, potentially remote) file they're about? Especially with vanilla Emacs, that's always the first place you want to look when you see freezes doing file operations on a remote host over a slow or flaky link.
I believe I first added that change to my .emacs in 2010 or 2011, and as far as I can recall, it was the only change I ever needed to make to address Tramp being slow sometimes.