Certainly, in the recent past, the chances of doing an entire application in AJAX seemed remote for the vast sea of developers. The thought of writing a rich application in JavaScript, for most developers, is total anathema - akin to having one's body shaved and thrust into a pool of warm alcohol.

Please don’t write and plead for a change in my aversion to writing metric tons of JavaScript, for my heart isn't in it  - as most developers' hearts aren't in it. It is not so much the writing of JavaScript as it is the lack for tools...and the horror of debugging it. Sure tools exist but they are a far cry from what you get in the Java world.

Writing JavaScript is like changing a baby’s diaper: you don’t like to do it, but you love your child and you do it anyway. You may not like to write JavaScript, but you want to deliver richer applications for your end users so you may do it anyway. Dare I say the best developers are the ones that love their end-users?

Thus the missing ingredient is the ability for Java developers to develop AJAX applications in Java instead of JavaScript, i.e., to take the smell and rank out of it. This would allow a vast community of developers to develop rich web applications where before a select few script-heads would dare go.

Enter stage left the contender for changing the way, once and for all, the world uses the web: Google!

Google just introduced the Google Web Toolkit (GWT), a free, publicly available Java development framework. This framework allows developers to develop and debug applications in Java and deploy them in AJAX. The Google approach to AJAX development is to avoid JavaScript (for most developers anyway).

You can write all of your AJAX code in plain old Java. You can debug it. Use breakpoints.

They have a plug-in where they allow your code to run in the browser and hook back to your Java code. Then when your code is ready to deploy, you run the translator that converts your Java code into JavaScript code that can run on any browser - or so the vision states. They also have an RPC mechanism to call back to Java objects on the server for data and business rule validation. The Java code looks like AWT, Swing or perhaps SWT code. In other words, it is what most rich GUI app developers are familiar with.

The framework is also extensible, so if your favorite Dojo JavaScript widgets don’t exist you can extend the framework to support them. Most developers won’t have to do this, but you can.

One of the Google examples is an Outlook clone. It doesn't look like a web application. It looks like a rich application. If it all seems too good to be true, you are right. However, if even half of it is true, this changes everything.

Cynicism is good. Without cynicism you will be driven hither and dither, to and fro, back and forth with each new buzzword, and vendor marketing claims. However, cynicism must be balanced with potentially the most disruptive technology. The mantra at JavaOne seems to be JSF, JSF, JSF, NetBeans, NetBeans, NetBeans,. AJAX, AJAX, and AJAX. Never mind that Eclipse is the dominant developer platform by far, and most vendors that have a plug-in seem to target Eclipse first, and certainly Google has followed this model with model with GWT and released with Eclipse plug-ins.

Among the noise, there is this announcement from a company that started the AJAX phenomenon and has the most popular AJAX applications. Is this announcement from Google the most important announcement for AJAX and the most important announcement at JavaOne? It is too soon to tell if this is the most important message at JavaOne 2006 due to how much reality and robustness is in the GWT, but the potential is there. Time will tell.

• i-Technology Viewpoint: "Spring Good!"
• The Next Programming Models, RIAs and Composite Applications
• i-Technology Viewpoint: "SOA Sucks"
• i-Technology Viewpoint: When to Leave Your First IT Job
• i-Technology Viewpoint: The New Paradigm of IT Buying
• i-Technology Viewpoint: "Pessimism Leads to Weakness, Optimism to Power"
• i-Technology Viewpoint: Is Model Driven Architecture Coming Into Its Own?
• i-Technology Viewpoint: Death to the Browser
• i-Technology Viewpoint: Attack of the Blogs
• i-Technology Viewpoint: Are We Blogging Each Other To Death?
• i-Technology Blog: Can Blogging Change the World?
• i-Technology Viewpoint: Is Web 2.0 the Global SOA?
• i-Technology Viewpoint: The Five Dimensions of Blogs
• i-Technology Blog: Death-Knell For "Rich Media? Hardly!
• i-Technology Viewpoint: We Need Not More Frameworks, But Better Programmers
• i-Technology Viewpoint: What Are the Drivers of Social Software's Success?
• i-Technology Viewpoint: It's Time to Take the Quotation Marks Off "Web 2.0"
• i-Technology Blog: Google Trends on Java, McNealy, AJAX, and SOA Give Pause For Thought
• i-Technology Viewpoint: Does Adobe Flash Need Re-Branding?
• Advertising on Google.com Requires No Personally Identifiable Information (PII), States Executive
• "To Google" Is Officially a Verb: A Behind-the-Scenes History
• Google Is Ten: The Search Engine That Changed the World
• Human Error Causes One Hour's Google Search Chaos
• Google: The cause of and solution to all life’s problems