7.Comparison of Ajax and Applet

The AJAX-like approach has three main advantages over Applets. 

1. JavaScript generally starts faster than an Applet. The browser preloads the JavaScript run time, but delays loading the Applet JVM until first use. The load overhead for JavaScript gets buried in the browser start up time, when the JVM load gets blamed on the first Applet. The JVM is a much bigger and more complex animal than the JavaScript runtime. 
2. AJAX is really just HTML and JavaScript and CSS, so it acts like a web browser. That is, you can resize the window and expect to see text and tables wrapped and presented in all the normal ways. All the UI kludginess of Applets is gone. 
3. JavaScript is not constrained by the same tight sandbox restrictions as Java. Your users don’t have to deal with the geekiness of signed Applet permission granting. 

Java Applets have the following advantages over AJAX: 

· Java is object oriented. It won’t fall apart under its own weight as project complexity grows. 
· JavaScript has many bugs and platform-specific eccentricities. 
· JavaScript might be looked on as a limited or toy language designed for scripting inside a browser. Java is a general purpose language suited for pretty well any sort of computation. 
· Java security is tighter. Unsigned Applets are less potentially dangerous. Sooner or later after a major scare, corporate America is going to ban JavaScript from their machines because of security risks. At that point, all legitimate Ajax code will stop working, so I consider it irresponsible to go the Ajax route. 

Microsoft has embraced Ajax and renamed it Atlas, which presumably means they are busy figuring out how to lock Ajax apps into Microsoft and make sure Java apps stop running. 
A Part of Thiyagaraaj Websites