#symbolics — Public Fediverse posts

And I think that's the important bit. It hits a sweet spot for functionality and ubiquity, _and_ it is freeform enough that I don't have to think in advance how I want to use it—I literally adapt queries and files to the project I'm working on, as I go.

It's a "whatever" box in the context of, "I'm down for whatever you're into, boss" box. But it will do "whatever", deterministically. By cleverly combining pretty, extensible, and customizable rendering of the results of queries over an ad-hoc #markdown-based datastore.

Now, I know that (especially after reading the mention of #symbolics #lispmachine in the first post), someone's gonna say "but emacs!". And sure, follow your bliss, not stepping into that one. Suffice it to say, I'm well past mid career and have tried to love Emacs, perennially, since I started. I have accepted that it meets neither my workflow nor aesthetic needs (and I'll thank you for trusting me on that).

I thought, for a while, that maybe I could make #VSCode be the environment I could use to do this, what with MarkdownPreviewEnhanced and other plugins. But that is an IDE optimized for developing _other_ applications, which is different from building a boat whilst sailing it.

Anyway, this is turning into something that should be a blog post, and I don't expect anyone will read this far anyway, but I thought I'd stop and give credit where credit is due. #obsidian is the closed thing to an ad-hoc productivity operating system I've ever used, and it's quietly become one of the most important pieces of software I have.

Nicely done, @obsidian and community. And nicely done, @gruber and #aaronschwartz and everyone who's made #markdown what it is.

And I think that's the important bit. It hits a sweet spot for functionality and ubiquity, _and_ it is freeform enough that I don't have to think in advance how I want to use it—I literally adapt queries and files to the project I'm working on, as I go.

It's a "whatever" box in the context of, "I'm down for whatever you're into, boss" box. But it will do "whatever", deterministically. By cleverly combining pretty, extensible, and customizable rendering of the results of queries over an ad-hoc #markdown-based datastore.

Now, I know that (especially after reading the mention of #symbolics #lispmachine in the first post), someone's gonna say "but emacs!". And sure, follow your bliss, not stepping into that one. Suffice it to say, I'm well past mid career and have tried to love Emacs, perennially, since I started. I have accepted that it meets neither my workflow nor aesthetic needs (and I'll thank you for trusting me on that).

I thought, for a while, that maybe I could make #VSCode be the environment I could use to do this, what with MarkdownPreviewEnhanced and other plugins. But that is an IDE optimized for developing _other_ applications, which is different from building a boat whilst sailing it.

Anyway, this is turning into something that should be a blog post, and I don't expect anyone will read this far anyway, but I thought I'd stop and give credit where credit is due. #obsidian is the closed thing to an ad-hoc productivity operating system I've ever used, and it's quietly become one of the most important pieces of software I have.

Nicely done, @obsidian and community. And nicely done, @gruber and #aaronschwartz and everyone who's made #markdown what it is.

@screwlisp

You can pick up the document 'Signalling and Handling Conditions' from this index page:

http://nhplace.com/kent/ZL/

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

You can pick up the document 'Signalling and Handling Conditions' from this index page:

http://nhplace.com/kent/ZL/

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

#lisp #pascal #symbolics #genera #niklauswirth and we can call PASCAL procedures/functions from Lisp

As one can see, the integers in Symbolics PASCAL then are also extended to bignums ...

#lisp #pascal #symbolics #genera #niklauswirth then we can call Lisp functions from PASCAL..

#lisp #pascal #lispmachine #symbolics #niklauswirth The Zmacs editor had a syntax-aware PASCAL mode. One could also run PASCAL programs from the Lisp Listener (aka REPL). The debugger than understood PASCAL stack frames, could display the source code and execute PASCAL snippets...

I wonder what Wirth would have to say about it. He was developing similar computer systems: Lilith with Modula 2 and Ceres with Oberon.

#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...

40 days left to the submission deadline of #EuropeanLispSymposium (#ELSConf) in #Amsterdam:

🧷 (Friendica) https://libranet.de/display/0b6b25a8-1763-a88a-e526-72b275177682

🦎 (Matrix) https://matrix.to/#/!gqlYAZsfzSnmFNEHAT:magdeburg.jetzt/$z7kGECRQluF1iZzNhW-0I1e3lUmg-pff8PcAh96gox4

🦎 (Telegram) https://telegram.me/FamilyOfLisp/309

🌺

🏷️ #Lisp #Scheme #CommonLisp #Clojure #Racket #Emacs #ACL2 #AutoLisp # ISLisp #DylanLang #SKILL #Hy #Shen #Carp #Janet #uLisp #Picolisp #Gamelisp #TXR #InterLisp #Medley #OpenGenera #Symbolics #ThinkingMachines #ConnectionMachine #MultiLisp #AMOP #CLOS #SICP #PAIP #AIMA #Lambda #CLtL2 #HTDP

40 days left to the submission deadline of #EuropeanLispSymposium (#ELSConf) in #Amsterdam:

🧷 (Friendica) https://libranet.de/display/0b6b25a8-1763-a88a-e526-72b275177682

🦎 (Matrix) https://matrix.to/#/!gqlYAZsfzSnmFNEHAT:magdeburg.jetzt/$z7kGECRQluF1iZzNhW-0I1e3lUmg-pff8PcAh96gox4

🦎 (Telegram) https://telegram.me/FamilyOfLisp/309

🌺

🏷️ #Lisp #Scheme #CommonLisp #Clojure #Racket #Emacs #ACL2 #AutoLisp # ISLisp #DylanLang #SKILL #Hy #Shen #Carp #Janet #uLisp #Picolisp #Gamelisp #TXR #InterLisp #Medley #OpenGenera #Symbolics #ThinkingMachines #ConnectionMachine #MultiLisp #AMOP #CLOS #SICP #PAIP #AIMA #Lambda #CLtL2 #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

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:

→ https://t.me/FamilyOfLisp 🦎

🌺

🏷️ #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