It’s a week since ajaxLaunch released ajaxWrite, now it is the time for ajaxSketh to be launched to the wild. Comparing to ajaxWrite, ajaxSketch was loaded faster than ajaxWrite (I guess there are less buttons in ajaxSketch). Anyway, the overall performance of ajaxSketch is not quite as good as I expect. You will get some slow-motion while dragging an object using your mouse pointer. In addition, I don’t like some behavior, e.g., I have to select an object before dragging, otherwise, the object will be resized.

The point is "to ajax or not to ajax". This is a very interesting topic. AJAX is very popular so everyone are trying to re-implement all kind of applications. The early applications ported to AJAX are the famous office suite. ajaxWrite is a good idea and very effective since most actions are about typing and manipulating texts. However, ajaxSketch is mainly working on graphics element and, a must, drag-and-drop. Response time is critical to satisfy user experience, especially end-users. They can’t wait, in fact, they don’t know how to wait. So the problem today may be not the fault of programming technique used in ajaxSketch but my computer is too slow.

Too slow computer is just a temporary problem. So, the answer should be "to ajax" as soon as possible. This is common answer used by Microsoft for long time. They always develop something big and also impossible to run on current commodity resources. Fortunately, they know the art of postpone. The big monster will fit to all machines when it is officially released (maybe next year).

Technorati Tags: English, IT, Software, Programming, JavaScript, Review, AJAX, AjaxLaunch, AjaxWrite, AjaxSketch