Link Details

"I'm not saying Ajax is bad, I'm saying it's immature"

Something doesn't mature if you don't use it.

Oh, and making me signup for opera.com to leave a comment... yeah that sucks

You have to know your audience too. Sometimes you don't care about leaving people behind. I have seriously considered making it so that people who use IE6 can't even access my blog, because that's how much IE6 irritates me as a web developer. I would not really care about leaving them behind.

Use of ajax is akin to the idea that guns don't kill people -- people kill people (sometimes using guns). Any programming tool, framework, language, paradigm, [insert other aspect of programming here] is bad if you are incapable of using it well. Some people will bastardize the use of ajax, but that's not a fault of the idea, it's a fault of the programmer.

Also, the author's conclusions don't really match up with the title. Just an observation.

It seems like another "Hey look at me!" headline. Ajax itself isn't a problem, it may be people using it poorly that are the problem. That Flickr example doesn't exactly help his point either. He took a simple page on Flickr and turned it into a giant form that's going to be confusing for people.

The point of this article is: Don't use AJAX just because you can. Use AJAX as a spice instead of a main ingredient whenever possible to stay accessible.

Sounds like it's not AJAX that is immature but the screen readers that are falling behind.