I've read that some of you are installing their own set of packages on top of Pharo-Core and not using Pharo. Why is that so? What don't you like in Pharo? Why didn't you tell us before?
Uhh? Don't tell me you didn't know? All images I build on my Jenkins are based on PharoCore since we setup that infrastructure. I even unload packages from PharoCore, because I think it contains far to much cruft (https://github.com/renggli/builder/blob/master/scripts/pharo-cleanup.st). This is also something I repeatedly brought up. I don't use Pharo mostly because of OCompletion. It looks ugly and I get annoyed to have it constantly suggesting me stuff I didn't ask for. No other IDE I know has such an aggressive and annoying completion behavior. Also the Pharo images usually contain very old code, for example the image I just downloaded from pharo-project.org uses a version of OmniBrowser with the broken scrollbar. Something that I fixed in the beginning of this year, I think. Personally I don't need many of the packages loaded into Pharo: AutmaticMethodCategorizer (something similar is in OB-Standard for a long time), Autotest (something similar is in OB-SUnitIntegration for a long time), HelpSystem, MemoryMonitor, MorphicExtras, Sound, ArchiveViewer, SqueakCompatiblity, BitBltPen, MovieMorph, ObjectMetaTools, Nile, ProfStef, ScriptManager, XMLSupport (I load that only when needed), XMLWriter.
If we don't have this information, you might not like the new Pharo-Core and you will have nothing anymore to base your images on. Speak now or forever hold your peace :-)
Since the beginning of 2011, 3757 of my images were downloaded from people other than me. Not sure who this is, why they do it, and if this number is any significant? Maybe it helps you for your statistics? Cheers, Lukas -- Lukas Renggli www.lukas-renggli.ch