> On 13 Jan 2015, at 07:00, Hern��n Morales Durand <hernan.morales@gmail.com> wrote:
>
> First of all, I am not the developer of Log4s, but I have been using it for a while and I see no significant gain switching to SystemLogger or ZnLogEvent. As Alain said, it is based in Log4j, which has his own Wikipedia page: http://en.wikipedia.org/wiki/Log4j
>
> I don't think there is too much sense in having "Log Objects" around, where probably I want to tail a daily rolled log from a headless remote image. I read the documentation of SystemLogger hoping to find a mechansim which dynamically selects compression strategies based in what's logged, or some other advanced feature, but I didn't found any :(
Maybe we should do away with Events as objects, Methods as objects, Exceptions as objects, Announcements as objects, Ring, MC, Commands as objects, Windows, Menus, ... - well, this whole objects everywhere thing is silly, let's use strings instead ;-)
We'll keep on trying to explain and to explore the possibilities.
Log objects are much more powerful, less expensive than you think, and backwards compatible with textual output.
Logging is deceptively simple, managing megabytes of log files is a PITA. Structure, classification, intelligence, behaviour are the answers.
BTW, it is not that you are not allowed to log some simple things to the Transcript, it is that it does not really scale, conceptually.