Hello,
This mail has been prompted (I'm sure you're sick of these;) by
Ceki's
critique of JSR 47:
I'll say now that many people prompted to comment by that critique
have
*not* reviewed JSR 47 properly themselves. That's fine; over the years
I
trust Ceki's opinion on this matter over anyone, but if you feel that
Ceki has made factual errors, *please* give a detailed response to
clear
things up.
Otherwise, one can only assume that the JSR 47 team acknowledge
log4j's
similarity and superiority, and are continuing anyway.
So please consider; what happens a few years from now? As the JSR
process keeps churning out hastily assembled APIs, the cracks in the
Java platform will widen, developer resentment at Sun's arrogance
will
increase, and the Java platform will be weakened at a time when, what
with Microsoft's .NET push, it can least afford to be.
So before foisting an inferior API on developers, please consider
adopting log4j. The excuse "too late in Merlin's development cycle"
is
rather poor; log4j is rock-solid and can be included with a minimum
of
fuss.
Regards,
Jeff Turner
--
jeff@socialchange.net.au
Web programmer
Social Change Online
Sydney, Australia