Comparison of anthem. net, ajax.net, and Atlas

Many people want to learn Ajax technology under. net, but they don't know which framework to learn. Here we mainly compare the Ajax technology under three. net.
1. Atlas
Atlas disadvantages:
Atlas is also the most difficult to master among the three technologies. It has completely encapsulated Ajax technology. After learning the Ajax principles, it is still very difficult to learn about Atlas. It is equivalent to learning the C ++ principles and then preparing to use VC ++ for development.
Due to the large number of packages, if an error occurs during the development process, developers will not be able to start, only to request Microsoft to remove the bug quickly. There are not many of these bugs, and will they affect development? From the perspective of my current usage, there are still many bugs. For example, some pages developed using Atlas cannot be clicked consecutively. If you click consecutively, an error occurs.

Advantages of Atlas:
After all, Atlas was launched by Microsoft. Due to its good encapsulation, it has implemented a large number of complex applications. The page development process is simple and suitable for large-scale project development.
The overall performance of Atlas is the highest among all Ajax frameworks.
For the convenience of porting the original project to the Ajax framework, Atlas is undoubtedly more advantageous, from the project of the general framework to the Ajax framework, using Atlas, you only need to nest everything on the original page into updatepanel to implement Ajax.

2. ajax.net
Advantages of ajax.net:
Ajax.net only encapsulates Ajax technology in the simplest way. developers can develop any task.
Ajax.net is especially easy to use. If you have learned the Ajax principles, you can use ajax.net for development in just a few minutes.
Disadvantages of ajax.net:
Ajax.net does not have page display controls, so it can only be used to call methods or webservers in the background class on the page.
The development workload of ajax.net is large, and it is not suitable for porting existing projects to the Ajax framework.

3. anthem. net
Advantages of anthem. Net:
Anthem. Net is a lightweight Implementation of ASP. NET Ajax, or even a perfect lightweight implementation.
The conciseness of the anthem. Net code greatly reduces the chance of script errors. When a project uses Asp.net ajax to frequently click a page, the script error sometimes occurs, and the script does not exist in Anthem. net.
Anthem. NET is open-source. If an error occurs, the source code can be high.
Anthem. NET is easy to use.
The performance of anthem. NET is not much different from that of Atlas.
Disadvantages of anthem. Net:
The amount of anthem. Net code is only one of the 12 points of Asp.net Ajax, and it cannot take into account so many complex applications.
You can only use your own page control when developing a page in Anthem. net. You cannot use the control provided by vs2005.

Summary:
There are many other Ajax frameworks that will not be compared here, such as magicajax.
When developing projects, I would like to see that Atlas and ajax.net are used less, and anthem. NET is used more. Debugging fails because of an atlas error. The development workload of ajax.net is too large. Developers must implement the huge page display results by themselves. Although the features of anthem. NET are simple, how many complicated problems will we encounter during project development? If so, you can use Atlas and ajax.net to solve them. In addition, if anthem. Net cannot meet the requirements, you can expand it on your own to contribute to open-source software.
Magicajax is also a very good tool. Its performance is similar to that of Atlas, and its stability is better than that of Atlas, but it is billed.