To be honest, looking at your arguments for Maven being better, most of those are pros or cons, depending on where you stand. They're tradeoffs. Also, as far a

To be honest, looking at your arguments for Maven being better, most of those are pros or cons, depending on where you stand. They're tradeoffs. Also, as far as I know, Go doesn't require special support from your git (or whatever VCS you use) server, as is confirmed by the reference: https://golang.org/ref/mod#vcs https://golang.org/ref/mod#vcs Though I mainly wanted to comment on the profiles part. Could you please provide links to tools which are in your opinion good for complex profiling use cases? I'm asking because I myself really like both the web based profile viewer, as well as the go tool trace viewer, for more complex situations. However, to address the other points: testing has good libraries for equality and mocking (I.e. testify); formatting is a trade-off, many people prefer one forced consistent code style, even if they don't like it Overall, your conclusion of the Go ecosystem being "definitely worse" looks quite far fetched based on your arguments. Not to say it's wrong, the reasoning just isn't at all convincing.