Sorry I wasn't clear.�� I didn't mean this part... "most people think Smalltalk is dead and a relic of the past and we want to avoid that negative connotation"
I meant this... ��"because the next thing always is 'No, don't do that, you can't change anything'. Pharo was started precisely because we want the freedom to change things where necessary (on all levels, VM, language, compiler, runtime, libraries, concepts, tools, ..)".
Now to directly address you points
* additional new features���� It is 30 years since Smalltalk-80 was released.�� Has there been so little advancement in non-Smalltalk fields that there is nothing to learn or improve? What about the the next 30 years?�� Now actually, features already differ between members of the Smalltalk family. [1]
* syntax��that extend Smalltalk
I haven't seen much movement towards changing syntax.
* desirable quality of Smalltalk /language/ is its pure��simplicity.��
You are right.�� We need to take care here.�� But we want to avoid someone coming along saying "you can't do that! that's not Smalltalk!" ��
For example... "Whether Squeak should comply with ANSI Smalltalk is a common flame war.[2]"
*��Pharo /environment/ (including the��tooling and class libraries) will evolve and grow and improve, then you��can't really call Pharo a "new language."��
Actually I don't see anyone running around saying "we've made a new language." ��What I've seen is that its more about the environment.�� But the separation between language & environment is a grey area for Smalltalk (the language is so minimal).�� Saying "Pharo is not Smalltalk" is a pragmatic approach to dealing with [2].�� Saying it first helps avoid compliance-based arguments later if anyone is surprised that something changes. �� But I think its fair to consider Pharo in the Smalltalk family.�� You might consider similarities with "GNU's Not Unix". ��
cheers -ben��