[Moose-dev] Re: Moose and Pharo?

Now that I've read it, it makes sense what you are saying, but I also think that it would be nice if everyone would explain his point of view so we can discuss and find consensus. I'm not using Moose at the moment, but here is why I said that having development version of moose on the development version of Pharo is good: Imagine that Pharo X is released with Bloc and there is super cool Roassal 3 that works on Bloc. If Moose is following Pharo, then soon after that stable Moose Y is released with cool version of Roassal 3. On the other hand if Moose is working only on stable version of Pharo, then to get cool Roassal 3 on a stable Moose version you have to wait for longer. Please note that libraries and frameworks used in my description can be anything, it was just to make the point. Stephan's example with Seaside is good. There is also more complexity because it runs on multiple platforms, but for me it is always painful to load Seaside. I want to use Pharo 5 because it has QA, but the stable version of Seaside still uses some deprecated methods and has some classes missing. It works, but each time I load it I get warnings and it is frustrated. Cheers. Uko Sent from my iPad