David Beaumont

SimpleMessageFormatter is not intended to be a public API, so it's not something I want to make general purpose. Feel free to make your own formatter (and if you were...

In fact you've just made me see an issue in the JDK backend, since it uses the underlying logger name for "getLoggerName()". This is wrong since it prevents JDK loggers...

Hmm, yes, this is all a bit unsatisfying at the moment (you can tell I'm a total noob at Maven stuff). It'd be ideal if the current default backed was...

The issue is that there are those who use custom log levels, so it's hard to accommodate them without something that just ends up using the "value" of the level....

For better or worse, you can mimic everything that SLF4J does using JUL Level, but not the other way round (because of custom levels). We went with the most flexible...

Sadly I just don't have time or experience with them to maintain the non-JDK backends. I'm happy for contributions to improve the configuration and usability (even if just to the...

Right now there isn't an easy way to customize this I'm afraid (it's part of the SimpleLoggerBackend, which is by design, as the name suggests, very simple). I do have...

As Louis says, there should be no cost to "string creation" because you express that as "literal format string plus arguments" and let Flogger format it only when the log...

> Well all the bytecode I have ever looked at was doing new String("foo"); for the string literal. Not sure when or if that changed. But if you are both...

> 11 ldc [4] That's the "load constant" which gets the "my main message" literal and puts a reference to the interned String on the stack. There is no allocation...