the general idea is to have a NewtonScript interpreter running on
Unix.


this makes sense only if we can provide a mechanism to execute
existing NewtonScript packages -- the Apple-defined format for
distributing Newton apps.

the challenge is that the Newton is designed around its persistent
storage model, and applications are written to become part of a
framework of objects, rather than standing independently.

we therefore have two options: to "install" a package each time it is
run, and discard the installation when finished, or to provide some
sort of persistent environment in which to run NewtonScript apps.


when looking today at the design of the NewtonOS, it's my opinion that
some decisions have stood the test of time:

- soups and stores
- prototype inheritence
- handwriting recognition

while other have not:

- uni-processing model
- single threaded applications
- newtonscript-only programming
- the filing model within the UI


when designing a Unix-based system to run NewtonScript applications,
it's tempting to "improve" the original design to overcome these
perceived weaknesses.


what features must be provided to allow reasonable functionality?

- GUI and application protos
- soups and stores


