which os do you use? 2013/3/28 Yanni Chiu <[email protected]>
> On 27/03/13 10:24 AM, Esteban Lorenzano wrote: > >> >> Here in Pharo headquarters we are shock that there are just 10 new bugs >> reported for 2.0 after the release... >> So... I wonder... is that because we made a really cool release, or just >> because nobody is using it? >> > > Just before the release I loaded up my project, and did a quick check to > find that everything looked fine - except that I would have to migrate to > Fuel-1.9. > > I had noticed that package loading seemed extremely slow, but did not look > further into it. I think I saw mention that it's due to some usage of > #become:, during the compiling of code. Based on build times (of just > loading the rough equivalent code), it seems about 3 times slower to do a > build on a Pharo-2.0 vs. Pharo-1.4. > > The slowness is not just an annoyance, because I actually compile code in > my application - it's just compiling getters and setters. I've not got > enough working yet to see whether it's going to adversely affect the > usability (it could make startup time too slow). > > Another thing I've noticed is occasional sluggishness in the UI. It's hard > to pinpoint, I often feel like my clicks are being lost. > > The behaviour of the TestRunner was odd. Eventually I discovered running > tests via the Nautilus browser, but the UI feedback is extremely confusing > for "abstract" test cases. I still don't quite understand the results I see > there, so I do a final run of the tests in the TestRunner. > > Another strange issue I had with test cases was to do with the interaction > of the deprecation warnings. In by build script, I run: > Deprecation raiseWarning: false. > Deprecation showWarning: false. > so the build can run headless. It took me a few hours, and a careful > single stepping, to find that the deprecation exceptions were being > swallowed. I'm sure the TestRunner did not behave this way before. If you > ran a test, you would still see the deprecation exceptions. It was really > frustrating to see your test fail, but have the stack cleared out before > you could debug the exception that caused the test failure. > > Are these bugs, or just me getting used to the new release? > > >
