Tudor Girba-2 wrote
You would recommend 3.0 even for production systems? I certainly do recommend it. I am using it since 3 months in production, and for my purposes (mainly using Moose for various analyses), it works perfectly.
I debated whether to post this, since I certainly do not want to discourage people from porting, or take away any enthusiasm for the upcoming release, but thought it was an important user experience... I took the seemingly unanimous advice from the Spotlight thread, and tried to work in 3.0. The first time I brought up a debugger (which is a frequent occurrence in my workflow), I tried to DoIt "self selectedItem", and the debugger replied that it did not know the variable selectedItem and would I like to create an instance/temporary variable⦠huh?! I quickly ran into a few more slowdowns and annoyances (like all-repos-shown-in-MC-browser). So I was in the position that I had invested part of my limited time window getting set up on 3.0, only to figure out that I couldn't do something essential. Even to report the bug would've eaten up more time. I slunk back to 2.0 and got back to work for the time I had left. Do we want 3.0 to be banged on as much as possible? Yes! Is it amazingly stable given the breath and depth of changes to core? Yes! But I don't think the decision is a slam dunk no-brainer just yet⦠----- Cheers, Sean -- View this message in context: http://forum.world.st/Porting-to-Bleeding-Edge-was-Spotlight-Demo-tp4734028.... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.