This approach of swapping out inactive classes have two big problems:
- The granularity is too high: the class. As soon as only one method is invoked, the whole class is recovered.
- It is very common to recover all classes doing a simple action. For example, searching for implementors or senders of a certain method. Because of this, when you are developing in your Smalltalk image is very likely that all classes are recovered in less than 5 minutes of work. It is not useful. Browsing or editing code seems not to be a problem, thus. Maybe this approach has more sense in production images rather than development.