An ad for Smalltalk/V from the 1986 Byte magazine.

Marketing of "AI" hasn't changed much in the last 40 years.

"Watching someone use an AI workstation is a vision of what the computer was meant to be. Fingers dance across the keys as windows dilate, shift, overlap, and disappear on the bit-mapped display. ... The interface vanishes, man and machine are one. Smalltalk/V brings that experience to your IBM-PC."
#smalltalk #ai

An ad for Smalltalk/V from the 1986 Byte magazine.

Marketing of "AI" hasn't changed much in the last 40 years.

"Watching someone use an AI workstation is a vision of what the computer was meant to be. Fingers dance across the keys as windows dilate, shift, overlap, and disappear on the bit-mapped display. ... The interface vanishes, man and machine are one. Smalltalk/V brings that experience to your IBM-PC."
#smalltalk #ai

This 1988 paper reports on Smalltalk-80 for exploratory programming and fast prototyping at Tektronix.

Standard software engineering uses programming to implement a given specification. In contrast, exploratory programming is writing the specification.

https://dl.acm.org/doi/abs/10.1145/51607.51614

Some of the parallels the paper draws to Interlisp-D are not entirely accurate.

https://groups.google.com/g/lispcore/c/G9ozbhT2OnQ/m/-XF_Ufm6CAAJ

#smalltalk #interlisp #retrocomputing

Anyone seen an #ActivityPub library written in #Scheme (any flavor) or #Smalltalk ?

I'm not finding any sign of either.

No idea about #smalltalk

found this:

https://live.exept.de/doc/online/english/programming/contexts.html#HOMECONTEXT

> This is one of the most fundamental differences between Smalltalk and most other programming languages:

> in Smalltalk, a context behaves just like any other object, in that it is not destroyed, IFF there are still references from other objects to it. (typically, these are blocks)

A bit like #Forth - moved away but not forgotten (if I get it right)