When comparing Beego vs Negroni, the Slant community recommends Beego for most people. In the question“What are the best web frameworks for Go?” Beego is ranked 4th while Negroni is ranked 7th. The most important reason people chose Beego is:
Beego is a "batteries included" web framework, which means that a lot of features already come out of the box. This way you don't have to spend time and find third-party libraries to integrate to the framework for most of the tasks you need to complete.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro No need to find and install external libraries
Beego is a "batteries included" web framework, which means that a lot of features already come out of the box. This way you don't have to spend time and find third-party libraries to integrate to the framework for most of the tasks you need to complete.
Pro Built-in tool which watches for changes
Beego has a built-in tool which watches the code for changes. This tool (called bee tool) can be configured to run any task once the code changes. It can run tests or reload and rebuild the whole project.
Pro Built in ORM
Beego's eloquent ORM is a simple and fast Object-Relational Mapping which helps with organizing the application's database. Beego examples and documentation all use the beego ORM. No need to learn to use and integrate another ORMs API.
Pro Captcha
Pro Auto testing
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 Very opinionated
Con Very opinionated
Con Non-idiomatic code
Con Builds may fail silently
Sometimes even though a build has failed, the pages will still render. Apparently it caches a previous build when the current one has a problem. This can be a frustrating though because it leaves you wondering why the page you are working on stopped working out of the blue.
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.