#lispmachine — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #lispmachine, aggregated by home.social.
-
👾 The lost cause of the Lisp machines
｢ The common idea was that the arrival of RISC machines had killed it, but in fact machines like the Sun 3/260 in its ‘AI’ configuration were already hammering nails in its coffin ｣
https://www.tfeb.org/fragments/2025/11/18/the-lost-cause-of-the-lisp-machines/
-
You can pick up the document 'Signalling and Handling Conditions' from this index page:
It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.
In spirit, it was much the same. The biggest differences are:
* The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').
* The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.
* The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.
* Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.
* The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.
There are other differences as well.
#Zetalisp #LispMachine #LispMachines #Symbolics #LispM
#ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
#InternetArchive #Bitsavers -
You can pick up the document 'Signalling and Handling Conditions' from this index page:
It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.
In spirit, it was much the same. The biggest differences are:
* The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').
* The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.
* The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.
* Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.
* The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.
There are other differences as well.
#Zetalisp #LispMachine #LispMachines #Symbolics #LispM
#ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
#InternetArchive #Bitsavers -
You can pick up the document 'Signalling and Handling Conditions' from this index page:
It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.
In spirit, it was much the same. The biggest differences are:
* The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').
* The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.
* The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.
* Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.
* The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.
There are other differences as well.
#Zetalisp #LispMachine #LispMachines #Symbolics #LispM
#ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
#InternetArchive #Bitsavers -
You can pick up the document 'Signalling and Handling Conditions' from this index page:
It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.
In spirit, it was much the same. The biggest differences are:
* The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').
* The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.
* The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.
* Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.
* The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.
There are other differences as well.
#Zetalisp #LispMachine #LispMachines #Symbolics #LispM
#ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
#InternetArchive #Bitsavers -
You can pick up the document 'Signalling and Handling Conditions' from this index page:
It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.
In spirit, it was much the same. The biggest differences are:
* The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').
* The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.
* The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.
* Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.
* The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.
There are other differences as well.
#Zetalisp #LispMachine #LispMachines #Symbolics #LispM
#ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
#InternetArchive #Bitsavers -
@screwlisp Thought you would be interested in this.
On the ex-Symbolics employees mailing list somebody posted a link to a "history of the Lisp machine".
https://youtu.be/sV7C6Ezl35A?si=S4uh4-JXKC2_7lOR
It's kind of long and so I didn't watch the whole thing, but just skipped around a little bit. Somebody else who did watch it said,
'Fascinating exposition. Given his mispronunciations of "CADR" and "Macsyma", it's clear that he wasn't in the room where it happened, nor spoke to anyone who was. But I can't quarrel with his research or cause-and-effect analysis of both the industry as a whole and Symbolics in particular.'
-
The document preparation system of Symbolics Lisp Machines consisted of two main hypertext tools, the Concordia authoring environment and the Document Examiner documentation browser and delivery interface. These papers describe the tools.
Supporting Document Development with Concordia
https://archive.org/details/smbx-concordia-paper-1988Document Examiner: delivery interface for hypertext documents
https://dl.acm.org/doi/abs/10.1145/317426.317448 -
Back in the 1980s, when my then-office-mate was developing the Japanese product for the Symbolics lisp machine, we had an electronic version of this.
It was a big pad, about 50cm x 50cm, with a stylus to pick out individual characters. This was for kanji; the hiragana and katakana were handled separately.
To watch him use it was amazing... and slow.
-
Symbolics lisp machine demo 1990
-
#lisp #commonlisp #lispworks #symbolics #lispmachine
Made the KR frame system from the UIMS Garnet for two Common Lisp implementations work: LispWorks 8 and Portable Genera. I used this version: https://github.com/ury-marshak/kr
Typical problem porting code:: the initial value for structure slots is undefined in CL. The code assumes NIL.
Attached a screenshot of the KR examples in Portable Genera, a Virtual Lisp Machine on an Apple Mac mini with M4 Pro.
-
Prehistoric AI, OpenBlade's relative
#unix_surrealism #lispmachine #openblade #openbsd #technomage #comic
-
@amoroso #symbolics #genera naturally also has graph drawing features. Attached screenshot shows a simple example. In the Listener (-> #lisp #repl) I define a new command Show Flavor Tree. It displays the inherited Flavors. Flavors are early classes on the #lispmachine. The Listener is also a drawing plane. The command takes the name of a flavor class, then calls the graph formatter with arguments. PRESENT-FLAVOR prints the flavor and makes it mouse sensitive.
-
#lisp #commonlisp #lispmachine #genera
Then checking the list of compiler warnings, using the Zmacs command „Edit Compiler Warnings“.
-
#lisp #commonlisp #lispmachine #genera
Compiling the ALEXANDRIA library on a Lisp Machine, actually using ASDF.
-
@amoroso #lisp #commonlisp #lispmachine #symbolics #genera
2) I've compiled the LOOP alternative ITERATE (written by Jonathan Amsterdam) on the VLM. It actually works. ITERATE has even more features than LOOP, but uses a more Lisp-like syntax.In the right X11 window there is a Zmacs and a Lisp Listener. The left X11 window is from the same VLM, but displays the documentation browser in its own X11 window. The documentation content comes from another VLM.
-
@amoroso
#lisp #commonlisp #lispmachine #symbolics #genera
1) Thanks, I just updated my Genera to the latest release 9.0.6. The installation is slightly unusual. It's a virtual lisp machine (VLM), here running on a Mac with an M1 Pro cpu. UI is via X11, using the XQuartz application. The VLM talks to another VLM on the network, which provides various server functionality. But it also has its own file system, which is actually a Lisp Machine File System (LMFS). -> 2) -
@amoroso #genera #lispmachine #lisp #commonlisp
Same for Symbolics Genera:
-
#lisp #lispmachine #symbolics #genera #pascal #niklauswirth Niklaus Wirth's PASCAL made it to unusual systems: Here is a screenshot of a Lisp Machine, browsing the original Pascal User Manual and Report, but in a hypertext browser, with a PASCAL implementation loaded...
-
-
The #Telegram and #Matrix groups named #FamilyOfLisp are now synchronized (bridged):
🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt
The two groups are for friendly exchange and dialogue on topics related to the Family of #Lisp #programming languages.
🌺
🏷️ #Scheme #CommonLisp #Racket #Clojure #DylanLang #ELSConf #AMOP #CLOS #InterLisp #OpenGenera #LispMachine #Medley #ConnectionMachine #Symbolics #AutoLisp #MacLisp #ZetaLisp #EuLisp #ISLisp #CLHS #SICP #AIMA #CLtL2 #PAIP #HTDP
-
The #Telegram and #Matrix groups named #FamilyOfLisp are now synchronized (bridged):
🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt
The two groups are for friendly exchange and dialogue on topics related to the Family of #Lisp #programming languages.
🌺
🏷️ #Scheme #CommonLisp #Racket #Clojure #DylanLang #ELSConf #AMOP #CLOS #InterLisp #OpenGenera #LispMachine #Medley #ConnectionMachine #Symbolics #AutoLisp #MacLisp #ZetaLisp #EuLisp #ISLisp #CLHS #SICP #AIMA #CLtL2 #PAIP #HTDP
-
The #Telegram and #Matrix groups named #FamilyOfLisp are now synchronized (bridged):
🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt
The two groups are for friendly exchange and dialogue on topics related to the Family of #Lisp #programming languages.
🌺
🏷️ #Scheme #CommonLisp #Racket #Clojure #DylanLang #ELSConf #AMOP #CLOS #InterLisp #OpenGenera #LispMachine #Medley #ConnectionMachine #Symbolics #AutoLisp #MacLisp #ZetaLisp #EuLisp #ISLisp #CLHS #SICP #AIMA #CLtL2 #PAIP #HTDP
-
And said #portable / #smartphone should use #asynchronous (#SelfTimed) integrated circuites whereever possible for #resource #efficiency. :)
🌺
-
If you would like to come over to a friendly group on Telegram focused on the programming languages in the #FamilyOfLisp — please feel welcomed to join!
We are here:
🌺
🏷️ #Lisp #Scheme #CommonLisp #Racket #InterLisp #Clojure #BaLindaLisp #Hy #ELSConf #ZetaLisp #LispMachine #ConnectionMachine #ThinkingMachines #Emacs #AutoLisp #CLOS #AMOP #SICP #CLtL2 #PAIP #AIMA #PCL #Symbolics #Genera #DylanLang #LFE #ISLisp #Arc #Janet #Jank #OnLisp #HTDP #CLHS #EuLisp
-
@lispnik @lojikil @anticomputer
By ›the thick blue book‹, do you mean ›Lisp Lore‹?
→ https://t.me/FamilyOfLisp/389
🌺
🏷️ #LispMachine #InterLisp #LispLore #ISLisp #CommonLisp #Picolisp