Hi, On May 16, 2012, at 9:23 AM, Pavel Krivanek wrote:
On Tue, May 15, 2012 at 11:29 PM, Stéphane Ducasse
I will quote Germán (I hope he will not mind): "lot and lot of things... Lot of new things each day. Not time to stabilize nothing. Is needed such acceleration? ... My point is, I'm trying to move a business with Smalltalk and the acceleration of Pharo is well know by me (from other companies) and sooner or later, impact in my job and I'm a very LITTLE software house can't migrate my products all the time."
well... as you quote German, I will quote myself answering Germán (well... also translating from spanish and putting some context) :) I said something like: "No no no, that's not true" :) 99% of the changes affects infrastructure and/or replace old tools. Why your work should be affected by that? I migrated Seaside from 1.3 to 1.4 in 15'... and the "problem" was not Seaside-Pharo incompatibilities, but to adapt configuration to not load OB (just not choose those packages in the metacello config) Other frameworks like Magritte and Pier ran out of the box. (well... Magritte-Mophic needed a small adjust... and that was like 5') For more examples, my personal projects (I submitted 3 slides yesterday for two of them), are usually complex projects (both for web and desktop) and I migrated all of them in less than a morning work (I needed to update/modify my metacello configurations for that). So... as soon as I know... your feelings are just that: feelings. Not real facts. And maybe those feelings are because we (as a community) are growing and we need to adapt our communication processes to match current status. But I think that's a good think, not a bad one.
We simply have to accept that some developers can have this feelings and try to find a way how to limit it. I think that some official Pharo blog (maybe written by Esteban) would be very helpful. Some kind of not very extensive technical information source that will help people to stay in touch with Pharo progress. That will explain what is being changed in Pharo and why. I think that developers than will see the changes like positive not as alien ones.
As I said above, I agree we need to improve our communication efforts. New times need new ways :) I think a developers blog is a good idea, but I cannot commit myself to produce one weekly blog post, for me a monthly post is more realistic... but I will talk with others and see how can we fulfill that. Also, maybe splitting list as Marcus said is a good step... best, Esteban