As mentioned on the follow-up UO recording, we mentioned some of the reasons:
- CL uses ( or used? ) classpath scanning to choose which implementation to use, rather than how slf4j has concrete implementations in each dependency - i.e. slf4j-log4j has all the logging implementation for log4j, so you just include that dep along with core, I believe they share the same class names ( which kinda feels evil ) but I could be wrong?
Richard also mentioned there was threading issues with CL I think...