Starting from Google

I remember that when Gmail was just getting angry last year, I was eager to get an invitation from someone else. the interface at the beginning is too simple. however, out of trust in Google search, we still try to use its related products. the series of things that followed have become increasingly stunned. starting from Gmail, when sending a new mail, enter the recipient's address. It can automatically retrieve my address book based on the letters I typed without refreshing the page, then, the relevant address is directly displayed below the cursor, similar to the smart sensing effect in vs.net. of course, from a technical point of view, this is not difficult. You can use XMLHTTP to implement it. However, we all know that if XMLHTTP is returned in XML format, this speed is sometimes intolerable. however, Gmail can be described as fast. at that time, I felt that Google must have done something in this common technology. I didn't care too much about it. Later I saw that Google map also adopted similar effects, and then I saw Google suggest. It can be said that in suggest, Google applied this processing method to the peak, and the speed is so fast that you can hardly feel the pause.

Later, I learned that these excellent user experience is based on AJAX. So far, I have not seen any other company using such a large-scale processing technology like Google. therefore, when Ajax is mentioned, many people may feel unfamiliar and mistakenly think it is a javascript advanced function or a new technology. In fact, I have read an article about script callback in the previous stage. however, Ajax is not a new technology. It is based on existing technologies such as JavaScript, CSS, Dom, XML, and XMLHTTP, I prefer to regard it as a client solution framework that enhances user experience. it re-divides our existing web interaction methods. For example, the traditional JavaScript remote technology directly interacts with the background through an XMLHTTP, while Ajax creates a middle layer Ajax engine, so, our Javascript is interacting with this intermediate layer, and then the engine is responsible for interacting with the background.

If we leave aside other things and simply look at the experience that Google shows to us, we will think this is a great initiative-indeed, I also think it is a pioneering initiative-but, in fact, at least for the time being, it is far from mature enough. The thought of writing a pile of JavaScript code will make me shudder. this is not suitable for large-scale Web application development. however, I think this processing method can be used in some specific functions to improve the web user experience.

There is also an interesting discussion: Ajax: 99% bad