Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing AIDA/web vs N2O, the Slant community recommends N2O for most people. In the question“What are the best backend web frameworks?” N2O is ranked 29th while AIDA/web is ranked 47th.
Specs
Question 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 Fast binary data
Pro Binary encoding and protocols
Here is a list of types of endpoints which are supported by EMQ and accesible to N2O apps: WebSockets, MQTT, MQTT-SN, TCP, UDP, CoAP. Normal use of N2O as a Web Framework or a Web Application Server is through WebSockets, but for IoT and MQTT applications it could be served through UDP or SCTP protocols providing application level message delivery consistency.
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.
Con Unfriendly developer community
Developers are often rude and unfriendly to users.
Con Bad documentation
It has bad documentation, which leaves out crucial steps, making it hard to learn.
