But even so, I still think this Next Big Thing called AJAX could well turn out to be a disaster for the web (disaster with a lower case "d," that is.)
Why? The simple answer is "state", or lack there-of.
In the early days for the web, a Uniform Resource Locator pointed to a page on the web that stayed the same, at least until updated. Later, many URLs pointed to dynamic content, but most returned deterministic content; i.e. they returned the same HTML even if accessed multiple times. However web pages with AJAX content have an infinite potential number of states, many for which no URL will ever exist.
Why is this bad? Let me use examples. Have you ever tried to email a friend a Google Map at the precise zoom level you are viewing? Fortunately Google makes it possible with the "Email" link, but how many other web developers will go to that level of effort?
As another example, try using GMail. Click around a bit. Now click the refresh button. Shazam! The page view you had disappears and you return to the Inbox. Now click the [Back] button. Do you go to the state where you were previously? No! You go back to the prior web page, whatever that was. You cannot go "back" to the prior page in an AJAX site because the browser doesn’t manage the state for you. Instead the AJAX developer has to manage state and provide a "Back" link or you won’t be able to go back. So what’s the likelihood when he’s behind schedule to release a new website he’ll go to that extra effort, or even that he’ll know how?
Okay, these are just nits from someone resistant to change, right? Well, not exactly. The biggest problem with lack of state is that programs, such search engines, can’t process AJAX web pages programmatically; Google, for example. Anything hidden behind AJAX’s interactivity is also hidden from search engine view.
In the July 4th, 2005 issue of Information Week, Google’s own Bret Taylor claims clicking on a blue URL and loading a page is "the old Web User interface." Ironic that the company that spawned interest in AJAX is the one that depends most on the programmatically indexed web pages that AJAX will minimize.
2 Replies to “AJAX: A Panacea, or a Pending Train Wreck?”
I don’t know – this doesn’t seem like such a big problem for a lot of sites. Most content-based sites cannot really be AJAXified unless the author is a bit nuts. And it’s still easier to build a simple page-based site.
Still, as a site author, if you go AJAX, you’d better have a fallback strategy – imagine a mailing list archive that was fully AJAX – it wouldn’t get indexed by google and co. The author would have to make sure that there were "virtual" static pages that served as entry points for all the unique "items" in the site.
Basically what I meant was, even though AJAX can allow developers to craft wonderfully interactive user interfaces, AJAX has a dark underbelly for which developers and managers should be cognizant and careful.