Squeak as (and) "Das Glasperlenspiel"

Kokan kokan at acm.org
Mon Dec 27 13:00:42 UTC 1999


Thanks Henrik.
I think that your list is the answer for 1). Regarding 3), I can say that I am
familiar with AOP effort and some other efforts related to it.
Kokan

Henrik Gedenryd wrote:

> Kokan wrote:
>
> > 1) "Why the Computer Revolution hasn't happened yet?" (Alan's last
> > year's talk
> > at CMU): Is there a transcript of it or something like that? If not,
> > what would be
> > Squeak's role in helping with it (Computer Revolution)?
>
> Marcus Denker posted these a while ago:
>
> S P A C E W A R Fanatic Life and Symbolic Death Among the Computer Bums
> by Stewart Brand http://www.wheels.org/spacewar/stone/rolling_stone.html
> This is the famous "Rolling Stone" article about Xerox PARC from 1972
>
> The Xerox "Star": A Retrospective
> http://www.best.com/~curbow/xerox/retrospect/
>
> Alan Kay: The Computer Revolution Hasn't Happened Yet!
> http://www.educause.edu/conference/e98/webcast98.html
>
> Alan Kay: Software Design, the Future of Programming and the Art of Learning
> Educom Review March/April 99
> http://cause-www.niss.ac.uk/ir/library/html/erm99027.html
>
> Wired brings together two legendary minds: Alan Kay and Danny Hillis.
> http://www.wired.com/wired/archive/2.01/kay.hillis_pr.html
>
> Revealing the Elephant: The Use and Misuse of Computers in Education
> http://tolearn.net/marketing/kay1.htm
>
> Alan Kay: Powerful Ideas Need Love Too!
> http://el.www.media.mit.edu/groups/el/events/love-too.html
>
> The Way We Were
> http://www.syllabus.com/archive/PreSyll/Syllabus_Issue_24-_September_1992_
> Distance_Education/The_Way_We_Were.txt
>
> A bicycle for the mind:
> http://cispom.idbsu.edu/is120erickson/webdoc/kay.htm
>
> > 2) Finding aha vectors (Alan Kay and 'HOPL II - Closing Panel'):
>
> Can't help you with this one, but it sounds interesting.
>
> > 3) What would be a Second Generation MOP? Third, ...? Would it go beyond
> > the
> > approach in 'The Art of the Metaobject Protocol'?
>
> Don't know if this is the answer you were looking for, but a MOP could be
> described as a design which allows the implementation of one Aspect (as in
> AOP) to be replaced by the MOP user. The protocol provides the appropriate
> interfacing points for hooking up a new aspect version; one might say that
> the protocol is designed to use the ordinary language facilities as an
> Aspect Weaver for weaving the new aspect version into the code.
>
> For references to these issues, see the AOP reading recommendations on the
> Swiki. Especially the Czarnecki chapter which is a very good up-to-date
> summary of all the related work directions, with fresh insights.
>
> http://www.prakinf.tu-ilmenau.de/~czarn/aop
>
> hth,
> Henrik





More information about the Squeak-dev mailing list