On 22-06-15 16:49, Yuriy Tymchuk wrote:
The point is that I can take my 2 year old Ruby
project, load gems and it works. When I take my 2 month old Pharo project that depends on
Roassal (this is not only about Roassal, I just have a concrete case) - it breaks.
Pharo itself is not yet managed with configurations, and has AFAIK a
much higher change rate
than Ruby. I have been a lot less lucky with older Ruby stuff, combining
stuff from different eras
That makes it essential not to depend on the numbered versions, as you
know that they will
need to be patched to keep working on a moving target.