#symbolics — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #symbolics, aggregated by home.social.
-
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.
-
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.
-
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.
-
It is #Symbolics Virtual #LispMachine running "natively" on Mac M4.
-
It is #Symbolics Virtual #LispMachine running "natively" on Mac M4.
-
It is #Symbolics Virtual #LispMachine running "natively" on Mac M4.
-
It is #Symbolics Virtual #LispMachine running "natively" on Mac M4.
-
It is #Symbolics Virtual #LispMachine running "natively" on Mac M4.
-
quite the "bird"/"plane" being modeled..
https://www.youtube.com/watch?v=8RSQ6gATnQU&list=PLWRTLH_j65YganGU8ROO633CZQrAeqVTI&index=11 -
quite the "bird"/"plane" being modeled..
https://www.youtube.com/watch?v=8RSQ6gATnQU&list=PLWRTLH_j65YganGU8ROO633CZQrAeqVTI&index=11 -
quite the "bird"/"plane" being modeled..
https://www.youtube.com/watch?v=8RSQ6gATnQU&list=PLWRTLH_j65YganGU8ROO633CZQrAeqVTI&index=11 -
quite the "bird"/"plane" being modeled..
https://www.youtube.com/watch?v=8RSQ6gATnQU&list=PLWRTLH_j65YganGU8ROO633CZQrAeqVTI&index=11 -
quite the "bird"/"plane" being modeled..
https://www.youtube.com/watch?v=8RSQ6gATnQU&list=PLWRTLH_j65YganGU8ROO633CZQrAeqVTI&index=11 -
Imagine having one of these jobs back in the day.
https://www.youtube.com/watch?v=ud0HhzAK30w&list=PLWRTLH_j65YganGU8ROO633CZQrAeqVTI
-
Imagine having one of these jobs back in the day.
https://www.youtube.com/watch?v=ud0HhzAK30w&list=PLWRTLH_j65YganGU8ROO633CZQrAeqVTI
-
Imagine having one of these jobs back in the day.
https://www.youtube.com/watch?v=ud0HhzAK30w&list=PLWRTLH_j65YganGU8ROO633CZQrAeqVTI
-
Imagine having one of these jobs back in the day.
https://www.youtube.com/watch?v=ud0HhzAK30w&list=PLWRTLH_j65YganGU8ROO633CZQrAeqVTI
-
Imagine having one of these jobs back in the day.
https://www.youtube.com/watch?v=ud0HhzAK30w&list=PLWRTLH_j65YganGU8ROO633CZQrAeqVTI
-
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 -
I always liked the idea of being one of those cool Lisp programmer with the Symbolics machines doing dark wizardry on green phosphor. It looks cool, but I'm almost certain I would actually hate it. Too bad, now we can just make Google do it for us.
-
I always liked the idea of being one of those cool Lisp programmer with the Symbolics machines doing dark wizardry on green phosphor. It looks cool, but I'm almost certain I would actually hate it. Too bad, now we can just make Google do it for us.
-
I always liked the idea of being one of those cool Lisp programmer with the Symbolics machines doing dark wizardry on green phosphor. It looks cool, but I'm almost certain I would actually hate it. Too bad, now we can just make Google do it for us.
-
I always liked the idea of being one of those cool Lisp programmer with the Symbolics machines doing dark wizardry on green phosphor. It looks cool, but I'm almost certain I would actually hate it. Too bad, now we can just make Google do it for us.
-
I always liked the idea of being one of those cool Lisp programmer with the Symbolics machines doing dark wizardry on green phosphor. It looks cool, but I'm almost certain I would actually hate it. Too bad, now we can just make Google do it for us.
-
😺🐻🐰 #satire #humor #parody #cult #philosophy #spirituality #surreal #symbolics #semiotics #cat #cats #teddy #teddies #art #artificialintelligence
🔗 New story up 🌐
-
😺🐻🐰 #satire #humor #parody #cult #philosophy #spirituality #surreal #symbolics #semiotics #cat #cats #teddy #teddies #art #artificialintelligence
🔗 New story up 🌐
-
😺🐻🐰 #satire #humor #parody #cult #philosophy #spirituality #surreal #symbolics #semiotics #cat #cats #teddy #teddies #art #artificialintelligence
🔗 New story up 🌐
-
😺🐻🐰 #satire #humor #parody #cult #philosophy #spirituality #surreal #symbolics #semiotics #cat #cats #teddy #teddies #art #artificialintelligence
🔗 New story up 🌐
-
😺🐻🐰 #satire #humor #parody #cult #philosophy #spirituality #surreal #symbolics #semiotics #cat #cats #teddy #teddies #art #artificialintelligence
🔗 New story up 🌐
-
The always awesome Asianometry channel covered Lisp, early AI, and the Lisp Machines earlier this year:
“A Cult AI Computer’s Boom And Bust”, Asianometry (https://m.youtube.com/watch?v=sV7C6Ezl35A).
#Video #Asianometry #Lisp #AI #LispMachines #Symbolics #YouTube
-
The always awesome Asianometry channel covered Lisp, early AI, and the Lisp Machines earlier this year:
“A Cult AI Computer’s Boom And Bust”, Asianometry (https://m.youtube.com/watch?v=sV7C6Ezl35A).
#Video #Asianometry #Lisp #AI #LispMachines #Symbolics #YouTube
-
The always awesome Asianometry channel covered Lisp, early AI, and the Lisp Machines earlier this year:
“A Cult AI Computer’s Boom And Bust”, Asianometry (https://m.youtube.com/watch?v=sV7C6Ezl35A).
#Video #Asianometry #Lisp #AI #LispMachines #Symbolics #YouTube
-
The always awesome Asianometry channel covered Lisp, early AI, and the Lisp Machines earlier this year:
“A Cult AI Computer’s Boom And Bust”, Asianometry (https://m.youtube.com/watch?v=sV7C6Ezl35A).
#Video #Asianometry #Lisp #AI #LispMachines #Symbolics #YouTube
-
Wise, sobering words 😞:
“The Lost Cause Of The Lisp Machines”, Tim Bradshaw (https://www.tfeb.org/fragments/2025/11/18/the-lost-cause-of-the-lisp-machines/).
Via HN: https://www.tfeb.org/fragments/2025/11/18/the-lost-cause-of-the-lisp-machines/
On Lobsters: https://lobste.rs/s/rifpe8/lost_cause_lisp_machines
#Lisp #LispMachines #Symbolics #Nostalgia #Programming #IDE #Hardware