do not worship at the altar of AJAX?
Why I do not worship at the altar of AJAX
I thougt this was a good argument. Although I tend to think that more AJAX rather than less is desireable. Too many of the neat tricks we see on the web today have a AJAX helping hand to through them all out.
they make it possible, and indeed almost inevitable, for the programmer to define their own user interface. This isn’t a good thing; people are used to web pages. They think they know how web applications should work. When they click ‘back’ they expect to GO back, not leave the application entirely. When they click bookmark they expect to bookmark what they’re looking at. When they change options, they don’t expect those options to take effect until they click submit or similar; some AJAX applications, however, put them into effect as soon as they are changed. In many AJAX applications, when you click to load some data, absolutely nothing happens until the data is loaded; no browser waiting symbols. And so on.
0 TrackBacks
Listed below are links to blogs that reference this entry: do not worship at the altar of AJAX?.
TrackBack URL for this entry: http://kennethhunt.com/mt/mt-tb.cgi/1654
I've no issue with the neat tricks, provided a non-Javascript version is provided, and I've used some of them myself on occasion. What I'm not keen on are these Javascript-based applications, which hopelessly break expectations of how a web app should behave.
I recently started writing MacOS widgets, for which AJAXy stuff is more or less essential...