Last 10% takes 90% of time. So I did 90% of the last 10% -- 81% of fun time ahead before #McCLIM release :-) Squashing relevant bugs, regressions and stuff. #lisp
Lisp Hacker
(Please try to enjoy each parenthesis equally, and not show preference for any over the others.)
@vga256 the original was developed by Jean-Marie Hullot, called "SOS Interface" and was written in Le Lisp for the early Macintosh
I just posted a video of solving Advent of Code 2025 day 3 in elisp/common lisp simultaneously. #emacs #elisp #commonlisp #lisp #adventofcode #adventofcode2025
"Lisp Style and Design" by Molly Miller and Eric Benson (Digital Press, 1990) is a Common Lisp book cited by Paul Graham in On Lisp which covers often overlooked topics. The book is now available at the Internet Archive:
https://archive.org/details/miller-and-benson-1990-lisp-style-design
RE: https://fosstodon.org/@interlisp/115643739371363748
If you always wanted to try out a Lisp Machine environment, but felt overwhelmed and didn't know where to start, the Medley Interlisp primer is for you.
The primer gently guides you into using the system and developing simple programs, even if you have no prior knowledge of Lisp. Plus, as the document also explains, you can run the actual environment.
Finally I have worked through my subtle OpenGL bugs and have working SDF font rendering via pre-loaded VBOs with precomputed UV and geometry data.
There is still a lag with pointer highlighting but the stream test stays snappy and doesn't get progressively slower with each event displayed.
I wrote a blog post, I wrote a blog post! enjoy :)
https://turtleware.eu/posts/Common-Lisp-and-WebAssembly.html
In the 1980s Interlisp-D came with a read-only remote desktop client for monitoring networked Lisp workstations, like in the screenshot. Medley Interlisp still includes the code which doesn't currently work.
https://files.interlisp.org/medley/lispusers/MONITOR.TEDIT.pdf
I would like to invite you to consider this report of designing and testing an offline computer science experience based on Lisp.
https://doi.org/10.17605/OSF.IO/KUGRN
https://www.researchgate.net/publication/397803009_The_Human_Computer_e_010_Learning_Research_Project_-Effective_Research_Problem_solving_in_class_and_school_Seminar_Michael_Schlauch_Project_documentation_What_are_the_key_characteristics_of_a_voluntar
#Lisp #Education #design-based-research #roleplay
A handy list of the main features of Common Lisp with concise descriptions and code snippets.
@amoroso the mentioned Symbolics 3600 had 36bit words with 8 bit ECC, IIRC: Imagine the costs for a few megawords of very specialized memory with lots of swap memory on disk. Which computer at that time had an high-level object-oriented operating system, commercially available? Mostly only Smalltalk machines and Lisp machines.
@amoroso They were also not widely available. They were very very expensive and I doubt that more than 10k of these machines were ever sold. The hardware was expensive, but the software was also very expensive. The early competition were UNIX Lisp systems like Allegro CL, Lucid CL and then LispWorks. But they and the hardware for them was also expensive (memory). Government money feeded the bubble. Later, after the AI crash a lot of the remaining applications were ported to C++.
@amoroso Microcode for the CPU was also implementing the low-level support which was used for multi-tasking, I/O, bitblts and other stuff. The idea was not to be the fastest in gabriel benchmarks, but to provide fast interactive response while developing large software (for that time) in a full debug mode. The whole OS, IDE and applications ran in something like a full debug mode. Fully introspective and reflective.
@amoroso he also has a lot of misses. These machines were only needed for a a few years, where there was demand of high-end research and development systems for Lisp, while other systems could not deal with Lisp runtimes of often hundreds of megabytes. Early Suns were known to have no support for GC in virtual memory and were often hanging/crashing with large memory applications.
Multi-language IDEs that interact with interpreters via protocols are now common, from classic Emacs with its inferior process protocols to VS Code with LSP and similar modern environments.
This paper described an early exploration of these ideas: a language-independend, Interlisp-based environment that interfaced with language processors over the ARPANET. In 1974.
Ryan Burnside entered the Autumn Lisp Game Jam 2025 with Interlisp Hungarian Rings, a puzzle he wrote in Interlisp. The project page provides instructions for downloading and playing the game:
We are redesigning the Interlisp bibliography for improved browsing and more informative entries. It's a work in progress and your feedback is welcome.
JSCL (#lisp to #javascript) has a live playground: https://jscl-project.github.io/
it supports a subset of CLOS, format and loop (what precisely remains to be seen EDIT: CLOS and LOOP support is extensive and better than thought. FORMAT support is minimal).
On World Digital Preservation Day 2025 Eleanor Young gave the virtual talk "The Medley Interlisp Project: Reviving a Historical Software System". The video recording and transcript are available here: