tirsdag den 17. marts 2009

Taking AJAX literally makes lousy Web apps

Jeg havde det på fornemmeren ... 

I have had this thought once or twice ...


By Tom Yager

Taking AJAX literally, using JavaScript and XML to create a Web site or application, is not a best practice. Far from it. Developers coming to the Web from C-like languages stumble into the AJAX trap, and the result is bloated JavaScript payloads, page load delays for every page refresh, browser and client platform incompatibility, and user frustration. If putting too fine a point on it is what's required to put my point across, so be it: Web site developers should consider JavaScript to be their last resort, and where it is used, it cannot be used the way it typically is today. 

The fact that you can write a Web page in a text editor makes some people believe that it's easy. Free JavaScript libraries and templates for wicked cool stuff like DHTML menus, browser type forking, forums, and AJAX animation make Web site and Web app authors think that no matter how big it is, if a page loads from their desk, all's well. In the majority case, no debugging, code coverage, testing, profiling, and other validation steps are applied to JavaScript. In all other languages, these things are not holstered until a page won't load. They're essentials that you use throughout a project. [...]

Read more: http://weblog.infoworld.com/archives/emailPrint.jsp?R=printThis&A=http://weblog.infoworld.com/yager/archives/2009/03/taking_ajax_lit.html

Ingen kommentarer:

Send en kommentar