I agree with you, but at the same time I am also a little worry that this log4j2 exploit may inadvertently push us to the other extreme. Now every time I want s

I agree with you, but at the same time I am also a little worry that this log4j2 exploit may inadvertently push us to the other extreme. Now every time I want some essential features to be added to a library, the log4j2 exploit will be brought up as a knee-jerk reaction. At least we already got https://github.com/mattermost/logr https://github.com/mattermost/logr, otherwise there could be years before we get to have a golang logging library with async logger.