Hi Stef, On Tue, Jun 17, 2014 at 4:37 PM, stepharo <[email protected]> wrote:
> I do not understand why log should be announcement. > Especially since log: is in Object in SystemLogger. > The Log class is a carrier for the message object. The Log class is essentially doing the same thing Announcement does. So, we can just use an Announcement for that. This is not a limitation. I think it is quite beautiful. > But I will not talk about this topic anymore because I felt insulted. > Doru like do not expect that people wants to join effort on any project, > if the only reaction you have > when ask for help is to create a competitive solution. > I am sorry you felt insulted. It was not the intention at all. Perhaps my wording stroke the wrong chord, but as I tried to explain, the goal is not to pursue Beacon, but to explore the design space. I even documented, provided examples, wrote several comments in the code. I based the implementation on the argument of Sven that using Announcement is conceptually a great opportunity for a logging system and I showed that if we do that it can indeed lead to less than half the size of the other solution. In the process, I also showed how by using Announcements we need neither level nor tags. I think it is precisely in the spirit of Pharo to be able to do more with less concepts. I cannot help it to have a different opinion, but I really do not see what else I could do to make my point and contribute. I could have just committed in the SystemLogger, but that would have meant re-writing it which would have turned out to be the same thing. Would it have been better to not do anything? I hope not. So, please, let's start over and let's keep in mind that email is a poor carrier of intention. I am here precisely because I want to work together with you guys. Cheers, Doru > Stef > > -- www.tudorgirba.com "Every thing has its own flow"
