This Just In: AJAX Doesn't have to be -- AJAX!

Yep, Jesse James Garrett, that cowboy of marketing hype, said it very clearly (according to Brent Ashley).

The Decree has been Handed Down:


Ajax is no longer an acronym to be limited to its original initials.

According to Jesse, as long as these two basic ingredients are involved, what you have is an Ajax application. (Hallelluja! Praised be the AJAX Gods! Lordy, Lordy!) :
  • asynchronous interaction model

  • browser-native technologies

  • Hopefully, organizations like the new OpenAjax Alliance will be able to reach consensus on what needs to be done and how in order to take us to the next level in Rich Internet Application evolution.

    Open Ajax Alliance? What the hell is that! Why don't we have an Open Javascript Alliance? How about an Open HTML one? What's the purpose?

    Anyway, the message is that now we can call it "AB" - definitely a step in the right direction!

    You see how very adaptible it all is? Even if it ain't really "AJAX", you can still call it -- AJAX! I can't describe how very comfy and relieved that makes me feel!

    Not only that, we can probably get rid of the "Asynchronous Interaction Model" one since a large percentage of so-called "AJAX" webpages do not use asynchronous methods anyhow. Now, "Browser-native" technologies, I suppose, is a "given" also, since without a browser, you'd probably just be watching TV, right? (Of course, for accuracy's sake, I'll probably want to look that one up in my HillBilly SpellChecker). Now this is GREAT NEWS - it means we don't need ANY REQUIREMENTS - therefore, ANYTHING can be AJAX! Whoopee! Though I walk in the valley of the shadow of XMLHTTP, I shall fear NO SCRIPT! WTFOMG! AJAX ME BABY! IT'S THE AJAX REVOLUTION! OMG! CRADLETODAGRAVE, BABY!

    Ain't marketing grand? Acronyms don't have to be limited to their original initials! Now if I am correct in assuming we can get rid of the "A" for Asynchronous and the "B" for browser-native as above, we don't need any acronym at all, and we can just go back to describing such applications as employing "Remote Scripting" which is the way it has always been anyway. Of course "the World AJAX Conference in Amsterdam" would suffer a bit, not having anything much to talk about, but - hey, That's Progress (TP).

    Listen: It's still Remote Scripting to me. That's what it was when Microsoft brought it out in 1998. You can "seminar it to death" if you want to. Eventually, as with any other fad, everything will settle down. Oh, people will still be doing "AJAX" -- just as they have been since last century. Probably by that time we'll have "Web 9.2" (And probably ATLAS 4.2 also).

    I can't seem to get this across to them. It's not AJAX - it's "AHAB" - A Lotta Hype And Bullshit!

    Comments

    1. Anonymous6:42 AM

      About The Codebehind vs. Inline Code ASP.NET Debate I must say it was the most biased opinion I've ever read about that particular subject.

      You couldn't give one single example where inline coding fits and accused those who use it of lack of knowledge or just being lazy to learn code behind.

      Internet, in this case WWW, native tongue is scipting. That's the nature of the service: a server response for a client request. While the protocol remains the same, things won't change. At least that much.

      There's been so much tryings to pull it to a desktop-like programming but there's no use. That's just not the nature of the WWW.

      ReplyDelete
    2. This relates to AJAX? That was eons ago! Back to the Future, man!

      ReplyDelete
    3. Anonymous11:09 AM

      Jeez, Peter...

      Don't sugarcoat it. Tell us how you really feel about it.

      ReplyDelete
    4. Peter -

      You really have to make yourself a tshirt like mine!

      - Brent -

      ReplyDelete
    5. Brent,
      I gotta hand it to ya. I've been UPSTAGED bigtime!

      Peter

      ReplyDelete

    Post a Comment

    Popular posts from this blog

    Some observations on Script Callbacks, "AJAX", "ATLAS" "AHAB" and where it's all going.

    IE7 - Vista: "Internet Explorer has stopped Working"

    FIREFOX / IE Word-Wrap, Word-Break, TABLES FIX

    System.Web.Caching.Cache, HttpRuntime.Cache, and IIS Recycles

    FIX: Requested Registry Access is not allowed (Visual Studio 2008)