Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!psuvax1!psuvm!cunyvm!ndsuvm1!mtus5!applerep
From: APPLEREP@MTUS5.BITNET
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Compatibility of stacks and Hypercard 2.0
Message-ID: <90213.175513APPLEREP@MTUS5.BITNET>
Date: 1 Aug 90 22:55:13 GMT
References: <1990Jul26.192703.894@midway.uchicago.edu> <45998@brunix.UUCP> <90213.091703SAS102@psuvm.psu.edu> <46359@brunix.UUCP>
Organization: Computing Technology Services, Michigan Technological Univ.
Lines: 12

Don't forget, also, that the ability to customize an existing stack is one
of Hypercard's greatest strenghts.  It gives the user the ability to both
utilize parts of someone else's stack in the way that best benefits them,
and to learn a great deal about stack construction.  If Hypercard stacks
were to be saved as compiled applications, I think you would probably lose
a lot of that great open-endedness that it has.

Tom Amberg
Apple Student Rep
Michigan Technological University (Go Huskies!!)

Disclaimer:  (the usual stuff)