When comparing Negroni vs Goji, the Slant community recommends Negroni for most people. In the question“What are the best web frameworks for Go?” Negroni is ranked 7th while Goji is ranked 10th. 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 Great performance
Goji is an abstraction layer over the standard Go library (which has support for HTTP) and added Einhorn support. There's probably very little you can do with Goji that you can't do with the standard library and a bit of elbow grease.
This makes Goji an extremely lightweight and fast framework.
Pro Socket manager integration
Goji integrates with Einhorn, which is a language agnostic socket manager. Making it possible to have websocket support in Goji.
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 Goji 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 Goji development being abandoned one day.