Maybe I missed it, but I don’t recollect Kay using this generalization before.
Maybe I missed it, but I don’t recollect Kay using this generalization before.
In computer terms, Smalltalk is a recursion on the notion of computer itself. Instead of dividing "computer stuff" into things each less strong than the whole—like data structures, procedures, and functions which are the usual paraphernalia of programming languages—each Smalltalk object is a recursion on the entire possibilities of the computer. Thus its semantics are a bit like having thousands and thousands of computers all hooked together by a very fast network. Questions of concrete representation can thus be postponed almost indefinitely because we are mainly concerned that the computers behave appropriately, and are interested in particular strategies only if the results are off or come back too slowly.
That's from the start of the HOPL paper, 1993. I would be surprised if he didn't use this image long before that.
As I digress, if you have to divide up a workload, you can start with a language based on message passing or you can implement message passing in some other language. The danger with implementing it is to not recognize that's what you're doing.
Have you heard of anything like that?