Question

Views

Why does Android maintain 2 different Log classes that seem to support the same things?

I'm talking about:

For what I've seen for some years developing, every Android official documentation points to the Log and not the Logger.

Even specific loggers like the TimingLogger uses the Log.

So why are those 2 supported?

Are there any feature that can be used through Logger than I can't achieve through Log?

Are there specific use cases for both?

about 4 years ago · Santiago Trujillo

Answer question

Answer 1 · 2022-06-13T15:48:11.821Z

The feature crossover seems to be:

Seems like "android.util.Log" is going to have:

Looks like "J.U.L" is going to have:

Buffering of records with the java.util.logging.MemoryHandler. This is good for say when a SEVERE error occurs you can include the last 1000 records which may be at lower level.
Filtering of records using java.util.logging.Filter. There are no out of box filters included but it does give more granularity over implementing this behavior in a android.util.Printer
Out of box support for XML.
Out of box support for Sockets.
Support for 3rd party java.util.logging.Handler implementations.