Name: rf98795 Date: 01/11/2000



Come up with a better code packaging model than Jar files. Keeping each class as
a separate standalone entity wastes huge amounts of space with duplicate copies
of class metadata (megabytes of it in classes.zip alone) and slows down load/
launch time by requiring a lot of runtime binding that could have been done at
build time. (Something like the "mclass" format used by JavaOS would be an
improvement.) Tools to help order the classes and/or methods to mimic known usage
patterns would help launch time and memory usage.

======================================================================