Ajax worry and inspiration: into also script, defeat also script

ajax| Script

The study of Ajax for some time, from the initial view of the distant, to the near, and then to the actual hands-on realization, understanding more and more deep, the idea is more and more. In particular, there has been a while running to study web2.0, but also to realize the great behind Ajax, secretly for its lucky, and more and more optimistic about the web.

But Ajax in my heart but there are some how can not get rid of the shadow.

Suddenly like the spring breeze, Ajax so very abrupt pop up. At the same time, there are also popular Web2.0, these words are now incomparable with drum power, anything, as long as the two sides, it became mysterious, unable to contain.

But others say Ajax is a gimmick because he is a new bottle of old wine.

In fact, the popularity of Ajax is its new bottles of old wine. The 3 concepts that Ajax represents, asynchronous, Javascript, and XML, should be said to be nothing new.

Asynchronous? In the operating system we have already learned, then the name is multithreading.

Javascript? He was already red all over the river, thinking of the DHTML of the year.

Xml? Look at those nouns, SOAP, RSS, WAP, etc., which of these nouns leave XML?

The combination of these nouns creates a powerful force, in that their design is different, and the thought behind the design is different.

The reason why these nouns can be flourishing, is that they have been applied very common, has been deep into every corner of the world.

Even a slightly fresher XMLHttpRequest in Ajax is not without a substitute. In the era of IFRAME we have achieved the same function, but XMLHttpRequest can do better than we do, help us to do more.

JavaScript is an adhesive that blends all Ajax technologies together. The so-called AJAX application is actually an application running in the client browser environment. The application uses the DOM to manipulate HTML to show the information to the user, through the event mechanism corresponding user action, through XMLHttpRequest and server communication, the use of the Protocol is HTTP, the data carrier is XML, and this application is composed of JavaScript.

JavaScript is a very powerful language, in other words, the universal language (general language). JavaScript has a lot of convenient and powerful features that allow us to develop a feature-rich product. But JavaScript is a script, or a script, which is a bad luck he'll never get away with.

There are a lot of problems with the script, such as its not strict enough, slow to perform, and so on, here is only a discussion of code reuse.

As applications become more complex and code grows, code reuse becomes important. The low-level code reuse is the source code level code reuse, flexible, but expensive. More advanced platforms, such as Java and. NET, have provided more advanced code reuse, intermediate code level, and even target code level. Even on the. NET platform, according to Microsoft's great idea, code in different languages can be unified and run together. It can be imagined how much combat power this will bring to the. NET Platform. Different languages, different platform code can be used here. Integration is now the main theme,. NET has a better future (as envisaged).

In contrast, scripting JavaScript is a much different area. No one cared when the app was small before us. However, when we implement a large number of AJAX applications, when we gradually enrich our clients, we will find JavaScript's mishap, that is, the script's mishap. Of course, we can adapt JavaScript to fit our needs, but then you'll suddenly find that JavaScript (if it's still called that name) is no longer a script.

In other words, the script is characterized by flexibility, so it is used to handle some flexible, but low development costs. But the traditional program language is more rigorous, the development cost is high, but his operation and maintenance cost will be low. So, when we realized that Ajax was a kind of customer-segment capability, and the server-side function shifted to the client, we had to re-examine the awkward position of JavaScript. The reason why JavaScript is so favored in AJAX applications is that it's flexible. Flexible JavaScript gets popular and becomes standard gradually. Ajax uses JavaScript to be able to quickly apply to become today's favorite. On the other hand, because of the flexibility of JavaScript, it is decided that Ajax will not be optimistic tomorrow because it is doomed to not be large. (if he still relies on JavaScript, also called Ajax, not AC (#) ax.) )

Look at the competitors behind Ajax, Micromedia's Flash,java Web start, and even. NET is likely to become his formidable enemy. When it comes to promoting its next-generation operating system, Microsoft focuses on his presentation. Imagine who still uses JavaScript when all IE supports Microsoft's latest presentation technology? Who still uses Ajax?

But even if Ajax falls, it doesn't matter, it's a transitional technology in itself. But what Ajax has to do is to brainwash us:

Ajax tells us to attach importance to scripting because they are flexible.

Ajax tells us to value users because they pay for it.

Ajax tells us to focus on interaction because software is a service.

Ajax tells us to value the Web because convenience is more important than anything else.

Ajax tells us to take off the blindfold and think about it in a different way. When you have a face that ignores the changes in the world, it is the world that abandons you, not the one you think you are.