We can start with working images for Squeak, Pharo, Cobalt, etc, and with
applications like Seaside, Etoys, etc. Each can be put in their own
namespaces for starter. Once they are in, a search utility will bring all
the common code to a 'Common' namespace and all the duplicated code in the
other namespaces removed. Individual developers can then use more and more
of the 'Common' code in their projects and borrow code from other
namespaces. The automatic search utility will move code to Common if the
code is use several times in different namespaces. I think the different
projects will turn out to be quite thin as time goes on.

The Global Smalltalk Image can be archive weekly so that nothing is ever
lost. Everyone has the benefit of the entire knowledge of the Smalltalk
community forever. We can develop tools to traverse the image and its
history so that reinventing should not happen. Only truly new ideas will be
coded and hopefully at a very high level.

All the best,
Aik-Siong Koh


askoh wrote:
> 
> Is this a good idea? Aik-Siong Koh
> 
> Global Smalltalk Image
> Contains everyone's code.
> Ideas are never lost.
> Easy to search everything. (Indexed for fast search).
> Remove duplications. (Automated as much as possible).
> Includes all forks all the time.
> Code growth will slow with size as reuse becomes more and more effective.
> Programming becomes more and more high level with high reuse of lower
> levels.
> Lower levels becomes more and more optimized, stable and tested.
> Automated runtime packager to make small application images.
> 
> 
> 

-- 
View this message in context: http://forum.world.st/Global-Smalltalk-Image-tp2970621p2970719.html
Sent from the Squeak - Dev mailing list archive at Nabble.com.