The idea is to design this in such a way that it "grows" towards completeness by slowly adding structures and messages via careful versioning and careful use of dynamic library plugins so that the whole project need not be recompiled completely each time a minor change is made.) With careful architecture, it could grow in strategically versioned steps where new features are added via new modules and registered to a feature list(only feature list need to be rebuilt), and be completely decoupled and test driven, since such as system is doomed to grow into an unmanageable spaghetti making it impossible to look back at very very quickly if this is not done. -- View this message in context: http://forum.world.st/Can-Pharo-VM-be-altered-to-act-like-GNUStep-as-well-tp... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.