I really like that Go has a great std lib, but it comes at the cost of quality or at least feature fullness. Some examples: - The csv package. Compare Go's csv

I really like that Go has a great std lib, but it comes at the cost of quality or at least feature fullness. Some examples: - The csv package. Compare Go's csv package with Rust csv crate. The package in Go's std lib is close to useless compared to the Rust community crate. - Logging. No tracing, limited providers, just recently added structured logging. - The xml package is very slow and cumbersome to use compared to modern element-tree-like implementation. For larger docs you probably need to resolve to a community package. - If I'm not mistaken, Java has a build in http server, which usage is probably very low. Instead people are using Jetty / Netty / Tomcat (? my Java times are long ago) To repeat myself: I personally like the std lib approach of Go. I disagree to any narrow view on this topic.