When comparing AIDA/web vs Java, the Slant community recommends Java for most people. In the question“What are the best backend web frameworks?” Java is ranked 42nd while AIDA/web is ranked 47th. The most important reason people chose Java is:
It makes it easy to debug and to read code.
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 Verbosity
It makes it easy to debug and to read code.
Pro Mature ecosystem
The language and all its tools have enough time to age and they've aged well.
Pro Type-safe
It is easier to catch errors sooner.
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 Memory hungry
Running the virtual machine, application server and application itself consumes significant amount of resources.
Con Unnecessarily obtuse and verbose
If you like typing 40 lines of code to open a file, Java is the language for you. If, on the other hand, you’d actually like to get something done, look elsewhere.
Con Oracle
Enough said.
In more detail: Oracle has acquired Java from Sun and continues to surround it with controversy ever since (legendary lawsuit with google, money extortion from the enterprise users etc.).