I was a little surprised to see Gorilla get kicked out. My understanding is that among Go developers, stdlib net/http + the Gorilla toolkit was the de facto sta

I was a little surprised to see Gorilla get kicked out. My understanding is that among Go developers, stdlib net/http + the Gorilla toolkit was the de facto standard approach. People are experimenting with new frameworks, e.g., beego, revel, martini, etc, but I don't think any of them are stable enough to meet your stringent criteria in that regard. It seems to me (as an outsider looking in) that the Go community is relatively "anti-framework", instead preferring libraries, like Gorilla, for special oomph in routing or sessions or what have you. I also think it's worth determining what you think the next decade's high level architecture will be: JSON api backends with fancy JS frontends, or more along the lines of standard Rails, Yii, etc? That will drastically change the type of web framework to choose.