100% agree with and I was not emotional just playing drama because I found the discussion so funny. So lets move. There are so many cool stuff along the road. Now reviewing Spec chapter :)
Stéphane Ducasse wrote
And can we have a private developer mailing-list :)
What the heck are you guys talking about?! Everyone take a deep breath... Here's the reality: One person who is a) not here to defend himself, and b) (allegedly) not using Pharo (allegedly) made an off-list comment that some developers (allegedly, possibly including himself) may find it jarring that in a year, one could find an unrecognizable latest version of Pharo. This, by the way, is true, even if it may not change our vision or plans. It may be unrecognizable. And, some developers *may* find that unsatisfactory. As we've already established, people do not like change.
Now, none of this seems like a reason for all this fuss. It's wasting our time and energy, which is already at capacity making Pharo the system of our dreams. Specifically, I think a private developers list would hurt Pharo both psychologically and physically - we want as many eyes on the issues at hand as possible.
Finally, the SO/separate-stackexchange-site/dev/users issue is a separate thing. If we're going to talk about mailing list discipline, let's stop hijacking people's threads.
In closing: * Let's all get back to work. People will react emotionally to the massive progress (change) of Pharo. Duly noted, but it's in the damn manifesto ("Not backward compatible" [1]). * Maybe we can improve our communication process, both for the devs and users. Let's discuss that.
[1] http://code.google.com/p/pharo/
-- View this message in context: http://forum.world.st/Pharo-is-exploding-tp4630233p4630489.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.