akater

I Have No* Blog & I Must Post

PGP: A249 61DE 3ADD 04E0 57AD CF45 9955 5CE6 F2E1 B21D

* I kinda have a blog now; it's in Russian t.me/akaterblog

Last Notes

2026-06-12 11:23:28 UTC

- reply

@nprofile…d73q
I've met at least one person who used to write Scheme for money. I'm also aware of people who write Elisp for money, but never met one in person. Magit developer got crowdfunded for a year's worth of work on Magit, full time.
@nprofile…y6jc

2026-05-27 15:49:06 UTC

- reply

@nprofile…tsag
Can you say “Scheme machine” instead? Lisp machines were never built around Scheme. And further, “virtual machine” would be much more appropriate because Lisp machines were actual hardware.
@nprofile…t3h7

2025-04-17 01:07:17 UTC

- reply

“to become actually usable and useful”
— I mean, in CL, of course.

2025-04-17 01:03:58 UTC

- reply

@nprofile…l9v9
I find CLIM exciting, ever since I learned about it (≈9 years ago). But right now my primary target is Lem — if Elisp code actually works in it, its chances to get (an additional) CLIM backend improve, I believe. I want existing Elisp code to become actually usable and useful, as quickly as possible.

2025-04-17 00:53:40 UTC

- reply

@nprofile…l9v9
Thank you. I still don't see the downside of having Common Lisp always available. I certainly want that, in Emacs, and everywhere — Emacs should be everywhere, of course, with very few exceptions.
Anyway, I'm compiling Elisp in SBCL and ECL these days. https://framagit.org/akater/cl-el/-/blob/master/el.org Not much is working right now, and even less is working right, but I think I'll get there.

2025-04-17 00:16:13 UTC

- reply

@nprofile…l9v9
What would be the downside of *not* having its own “domain specific lisp”? And what are those other grand lisp programs?
https://mastodon.sdf.org/@screwtape/114338617282391952