Stephane, This mail is in part a personal disclaimer and in part "a suggestion". In my case I'm chasing a big customer prospect (took longer than expected but we're almost there), at the beginning of this year we decided to use Pharo as the backend technology. But I already work as a full time Smalltalk PM+Developer and I don't have more than a few hours per week to dedicate to develop the core business of our project (which also has an Android client that also absorbs a lot of time). Being part of a loyal user base that promotes Pharo on every chance is important, maybe not as important as pushing code/docs back to the community, or paying a yearly fee. But I think that the user base, as humble or small as it might be, _must not be disregarded_. Today the overlap between the user base and the contributors is big, but I wouldn't see an small overlap as a bad thing. In fact it would be a good thing! Nobody would claim that Wikipedia is a failure because 99.98% of the readers never edit. On the other hand Business model/Funding is a WHOLE different story. Regards, Esteban. Esteban A. Maringolo 2013/9/18 kilon <thekilon@yahoo.co.uk>:
How does "extending Pharo help tool " sounds ? :)
I am struggling to learn how morphic really works, especially TreeMorph.
-- View this message in context: http://forum.world.st/if-Pharo-is-key-for-you-tp4708875p4708917.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.