When comparing AIDA/web vs CodeBehind, the Slant community recommends CodeBehind for most people. In the question“What are the best backend web frameworks?” CodeBehind is ranked 36th while AIDA/web is ranked 47th. The most important reason people chose CodeBehind is:
CodeBehind is a modern framework with revolutionary ideas.
Ranked in these QuestionsQuestion Ranking
Pros
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.
Pro Modern
CodeBehind is a modern framework with revolutionary ideas.
Pro Code-Behind
Code-Behind pattern will be fully respected.
Pro Under .NET Core
Your project will still be under ASP.NET Core and you will benefit from all the benefits of .NET Core.
Pro Get output
You can call the output of the aspx page in another aspx page and modify its output.
Pro Modular
It is modular. Just copy the new project files, including dll and aspx, into the current active project.
Pro Simple
Developing with CodeBehind is very simple. You can use mvc pattern or model-view or controller-view or only view.
Pro Fast
The CodeBehind framework is faster than the default structure of cshtml pages in ASP.NET Core.
Cons
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.
