Tools need time to mature

as the English say you cannot have an omelette without braking some eggs

If as you say "left naked in cold desert" is what it takes to push Pharo forward as fast as possible without compromising good design , then give me all the pain I can take it.

Fact is Pharo would be nowhere near to what it is today without the work of Moose team.

However as I am saying always we need more documentation, tools loose their moldability the less documented they are. To paraphrase another person " Documentation is not an obligation but is a necessity for success" . I love these blog posts but I would be willing to sacrifice some of the moldability to get documentation on how to use the tools and extend that goes far beyond a handful of blog posts. Though my recent effort to learn Unreal Engine which is made by team hundrends of time larger than the Moose team shown me that more people != more / better documentation. Modern software is suffering from 2 big curses

a) bad design, which was bad at the start but none never dared to improve it in order to not brake backward compatibility or familiarity
b) and lack of documentation , good or bad.

With Moose at least we have got rid of the first one.

On Sun, Jun 5, 2016 at 11:02 AM Nicolas Anquetil <> wrote:


I beleive the complains were not about the usefulness of moldability,
but rather the stability of the tools.

The debugger is a central piece of Pharo and when it breaks we are left
naked out in the desert (a very cold one).


On 04/06/2016 18:45, Tudor Girba wrote:
> Hi,
> There were a couple of emails in the recent period that questioned the usefulness of moldability (the ability of developers to customize their tools deeply and inexpensively). More specifically, the question was about the moldability of the GTDebugger.
> I put together a couple of thoughts of why we think that moldability is actually a competitive advantage:
> Please read it and provide feedback.
> Cheers,
> Doru
> --
> "Reasonable is what we are accustomed with."
> _______________________________________________
> Moose-dev mailing list

Nicolas Anquetil
RMod team -- Inria Lille

Moose-dev mailing list