...
To me I think that it would be good to have a Moosedev and a MooseDeployment part because we have many differnt frameworks in the system

This is certainly an important topic and it warrants its own discussion.

I think we should not distinguish between MooseDev and MooseDeployment :).

I know but now Moose is a large kitchen sink.

I will discuss with the synectique guys because I think that when we deploy a tool we do not need half of Moose and after we

cry for space. So we will see what we will do. Right now I do not want to manage my own Moose but if the company needs it, then I will do it

because I'm not spending my week-ends and more just for the fun of it. I have better things to do.

With your vision Pharo would be the sum of all its projects and I want exactly the inverse: a small core and

a modular infrastructure so that people can load what they need.

Now you know like me that this is not in opposition with the other scenario ;)

I think that learning how to deploy is the best way to get the best of both scenario: (1) customed under control deployement (2) full Moose.

My vision goes like this:
- Moose is a platform that works for multiple technologies. Perhaps we can distinguish between what makes sense for Java or for a language like C#, but the differences would be small and would not warrant different distributions.

- Moose is a platform for Pharo as well, although not many are seeing it like that. This means that the tools we have with Moose should be used for analyzing Pharo.
- We could distinguish between a Pharo only distribution and the distribution for all other languages. Actually, this is what we have with the GToolkit project: a Pharo specific toolset. However, we still want to have the Pharo-specific tools inside a Java-specific distribution given that we want people to develop their own tools fast. And to debug them. And to inspect them.

We just want clients using our tools because this is even more difficult to find the other clients.

If we encounter clients that can accept to understand that they can script their own tools

this will be a different story but a modular infrastructure support both.

So we want all the Pharo specific tools in the large distribution, too.

All in all, we now go towards:
- GToolkit for everyone that wants to develop in Pharo only.
- Moose for every other language (and it includes GToolkit).

Cheers,
Doru

--
www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev