When comparing Negroni vs Web.go, the Slant community recommends Negroni for most people. In the question“What are the best web frameworks for Go?” Negroni is ranked 7th while Web.go is ranked 17th. The most important reason people chose Negroni is:
Negroni was developed as an alternative to Martini and Martini's "batteries included approach". You can choose which middlewares to include in your project. This way you get to choose what to have built-in.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Choose what features you want to have
Negroni was developed as an alternative to Martini and Martini's "batteries included approach". You can choose which middlewares to include in your project. This way you get to choose what to have built-in.
Pro High performance
Web.go is a minimalistic web framework which adds routing to the net/http
package from the standard library. Even so, web.go tries to compensate for the small abstraction that it offers by structuring routes in a tree instead of a list. As such, it's a very fast framework which makes it a good choice in applications where good performance is key.
Cons
Con No built in router
Negroni cannot really be considered a true web framework because it does not have a built-in router. You need to choose one of the many web routers already developed by the Go community and integrate it into your Negroni project.
Con Doesn't add a lot of functionality on top of the standard library
Most of the tasks that web.go is used for can be completed with standard library support without adding the overhead of an additional external library and without having the risk of web.co development being abandoned one day.