Ajax Sucks Most of the Time

Vo0k writes "It seems that everyone is excited with what AJAX promises, and only few look at what it breaks as well. The article at Usability Views offers a critical view at the new Microsoft technology, pointing out some problems it creates, like breaking bookmarking, making the 'back' button useless, problems with printing, accessiblity and more. The single-sided view from the article provides a good counter-balance for all the craze."

Comments

Re:as in all new directions...

[14erCleaner]

the article was basically showing how those same things were valid at one point for using frames as well.

Please clue me in, then: do frames no longer suck?

wrong

[circletimessquare]

breaking bookmarking, making the 'back' button useless, problems with printing

ok, try any of those things with any standard non browser-based application: same problem. the point is, everyone raves about ajax because it makes the browser work like a standard application. but we are suppposed to be critical of ajax because, wait for it... it makes the browser work like a standard application. huh?

wrong. howabout you accept that what people are doing with ajax is SUPPOSED to do these things, and apply criticism of ajax ONLY from that point of view. that is, the point of view of how well ajax does what it is SUPPOSED to do. but criticizing ajax for making websites act not like a browser, when ajax is SUPPOSED to make websites not act like browser, is just silly

if you don't understand what ajax is supposed to do, don't criticize it, because you don't understand it. the difference is: some people know what ajax is supposed to do, and think it is good for SOME situations... and some people don't know what ajax is supposed to do, and think that everyone who wants to use it thinks it is the cure for every problem in the world, and therefore criticizing it like this way is useful. it isn't