> From: [...] Lex Spoon
> Martin Wirblat <sql.mawi at t-link.de> wrote:
> > Here are Squeak's current problems ordered by importance:
> > 
> > 1) library
> > 2) speed
> > 3) documentation
> > 4) community organization
> > 5) public relations and awareness
> > 6) language
> 
> Hmm, let me try.  My list would be something like:
> 
> 1. Stability, including stable sets of packages.
> 2. Dicing up the shared image into packages.
> 3. Documentation.
> 4. Better interfaces to the platform, especially to windowing systems
> 5. Beefing up the libraries in various ways.
> 6. Language, namespaces, ...
> 6. Public relations.

Well, if we're into lists... This lot presupposes that our intention is
to make a system that will scale to a larger number of developers, and
will attract those developers.  If those aren't the goals, this list
isn't appropriate - note that it doesn't correspond to my own wish-list,
for example.  It's also a list of goals; assume a problem corresponding
to each goal exists ;-).

1. Some way of stopping us all fighting over a single hunk of bits - the
image as it is distributed.  Call it packages, modules, sawdust,
whatever.  At present, this seems to be crippling development.

2. Sufficient speed and stability that the rest of this can be developed
without the developers getting hacked off with their toolset.  I develop
in MVC on Squeak 2.2.  It's really quick; I'd recommend a trip back in
time to anyone using the Morphic tools in a recent image!

3. Sufficient (but not excessive) documentation on the core and the
commonly-used packages so that an interested newcomer can pick this up
and use it.  This would include tutorial documentation, which is
probably the hardest part to write as it doesn't necessarily correspond
to the structure of the code.

4. Anything else.

		- Peter