I agree with Markus on that one , I am really a “release first update later” kind of guy. Which of course means also that I am against the idea of having only 1 release per year for Pharo. The why has been explained in myriads of online blog posts because I am far from the only one to believe in this. This why I never stuck with the stable release , I never saw any use for me or anyone else. Quite the contrary I think it hurts the development process by delaying bug reports. On Mon, 23 Oct 2017 at 05:27, Sean P. DeNigris <s...@clipperadams.com> wrote:
> Tudor Girba-2 wrote > > Bloc is usable since half a year (the tutorial from ESUG was also given > at > > PharoDays and works out of the box). > > [not-a-rant ;)] > After spending a good part of the day playing with Bloc, I'm wondering > whether I am approaching it wrong. When I hear "useable", I think useful in > real life scenarios - maybe not necessarily production, but at least > day-to-day personal/in-house use. With many failing examples, deprecations, > and seemingly minimally working text support (I was playing with > BlTextElement, not looking for a full editor), I didn't find this to be the > case. Am I missing something? Was "useable" meant in the sense of "ready > for > experimentation and feedback"? I am not complaining at all. I just want to > be clear on the status so I effectively manage my expectations and find the > best way to help out. Thanks! > [/not-a-rant ;)] > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >
