First thing, congrats to Pharo community, I observe a good trend. It may seem dumb, but it's great to have pharo executable and pharo icons. Once the image launched, my general feel is good too, though I'm not fan of multiple keys shortcuts. It stressed me to the point that I didn't realize the single key shortcuts were still active in text editor (desperately seeking cmd b+ something... when cmd + shift + N would just browse ivar references). I guess I'll get used to it. Browsing the class Object seems a bit long, I guess there's time wasted scanning the class hierarchy... Of course, there's a few things to polish. First I ran the tests, and here is what I have to say about it - there were two interactions requests, IMO, there shouldn't be any (a pop up for my name, and a menu) - there are some failures (10) and errors (3), is this expected? (see attachment) - more annoyingly, during the test, the progressbar feedback disappeared (sporadically flashing) and the TestRunner feedback too (number of succeded test updates went scarce) When I opened a FileBrowser to browse the filedOut TestRunner report, I typed *.txt as a filter and got a RegexSyntaxError nullable closure, that's surprising. There I stopped exploring the features and inquired a bit about the failures. Most failures are related to DateAndTime. I guess they occured because I was playing with image around midnight with a +01:00 offset. Early debugging let me see some highly questionable code, using negative seconds in internal representation is a recipe for trouble.. Having julianDayNumber the instance variable being different from julianDayNumber the message is also asking for trouble. Well, just wanted to share this first feedback, i think i have lot of things to discover in this image (I guess good things, but you know me, I generally report the bad first). cheers Nicolas