Let me put a last comment before going to bed.
I think that you are unfair because
- if you had a look at the list of features in 1.3 you will see that we
removed a lot of bad code,
- then if you look at the data that marcus sent recently, you will see
that the image size did not change that much and that most of the space
is taken by monticello timestamp,
- finally I do not buy this growing argument because such argument
already killed us when we were doing squeak. I prefer 5 nice little classes
with
a superclass than a fat one.
It is easy to judge other work, but I can tell you that we are concerned about
size and quality much more than average people.
I'm mainly doing pharo on my free time and I'm spending a lot of energy in
making it the best system I dream about.
Now when is the last time that you said to us: guys you are doing a good job?
Have a look at your emails and you will be surprised. Sometimes positive
feedback is much better than absence of negative ones.
Stef
>
> IMHO, the goal of Pharo should be to provide a minimal Smalltalk
> system where people Pharo can load what they need. Instead Pharo keeps
> on growing. I would prefer a system where I can decide myself what
> libraries and tools I want to use. I am sure that the current
> Announcement implementation can be fixed, but does it really make
> sense that the core team bothers about something that could be
> external?
>
> Lukas
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
>
