Item — HN Reader

This was a very kind and thoughtful way of putting this. I absolutely agree and really hate to see people rely on frameworks in Go (like Gorilla or Alice). These frameworks certainly have a place. But if you haven't written vanilla Go, you are really missing the point.

As jonesb6 mentions, Go really gives you a whole lot more than other languages like Python, Ruby, or Node. It has fantastic built-in routing (though I opt for httprouter) and a great template library (though I sometimes use Pongo2 to aid the port from Jinja2).

It appears to be very common for developers coming from Rails or Django or Express to try to find some other framework to force on Go. I'd just recommend that you give vanilla Go (possibly with some small libraries) a chance.

1 comments

> and really hate to see people rely on frameworks in Go (like Gorilla or Alice). These frameworks certainly have a place. But if you haven't written vanilla Go, you are really missing the point.

Just to jump in: Gorilla (a collection of standalone packages) and Alice (a middleware chaining library) are definitely (far) far calls from frameworks - the submission, and other frameworks like Gin/Martini/etc. are more strongly coupled.

I wouldn't blame anyone who uses gorilla/mux and/or gorilla/schema to avoid writing their own a) pattern matching router (which net/http does not provide) and/or a comprehensive, battle-tested r.PostForm to struct mapper.

Otherwise I agree that Go the language—and Go the community—lean towards glueing smaller components together, rather than reaching for a kitchen sink solution.