Sven Van Caekenberghe-2 wrote
> Thanks Jochen, thanks everyone.

Great report! Thanks, Sven :) I was thinking in the same direction - that my
posts always seem to focus on our work moving forward, and I rarely take the
time to do a nice writeup of successful applications like these, of which
I've had many. 

I was also thinking that many of the recent animated discussions are signs
of health in our community because:
a) They seem to often involve people that are not regular posters to the
list, signaling a potential widening of buy-in
b) While our community values constructive feedback (even if it's very
direct), it also fiercely protects people who have given us a lot (as
evidenced by the overwhelming response to a recent trolling on another ML)
c) Maybe most important: they are often about code and infrastructure that
didn't even *exist* a few years ago. For example, now we complain about
breaking builds; I'm sure we all remember not long ago when there was *no*
CI at all to complain about! It seems amazing that the system is as stable
as it is considering everything we overhauled/invented, including: streams,
http, file system, browser (2x), git support, FFI, changes, catalog, the
compiler, GT…

For myself, I am clear that any instability is a small price to pay for the
power and hope that Pharo offers. Every time I drop out of our live, direct,
turetles-all-the-way down into a Ruby script, command line, or configuration
file, this is proven again.

All we have to do is hang on! It is a well known principle that it often
seem most difficult just before success and the difference is who quits and
who doesn't :)

Sent from:

Reply via email to