> Hello!
>
> One thing is not clear to me. How is Pharo related to standard Squeak? I know
> Pharo is a fork with its own mission, but is the development related? Do
> fixes in Pharo propagate upstream to Squeak? Is Squeak even considered
> "upstream"? Do fixes in Squeak propagate into Pharo? Automatically or
> manually? Or have they started being developed completely independently from
> some point in time?
We do not really look at squeak. No time for that. Now if people having time
mentioned that we have an interesting fix then we will be inclined to include
it in pharo.
Let me restate our vision and why we decided to make Pharo.
Our goal and vision behind Pharo is to twofold:
- make sure that people can make money and create their own wealth in
Smalltalk. Provide the best environment we can for that (and this is not easy)
This is really important for us. A part of the team here is working on
setting up a company around tools build on top of Pharo.
We are really happy when we hear that people are using Pharo for making
business (net style, nextPlan, b9, pinesoft)….
This is really great.
- bring Smalltalk to the next level:
- first class variables
- small core
- may be new mop
- powerful tools and abstractions
The idea is to have a solid infrastructure to be able to invent the
next generation smalltalkish system because smalltalk lacks a lot and
innovation stopped a while ago.
(real sandboxing, real minimal kernel with pluggable ui…)
It will take time but we will get there.
Stef
