No post body was provided.
Ask HN: What do you think is the current best Go webframework and why?
1–10 of 18 posts
Re: Ask HN: What do you think is the current best Go webframework and why?
#2I prefer just using the standard library with a muxer like gorilla/mux.
Re: Ask HN: What do you think is the current best Go webframework and why?
#3I think the idea of a web framework in Go is too application level oriented where as Go is a great language to write infrastructure. If you implement a microservice, look for microservice frameworks. A web application itself seems to broad. I would almost always recommend to find a custom implementation.
Re: Ask HN: What do you think is the current best Go webframework and why?
#4Really really close to flagging this. There is no "best X" for any X. At least not without adding lots of context (and then it gets boring for other people since these details probably are not interesting for them).
Re: Ask HN: What do you think is the current best Go webframework and why?
#5I prefer just using the standard library with a muxer like gorilla/mux.
Because the more fully kithensunk ones are worse/bad/negative or just because you keep it simple?
Re: Ask HN: What do you think is the current best Go webframework and why?
#6I prefer just using the standard library with a muxer like gorilla/mux.
I second this approach. The go standard library has a multitude of utilities that make spinning up a Web application fairly straightforward. Moreover, utilizing the standard library gives you greater leverage when you need to adapt to the unique needs of your application.
Re: Ask HN: What do you think is the current best Go webframework and why?
#7Really really close to flagging this. There is no "best X" for any X. At least not without adding lots of context (and then it gets boring for other people since these details probably are not interesting for them).
If I am starting to learn Go and want to try my hands at building a web service, what should I use?
Re: Ask HN: What do you think is the current best Go webframework and why?
#8I prefer just using the standard library with a muxer like gorilla/mux.
Because the more fully kithensunk ones are worse/bad/negative or just because you keep it simple?
I prefer less opinionated where possible. "Worse" is really subjective, I just don't need bells a whistles for many of my projects, so the stdlib is just fine.
Re: Ask HN: What do you think is the current best Go webframework and why?
#9Really really close to flagging this. There is no "best X" for any X. At least not without adding lots of context (and then it gets boring for other people since these details probably are not interesting for them).
If I am starting to learn Go and want to try my hands at building a web service, what should I use?
For learning purposes, I might suggest the Go implementation of gRPC[1]. As the name implies, it is RPC focused and so doesn't necessarily translate well to a complete web service (HATEOS and such), but still provides some insights into how you might structure your code for that kind of project.
Re: Ask HN: What do you think is the current best Go webframework and why?
#10OP's question is far too broad to elicit useful answers.
Start with a feature list of what you require from the framework.
- Validation
- Routing
- Security
- Filtering
- Templating
- Data binding
- Component reuse
...