I could not agree more with you

I am very much against "One ring to Rule them All" , it did not work for Sauron in Lord of the Rings for the exact reason why its a bad idea to put all your eggs in one basket. Once it fails in a fundamental level you are screwed forever. ��

People reinvent the wheel because this is how evolution works, this is how our world works. You use what you have and you add something new to the recipe and hope for the best.��

It also gives the ability to users to choose the right tool for them. A developer of a Library can never be more smart than its users because he does not know their needs and cannot anticipate their personal desires and workflows.��

I have never had the pleasure of using a Logging system, but using Announcements sounds like a way I would go with it if it was me. Certainly will give it a try thanks Tudor.��


On Mon, Jun 16, 2014 at 10:13 AM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:

On 16 Jun 2014, at 08:52, stepharo <stepharo@free.fr> wrote:


Hi,

I like very much the new energy people are putting into creating the SystemLogger engine for Pharo. I think this is a specifically important area for which we have to have a solution out of the box. At the same time, I also think that Pharo provides an infrastructure that makes room for ideas that are otherwise hard to reach in other languages or environments.

Why Java does not have announcements?

Stef asked for collaborations around this project, so here is my literally small contribution: a rather different logging engine.
I do not see how this contribute to SystemLogger. So at least please do not say it, respect the amount of time I spent
design it and working with Norbert.

It is called Beacon, it is based entirely on Announcements, it has ~200 lines of code, it has no tags or levels, and in my opinion it is fully functional.

You can see a detailed description here including some informal comparisons with SystemLogger:
http://www.humane-assessment.com/blog/beacon

Please let me know what you think. I would be happy to join forces to reach a mature solution that is both versatile and that can show how Pharo is different.
So should we see it as a competitor to SystemLogger?
(you will say of course not) but I do not understand.

Just my 2 cents:
��Stef, I wouldn���t fight agains other projects, it���s natural that for popular environments there are different approaches to implement important tools. E.g. in Ruby there are few different web frameworks and I think logging too. And I wouldn���t be angry on Doru because he mentioned SystemLogger, for me the idea is that Pharo is missing decent logger, and there is a work being done on the big project, in a while Doru proposes small yet functional tool with it���s own philosophy.

I���m trying to ignore my personal preferences here, and move attention to the point that we should make our environment modular and let people decide what they want to use.

Uko




Cheers,
Doru

--

"Every thing has its own flow"