[squeak-dev] The future of Squeak & Pharo (was Re: [Pharo-project] [ANN] Pharo MIT license clean)

Juan Vuletich juan at jvuletich.org
Mon Jun 29 15:21:45 UTC 2009


Casimiro de Almeida Barreto wrote:
> No, it's just spinning around. Why? Just take a look at the statements 
> of Pharo and Cuis. They clearly point out what people think is wrong 
> with Squeak.org but doesn't have a single word about how to avoid the 
> situations to repeat in future.

The Cuis statement says (stuff in parenthesis added in this message):
- Close to the ideas in Smalltalk-80 and "Design Principles Behind 
Smalltalk".
    (Do not load stuff whose complexity outweighs its usefullness. Do 
not load too complex stuff)
- Include only kernel functionality.
    (Leave optional functionality out, to be included in optional packages)
- Included stuff should be in very good shape.
    (Do not load bad code)
- Include a greatly simplified version of Morphic as the main UI.
    (Do not include optional applications like Etoys. Do not include too 
complex stuff)
- Stable. Smalltalk kernel should not change much.
    (If something is not stabilized, as Unicode in Squeak, leave it out, 
to be included in optional packages)
All these are ways to avoid the problems with the software.

It also says:
- Lead by Juan Vuletich (jmv) after these principles.
This is the way to avoid the problems with the community.

Maybe all this is plain wrong for many. Maybe it will bring new 
problems. But it will indeed avoid the situations to repeat in the future.

Cheers,
Juan Vuletich



More information about the Squeak-dev mailing list