We have all been sentenced to an overdose of Ajax and Web 2.0. I agree that it’s fun and exciting to say that the next generation of web apps and Web 2.0 is here, but it’s going too far. There are no rules for what is an Ajax compliant application or what is a Web 2.0 app. So every new application / IDE / framework / code / website / service… now says that they are Ajaxed. One validation happens asynchronously and the app claims AJAX support as one of its top features.
It’s a sensible thing to do for marketing guys to draw attention by blowing things out of proportion, but I think techies need to be make more judicious use of the word.
Recently JUnit 4.0 was released, thankfully they didn’t say that it was Ajaxed. Hey, as I just typed this in GMail and pressed Ctrl+S accidentally, Gmail reminded me that Gmail’s the place where Ajax got its mass base.
What is an Ajax or Web 2.0 Application?
What happens when every web app is Ajax enabled and asynchronous communication is the rule and not the exception. I suppose that won’t take too long as every new web app wants to get on the Ajax bandwagon.
So by late 2007, it should no longer be fashionable to say that your app is Ajaxed. In a sense, Ajax will be dead. I wonder what will happen to the word Ajax, will it die out or morph into something new.