A lot of buzz is being generated by Adaptive Path, the company that invented the acronym

Figure 1: The traditional model for web applications (left) compared to the
As you can see in this diagram an

Figure 2: The synchronous interaction pattern of a traditional web application (top) compared with the asynchronous pattern of an
You can see that by eliminating the need to go to the server on every request, you are able to significantly speed up the user experience and response to user input. The use of a single acronym
It gives developers something to rally around. A new way of looking at programming online. A n ew way of providing web services.
So you may be thinking, why should I care about some arcane acronym that stands for “Asynchronous JavaScript+CSS+DOM+XMLHttpRequest.” The reason is because this is the technology that Google is using to develop some really interesting applications.
I spent 10 minutes today fascinated by Google Maps. It is the best application I have ever seen on the web because of the amazing graphics and the response time. Don’t get me wrong. This is not as fast as a desktop application but it is still faster than other web apps I have used.
You may be thinking that Flash can do much of what
In my opinion the birth of this new acronym may give programmers something to rally around and users will love the amazing graphics that



Technorati
Del.icio.us
Slashdot
Digg
twitter
I had this very same epiphany last week. I started asking the supposed "learned" about this Ajax thing, no one knew what I was talking about. The second I saw google maps - my jaw dropped.
http post/request seems like Fred Flinstones foot powered car next to the tripped out H2 that is xmlhttp.
It is without a doubt the future of the web.
This is a really interesting site as well(http://www.panic.com/goods/). the implications are amazing. Drag and drop web design interfaces that are really slick can't be far behind
This is "New"? XMLHTTP has been built into Internet Explorer since version 3.0, and the first "big" implementation of it was Outlook Web Access, written by the Microsoft Exchange team.
It's nice to see that the Mozilla / Firefox people have finally gotten around to including it in their browsers, but frankly, they've really shot themselves in the foot. You can't even make an XMLHTTPRequest in Firefox for a lousy RSS feed if its not in the same domain the page came from.
Acronymns abound. They really don't mean much unless there is really some new, innovative technology behind them. In this case, not.
You may be 100% right as the buzz about Ajax seems to have already slowed down. I did some searches on Ajax news and didn't find much. Still I think Ajax is a better name than XMLHTTP or whatever other acronyms people used to use. Sometimes a name is more important than we give it credit for. WiFi is a better name for example than 802.11x.
In order for Ajax to become popular, we will have to see lots of really interesting web apps that use this technology in new and innovative ways. This in turn will spur imitators.
If you are interested in Ajax maybe you would like:
Panoramio.com