flogger VS microprofile-config

Have you considered https://github.com/google/flogger ?

The main features that I've heard being asked for are handled by API decorators, such as Google's Flogger. I have personally not run into limitations that caused me concern about the speediness of slf4j2.

Yeah, I think switching to e.g. Flogger would be much more practical than rewriting it in Rust.

Why do you think they're using log4j to any significant extent? I'd be a bit surprised if they ever did rather than rolling their own, because for something this simple the cost of writing your own is far cheaper than dealing with a dependency. We're not talking about Linux or Clang here...

In particular, from https://github.com/google/flogger#yet-another-logging-api:

> Flogger is now the sole recommended Java logging API within Google.

There are a lot of great config libraries, you should also take a look at such as smallrye-config. I am trying to make my library compatible with microprofile-config but there are some fundamental differences.

You might have a look at MicroProfile Config as well.

Now you might be tempted to say well we just need a System.getProperties replacement. A SLF4J of properties config. Perhaps one that uses the ServiceLoader. And indeed microprofile config somewhat solves that problem. The problem is of course is backward compatibility (replacing all the old libraries uses of system properties of which you might not be able to) and of course that config facade adds a dependency.

Quarkus is internally using the SmallRye implementation of Eclipse MicroProfile Config (MP-Config). MP-Config allows to add so called Configuration Sources, that allow to supply config objects in a programmable way from e.g. a file in a strange format or perhaps even from a central repository. This brief post describes how to create a ConfigSource for Quarkus that knows about existing properties