[Pharo-project] About not using full Pharo

Stéphane Ducasse stephane.ducasse at inria.fr
Mon Jun 20 05:44:48 EDT 2011

On Jun 20, 2011, at 6:20 AM, Yanni Chiu wrote:

> On 19/06/11 4:38 PM, Damien Cassou wrote:
>> Hi,
>> 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?
> My image was always built from PharoCore. It was done this way before PharoDev existed, and I saw no reason to change.
> I thought people were supposed to build their own image (tailored to their needs). IIRC, PharoDev was initially provided as a convenience for those that wanted such an artifact.
> The concept of PharoDev evolved - I recall discussion about the "branding" of PharoDev as Pharo, and relegating PharoCore to the role of build process artifact. The discussion did not raise any flags for me, until now, when the discussion has turned to "eliminating" PharoCore.
> I've never mentioned this before because I never thought I was doing anything wrong by building my own image from PharoCore.

but you are not. :)
The point is that we should be able to have good tools inside the default system so that we can get faster.
We are fedup to do refactoring of core manually.


More information about the Pharo-dev mailing list