Run 2 images and Monticello. --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Pharo Consortium Member - http://consortium.pharo.org/ Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller On Mon, Dec 2, 2013 at 4:35 PM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
On 02 Dec 2013, at 16:24, Sean P. DeNigris <sean@clipperadams.com> wrote:
Uko2 wrote
Shouldnât we develop our tools in a more friendly way?
That would be fantastic. This thread is very interesting!
And, I just want to remind everyone that Pharo 3.0 is unreleased... Do not expect it to be stable,
Itâs not about stability of pharo 3, it about concurrency. And itâs the same problem in 1.2, 1.3, 1.4, 2.0. I can write ruby code while running tests, but I cannot do that in Pharo. This thread doesnât seem to have any reason, so I should just apologise for creating it because of frustration and ask everyone to stop discussing this :)
although it is remarkably so for the amount of deep changes that have been made. Maybe that has lulled us into a false sense of security/expectation. Remember, caveat emptor until it is released, when there obviously shouldn't be any changes which might introduce this kind of bug.
----- Cheers, Sean -- View this message in context: http://forum.world.st/Responsible-development-tp4726686p4726749.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.