Boo Ajax! Promote XAP!

Thursday, March 10, 2005

Recently in the web development field there has been an increased awareness about a certain type of application development methodology. The idea of using XMLHTTP to create dynamic UI apps has been around for a long time, but it seems that it’s just starting to hit the mainstream a la Gmail, Google Suggest, etc.

A few weeks ago a certain web developer, Jesse James Garrett, took it upon himself to package up these technologies with a bow and label it: “Ajax”.

Nevermind that it’s a household cleaner, the name just isn’t good. Unfortunately the sheep are moving through the pasture and latching onto the terminology like it’s some new shiny toy:

I don’t like the buzzword and it’s not descriptive of the actual components at work. The technology is not dependent upon JavaScript (that just happens to be its main medium of implementation), nor XML, nor asynchronous communication. In light of all of this, I propose a revised label that accurately describes the technologies and doesn’t conflict with anything you can find at your local grocery store (at least not here in CA).

XAP — XMLHTTP Application Platform

It’s concise, descriptive, and you can pronounce it. XAP is used for developing Applications (or pseudo-Applications) using XMLHTTP and their use comprises a Platform. Now whether or not we’re going to cover hidden iframes is another story, but I feel comfortable leaving that out of the acronym if not the umbrella of described technologies.

Promote XAP!

Edit: This article was originally written to see if anyone would pick up the buzzword. I dislike buzzwords intensely and don’t use any in practice. Obviously this one didn’t catch on like “Ajax”, but it was a fun experiment.

written by Brad Fults

Add your thoughts | Trackback URL

Archived at: http://h3h.net/2005/03/boo-ajax-promote-xap/

26 responses

  1. captain's log

    I liked XMLHTTP when it was cleaner

    Musings about the recent rise of an old web technology

  2. jbot

    XAP (if prononouced as Zap) is not too bad. It’s memorable and doesn’t conjure up allusions with bleach. However, I prefer my alternative: RISE - Rich Interactive Scripting and Extraction.

  3. Brad

    XAP as in “zap”, yes.

    RISE sounds fine, but I don’t think it’s specific enough to use for any one platform such as this. We could call .NET Web Services “RISE”, or any number of other platforms on which “rich interactive scripting and extraction” take place.

  4. anonymous

    hey guys, what about “STEVE”

  5. Andrew Scott

    Boo Ajax! Promote XAP!

    Boo Ajax! Promote XAP!

  6. KamiKazeKiwi3

    Ajax reminds me of other things too, like SOAP… Is that a SHAMPOO standard I sense coming down the pipe?

  7. Kae Verens

    nice name. much preferable to AJAX. also, XAP (’zzzzzap!’) brings “instant” to mind, which is how I describe my own XMLHTTPRequest applications.

    I hope this term spreads and overtakes AJAX before the scourer sticks

  8. Travis Wilson

    Ya gotta figure that, for the ten years that people have been doing, uh, this thing, if there was an appropriate name it would have shown up before now.

    XAP is not good for all the reasons AJAX is not good — namely, it prescribes the use of certain tools (XMLHttpRequest) when actually describing an effect (ohmygod the page just altered itself!). This will lock you up into a stone age as soon as a better tool comes along.

    Also, XAP is harder to spell correctly. Out go the verbal conversation transmissions. “Fred” or “Steve”, names that are obviously abstract, make the most sense. But try finding “Fred” in a google search. I’m pretty sure that “ajax”, whether Jesse thought about it or not, is succeeding because it’s pronounceable, spellable, and most importantly, googleable.

  9. Brad

    Travis,

    The point behind XAP was to introduce an acronym for the implementation of this dynamic method seen on today’s webpages, as forced by JJG (I was fine living without a buzzword for the technology). As mentioned before, it overcomes the deficiencies of Ajax in the way of platform dependence up until the point of XMLHTTP, which was explicitly admitted. Had I intended to make a description for the software method as a whole, it wouldn’t have made sense to keep the name of a specific technology inside of it.

    I don’t see where you get the spelling difficulty from at all. It’s “zap” with an “X”. Once a person has seen it, it’s not easy to forget, especially given the implied meaning of something that is instantaneous.

    I agree that there needs to be a name for the abstract method and I commend you on your efforts to put together an abstract specification. I do still, however, argue that “Ajax”, *especially* being an established, well-known international brand name, is a poor choice for branding the method.

  10. Jacob Rask

    Ajax is good. Simply because that’s what it called now. Deal with it.

  11. complex

    The world doesn’t need anymore goddamn acronyms.

  12. Elliott Bäck

    You know, though, Ajax is also the name of a greek Hero who fought in the Trojan war… Aias or Ajax of Telamon was his name, and holding the camp was his game…

  13. Xen

    You know, in the old roadrunner cartoons, whenever the coyote would be buying equipement from ACME? In the danish translation, it would be Ajax. That’s why I like the name.. It’s so generic, just like the technology.

  14. tom

    No.
    1. You aren’t well enough known to make this anything more than a passing phase.
    2. The pronunciation is not intuitive
    3. It’s a buzzword. We have enough buzzwords.

  15. Brad

    Agreed. Down with “Ajax”.

  16. Mental_Wanderer

    You could all it “dogfart” for all it matters. JJG has done me a favor by making it easier to use a search engine to find out more about these specific techniques and technologies. It also makes it easier to sell its use to the marketing wonks that run the company and care more about the label than the content. Now that I think of it, I suppose “dogfart” would be an unfortunate choice for that particular purpose.

  17. NoSheep! » What’s XOAD?

    [...] According to XOAD.com: XOAD is a PHP based AJAX/XAP object oriented framework that allows you to create richer web applications. [...]

  18. is there a reason for this blog?™ :: Let’s go Zapping :: December :: 2005

    [...] Read the nice article and following discussion at Boo Ajax! Promote XAP!. [...]

  19. ResourceBlog » XOAD - Ajax framework

    [...] XOAD - Ajax framework Posted on Tuesday February 7 @ 9:59 am XOAD is a PHP based AJAX/XAP object oriented framework that allows you to create richer web applications. [...]

  20. Gospel.Goober

    zzzzap! it’s coooooool! Boo Ajax!

  21. Mental Wandering continues… » Blog Archive » XOAD AND JSON

    [...] * XOAD XOAD is a PHP based AJAX/XAP object oriented framework that allows you to create richer web applications. [...]

  22. Dave Edelhart

    How about HTTP Amodal Content?

    you know…

    HAK?

  23. anonymous

    Is Ajax pronouced as in the Dutch football team Ajax Amsterdam (Ai-Acks)? I prefer this greatly. Good team too.

  24. hmmm

    Hmm - you guys have way too much time on your own to think about stuff that really doesn’t matter in the long run…. technology come and go….. just like everything else… it’s not like you’re naming your child or anything…. I personally like the name Ajax - because its nice and “clean”… c”,) º•º

  25. Q-efx

    well, name it what it does? or name it what it is?;)

  26. Bethany

    Hmm - you guys have way too much time on your own to think about stuff that really doesn’t matter in the long run….

    It’s all about priorities, really. Ajax/XAP/whatever you want to call it is a web concept, and as such, it will likely reach far more people than, say, your child (whose name we should all evidently be agonizing over).

  27. Comment Preview

Leave a comment

Comments are posted at the discretion of the site owner. Please try to be respectful, insightful and otherwise useful to society as a whole.

(X)HTML is allowed. You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <blockquote cite=""> <cite> <code> <dfn> <em> <kbd> <q cite=""> <samp> <strike> <strong> <sub> <sup> <var>