JVM logging systems configured by classpath scanning are evil. That is all.
-
-
Replying to @posco
I was always annoyed by JVM loggers which offered multiple different ways to configure them: code, classpath, params, config file, each method silently overriding another... maybe. The only killer feature of my (unreleased) logging library is that its configuration is explicit.
1 reply 0 retweets 3 likes -
Replying to @propensive @posco
Log4j2 is my most hated because it has a JSON configuration format that people often use, but it isn't documented and you're just expected to be able to translate from the XML syntax in your head
2 replies 0 retweets 1 like
I already had a moral objection to it before knowing anything else about it, just for abusing the digit "4" (four!) to mean "for", while quite correctly using the digit "2" to mean the number "2", all within a mere three characters...
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.