When comparing Gin-gonic vs Negroni, the Slant community recommends Gin-gonic for most people. In the question“What are the best web frameworks for Go?” Gin-gonic is ranked 1st while Negroni is ranked 7th. The most important reason people chose Gin-gonic is:
The documentation for Gin is broad and comprehensive. Most tasks that you will need to do relating to the router can be found easily in the docs.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Extensive documentation
The documentation for Gin is broad and comprehensive. Most tasks that you will need to do relating to the router can be found easily in the docs.
Pro Good for building REST APIs
Gin is a pretty minimalistic framework. Only the most essential features and libraries are included, making Gin a great framework for developing high-performance REST APIs.
Pro Well-tested and numerous middlewares
The Gin community has created numerous well-tested middlewares that make developing for Gin a charm. Features include gzip, an authorization middleware, and sentry.
Pro High performance
Gin runs 40x faster than Martini, and runs comparatively well compared to other Golang frameworks.
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.
Cons
Con Might not be suitable for large backend applications
Gin-gonic is great for building a REST API for the backend if you want to develop an SPA using a frontend framework. But for anything that requires more features on the server side, it would be better to use a more "batteries included" framework.
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.