I am trying to understand why the logging API in Android was not made independent of the platform. SLF4J has a clean separation between the logging API, and a pluggable logging implementation. In this scheme, the Android platform would just provide the logging implementation specific for the platform, but all of the logging statements sprinkled throughout the code would just be generic SLF4J and thus not platform specific. Given that logging tends to pervade the entire codebase, it seems this separation is critical for allowing Java libraries to function in applets, web applications, and mobile applications.
It is unfortunate that Sun did a poor job with the official JDK logging scheme, which lead to it not being universally adopted, but now it seems that Android has made the Java logging nightmare that much more unpleasant. Logging should really be part of the language specification rather than a library addon. There is already SLF4J for android with the logging implementation just delegating to the android logger, and so my question is, why is there not a best practice directive to use SLF4J logging, or better still, official adoption? It seems so obvious, I fear I must be ignorant of good arguments against this... Thanks for any insight! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
