I, for one, see a lot of value in a name. How many of you have tried to have an intelligent discussion with coworkers about “XMLHTTPRequest”? First of all, it’s next to impossible to say more than once or twice per minute.
As I recently posted on Ruby-Talk:
Think about design patterns. Most people agree that these are good things. However, most of these patterns are not new—it’s just that they’ve recently been given names to facilitate discussion about them.
When you give something a name, you can define and then hide an entire host of assumptions behind it. That’s where the value comes from.
At any rate, I really don’t care what people call it, as long as they define it somewhere, and the term becomes widely used. Ajax meets the first criterion, and is rapidly growing to meet the second, so I’ll use it.
On a somewhat related note, I’ve written my first Ajax-enabled application. It’s a simple word game-
feel free to try it out right here. No guarantees how long that link will remain viable-it’s running on a manually-started lighttpd instance. But enjoy it while it lasts. (Note: it has only been tested on Firefox and will almost certainly not work correctly with IE.)
Oh, and if you want to download the app itself, grab it here.