When comparing Beego vs AIDA/web, the Slant community recommends Beego for most people. In the question“What are the best backend web frameworks?” Beego is ranked 18th while AIDA/web is ranked 47th. 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 Conceptually simple, yet complete
Most frameworks seem to tend towards conceptually simple, but also stripped down (such as Python's Flask), or go the other way and be very fully featured, yet complex. AIDA/web, however, manages to give a programmer a lot of expressive power, while remaining conceptually simple -- an afternoon will get you building websites, and you'll feel comfortable with AIDA/web in just a week or so.
Pro Smalltalk
Program your web app in Smalltalk, an enjoyable and easy language to use. Smalltalk was the language to inspire modern Object-Oriented programming and pioneered many of the programming concepts used today, such as MVC.
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 Relatively inactive
At the time of this writing, AIDA/web is 26 years old (first created in 1996). While maintaining pace with modern technologies (REST, Javascript, etc.), the community is small. You might find it difficult to find timely help, find resources and tutorials, etc.