Just want to highlight a couple points of caution/clarification by groob from the reddit discussion[1]. In response to "What conclusion should I draw from this

Just want to highlight a couple points of caution/clarification by groob from the reddit discussion[1]. In response to "What conclusion should I draw from this?": > I don't think the lesson here is to judge these frameworks. The graph alone is not an indication of quality, there are other things to consider. I think the lesson is that goviz is awesome and you should run it against your own projects, where you know the code well. Having tightly coupled code should be avoided. A dependency graph can pinpoint areas of your application that are in need of refactoring, as well as code that is either easy or hard to remove. In response to "what's the deal with net/http?" > Please don't draw the wrong conclusion from these graphs. Vault is a complex, production ready application which does much more than your typical CRUD app. I find the vault http code to be of good quality, and written in an idiomatic style. If I was learning how to wrote APIs in Go today, I'd look at the vault http package to learn from. [1]: https://www.reddit.com/r/golang/comments/50uni1/dependency_graphs_of_go_web_frameworks/ https://www.reddit.com/r/golang/comments/50uni1/dependency_g...