Golang Logging Mess
Go has a logging mess. If you want to see it in action open up a Go application and look at the number of logging implementations that have been pulled into the application. For example, if you look into the Kubernetes modules you’ll find it’s using zap, logrus, klog, and others. This mess can lead to applications not exposing logs, binary bloat, and more. It also inverts control. Instead of the application controlling the logging the libraries do.
Many languages simply don’t have this problem. Some by design (e.g. Rust and Python) and some because the community chose to solve it (e.g., PHP with PSR-3).
This is a problem worth exploring and understanding.