When comparing Negroni vs Buffalo, the Slant community recommends Buffalo for most people. In the question“What are the best web frameworks for Go?” Buffalo is ranked 6th while Negroni is ranked 7th. The most important reason people chose Buffalo is:
The dev command will watch your .go and .html files and the asset folder by default. It will rebuild and restart your binary for you automatically so you don't have to worry about such things. Just run the buffalo dev command and go to localhost:3000/ to see all changes live!
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 Hot reloading
The dev command will watch your .go and .html files and the asset folder by default. It will rebuild and restart your binary for you automatically so you don't have to worry about such things.
Just run the buffalo dev command and go to localhost:3000/ to see all changes live!
Pro CLI project scaffolding
Buffalo aims to make building new web applications in Go as quick and simple as possible. buffalo new coke
That will generate a whole new Buffalo application that is ready to go. It'll even run go get for you to make sure you have all of the necessary dependencies needed to run your application.
Pro Database migration
Easily migrate database.
Pro Full web and api only generator for those not looking for full web templating
Pro Multi step Dockerfile included with scratch base for minimal size
Pro Embeded resources in binary for easy reference
Pro Great community channel when help is needed
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.