On 2/15/07, <b class="gmail_sendername">Boris Unckel</b> <<a href="mailto:boris.unckel.mlg@gmx.net">boris.unckel.mlg@gmx.net</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"><br>
<blockquote cite="http://mided0c429e0702151332t5c131601qad15c84c9b6be62a@mail.gmail.com" type="cite">
<div>
<div>This is especially valuable in a situation where you migrate
people away from log4j. Inevitably, when you are moving people away
from what they are familiar with - there are comparisons. So in the
case of migrating people away from log4j, when they forget to configure
the system correctly, there is a stderr default. If they make the same
error in slf4j there is an error and the program halts, the first thing
I'm bound to hear in this situation is, "Log4j wouldn't have done
that". However much you may disagree with log4j's approach, the
comparison is inevitable, and I have first hand experience to back this
claim up.
<br>
</div>
</div>
</blockquote>
This is not a correct comparison: People cannot migrate from an full
log API implementation to an log wrapper without choosing an underlying
full log API.<br>
<br>
People migrating away from a famous wrapper are disappointed about that
wrapper because it has a dozen of options to configure (default and
fallback implementation, service provider approach,</div></blockquote><div><br>I agree it isn't a fair comparison, but that doesn't matter - what matters is peoples perception of what is easier if you want an API to be successful. What you have to realize is that you are trying to push a 4th logging API on a large user based on the planet earth who by an large, mostly use the Logger interface. If you are used to not doing anything at all to get messages printed on stderr, which I would say most folks are, then you will have a bad experience if you switch to SLF4J and don't configure yourself correctly.
<br><br>As I said, deploying the correct implementation jar IS a kind of configuration, weather you call it that or not.<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">Yes, I have mentioned that. Again: I have no problems with the
ServiceProvider approach, and I did not write that.</div></blockquote><div><br>All I did was quote your message, you might want to check what you wrote. <br></div><br></div><br>-- <br><br>- Eric