24 Sep
2015
24 Sep
'15
9:33 p.m.
Pharo is very stable. Running in production without problems.
It takes a while to get things working on a new version of course.
Pharo4.0 is out since just a couple of months, of course all packages
aren't aligned.
I am using Pharo3.0 for commercial solutions and Pharo5.x for learning.
But you are right that configurations have to be rock solid.
I've found that #stable may not be so #stable and that it would be better
to load '1.2.3' instead.
The issue is that some dependencies are on #stable or similar symbols that
change and are giving headaches.
Phil
On Thu, Sep 24, 2015 at 7:14 PM, Volkert <volkert(a)komponentenwerkstatt.de>
wrote:
You are right. But it is not Roassal alone ...from a
User (f.e. a
newcomer) perspective it is always bad, if things not work ...and if things
not work, the "Pharo Ecosystem" so is not so cool anymore. So it is
relates to "Pharo".
I like the pace the "Pharo" Development moves forward, but i am afraid you
will lose potential users, if the things break all the time.
Volkert
PS: Yes i love Pharo ... and i hope that one day i can make money with it
:-)
On 24.09.2015 18:14, Peter Uhnák wrote:
Clicking on Proceed should install it, only examples will be broken.
This is currently being also discussed in another thread
http://forum.world.st/Problem-Loading-Roassal-2-development-in-Pharo-4-td48…
Too bad that Pharo is so instable ...
I don't see how this is related to Pharo.
Peter
_______________________________________________
Moose-dev mailing
listMoose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev