Sorry Stef but I disagree. PLEASE don't misunderstand me. I know a lot of
very good people have worked and is still working in Nile project. So, I am
sure it is an excellent product.

However, I don't think it should be in Dev image. Dev image is for
"Developers". So, we put tools like NewInspector, RoelTyper, E and
OCompletion, Refactoring, etc. But why Nile ?

I am not agree this is neither a way to push Nile to be used. It is no
difference if you already have the code in the image or not, it is just one
click of difference (as you have the Nile-All). Even if it where the case, I
think it should be in Core image.  The way to push a project to be used is
to write documentation, tutorials, show the benefits over other
implementations....and so on.

If Moose use it, ok, put it as a dependency. Now you have a Metacello
configuration for Moose :)
I mean, in SqueakDBX we use FFI and we don't put in the image. Seaside uses
Slime and it is not in the image.

Just my opinion. I hope no one feels offended.

What others think about this ?

Cheers

Mariano

On Sun, Jan 3, 2010 at 11:02 AM, Stéphane Ducasse <[email protected]
> wrote:

> Nile is in dev because it should be progressively use to replace existing
> streams.
> For example in Moose some important collection extensions depend on it.
>
>
> > Does another package of the dev image depends on Nile?  If not, I don't
> understand why it is part of the dev image. I see it as any other external
> package but not a "dev tool" that should be included.
> >
> > Thanks
> >
> > Mariano
> > _______________________________________________
> > Pharo-project mailing list
> > [email protected]
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to