On 03.12.2008, at 22:10, Stéphane Ducasse wrote:
The problem is that removing etoys is not a clean thing. We have
first methods
that are needed to be changed for both removing etoys *and*
polymorph. So that's
why the packages need to be in the pharo repository.
In general, if you think about code quality or modularity in the
context of Squeak:
Think about the worst you can think of, then multiply it by a
factor of 100. Then
you get to what the current state is in Squeak. It's a mess of epic
proportions...
Not that quite :)
:-)
It is getting better every day. :)
And I will really get better.
Now this is true that etoy is a great idea
Yes!
with a bad implementation.
Maybe it's not even the implementation... every implementation has
it's problems.
I think in hindsight, the problem is that they just never cleaned up.
And with that,
they just stopped to invest in the future.
It was always "the two week prototype that will be replaced soon". And
10 years
later, it was a mess (and there was no replacement, of course).
There is a lot that one can learn from that.
(And I hope that viewpoints did a good postmortem analysis of the
etoys project so that
they can incorporate these lessons into the things that they are
working on right
now...)
Marcus
--
Marcus Denker -- [EMAIL PROTECTED]
http://www.iam.unibe.ch/~denker
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
