> I want a minimal Smalltalk with decent modularity semantics.

We have been working on that since Pharo day one and we will continue. 

> I want
> decent integration with the standard tools of the trade. I _don't_
> want to require special unique snowflake tools to work with my code.

Ok

> Right now I'm breaking up the Squeak Trunk into pieces, unloading
> things as I go. I hope, at some stage, to end up with some fairly
> minimal thing that will still allow one to load the main things that
> Squeak's used for.

To me minimality can be a trap. We want to empower users. 
if you goal is to make smalltalk used with normal tool, 
I do not really understand why you do not focus on making Pharo fully working 
with Git.


> Colin Putney's Environments work is the main thrust
> for 4.5, together with the usual cruft removal work.

We are doing that since years but if you want to spend your energy on that this 
is your decision.

> But I see your point about lack of vision, whether perceived or
> actual. That's something Squeak will have to work on.

I even wrote 40 pages to describe that we will get a minimal image with no 
compiler, we have tanker 
and candle light that are starting to work and we dreamed about it with pavel 
back in 2005. 
But this is your time and energy. :) Just be ready for competition because we 
are going there for real.

There are so many exciting paths (type inferences, real modules, git back end) 
that I do not understand why 
you just redo what we did. May be this is something that you want to prove to 
yourself and this is ok too.


>> Most of the pharo people are not payed for doing pharo. What we are building 
>> (and fighting for) is an
>> ecosystem in which smart guys can also find a job and it is becoming to 
>> happen. Mariano is full of work
>> and many others. Sean told me that he got several job offers.
>> 
>> Pharo is not the end, it is the start. It is not like we would like it to be 
>> but everyday it gets closer to it.
> 
> That's good to hear. I feel the same way about Squeak, although it's
> clearly a lot, er, *mossier* than Pharo.
> 
> frank
> 


Reply via email to