This is part of a wry joke at the expense of LISPers and lambda calculators:
"... the heretic is chained in the dungeon where he is forced to learn Common Lisp on a Commodore 64 and interact with rapacious Lemmy-ings and Mastodonians."
@jackdaniel BBC Micro #Lisp back in 1982 (on a 6502), followed by Cambridge Lisp from about 1984, followed by Interlisp-D from 1986. I did use Harlequin's LispWorks about 1989, but not extensively. Can't remember whether Franz had REPL editing in those days, and there was an early PC Common Lisp called Golden something, but I can't remember whether it had REPL editing either.
It strikes me as really embarrassing that so many modern Common Lisp REPLs don't.
The Medley site has an experimental mirror of the source tree https://interlisp.org/src (may change) where Interlisp sources and TEdit files are available as PDFs, with the former prettyprinted and syntax highlighted.
A nice feature is bitmaps in Interlisp files are rendered as actual bitmaps like in this snippet of an address book program:
This is a #lisp machine for network protocols. Initially in pursuit of a social forum focused on link sharing.
as #startups and free projects alike rush to implement some #IETF RFC adding only 'but on the web'. I aim to define a modular protocol server which can support an arbitrary number of network protocols as a network daemon. Our POC in this endeavour will be to build an #NNTP -like protocol daemon which gateways to #IPFS storage. The content held in this system can be consumed by arbitrary clients; a web application presenting #reddit -like services would be just one of many potential clients, although it is likely that Gnus for Emacs will be the first one. https://codeberg.org/fade/callisto
@leonerd@tripleo I can only confirm this, even if currently FFI support does allow to bind #Perl to C/C++ quite easily. I find the general situation much better of other seasoned languages such as #Tcl or #Lisp, instead.
Today I got more time than expected to dedicate to the #springlispgamejam2024. I managed to refactor the game logic (still using no ECS...) to get some gameplay with collisions and randomness; and add music! (No sound effects yet...) #GNUGuile and #chickadee are very good BTW. #lisp#lispgamejam
“This is a self-contained low-power computer with its own display and keyboard that you can program in uLisp, a version of the high-level language Lisp for microcontrollers”
I'm doing some thinking about whether to learn common #lisp or #scheme and create tutorials for others at the beginning like myself.
The focus would not be on syntax or an encyclopedia of available commands or external libraries. It would be about "thinking" and decomposing problems into algorithms.
So far I like that scheme is tiny, has pretty much one syntax, leaving us undistracted from the problem to solve.
Anyway, if anybody's got any links related to SECD machines, or implementing VMs in general and/or lisp implementations for them, be sure to send it my way #lisp
I didn't know much about John Allen, the author of the classic 1978 book Anatomy of LISP. This post by a researcher who knew him well tells a bit about Allen, his work, and his passion for Lisp and computing.