How to report new technologies [csdn discussion draft]

New technologies and new products are emerging every day. Even technical experts in a single field can hardly grasp all the new technologies in the field. How can we understand and report new technologies and new products as far as possible as technical editors away from the front line of practice and provide readers with the most valuable information? According to McLuhan's media theory, the media can be understood from four aspects: What does it strengthen? What does it replace? How does it develop? How will it be reversed? We can learn from this idea to seize the pulse of new technologies.

1. enhancement: A new technology or new product must be able to do anything. This is not something that it can't do before, or is not doing well or is not doing fast. A technical report should find "this thing", so readers can know: what is the use of this thing, and under what circumstances it can be used.

2. Replace: when there is no such new technology, people will solve the problem in a bad way. These old methods are the objects to be replaced by new technologies. Find these "replaced objects" and you will be able to compare them to see the advantages and disadvantages of the new technology.

3. Development: The New Technology certainly did not suddenly jump out of the stone today. It certainly has a development process. Some people have done similar things before, and some people have put forward relevant theories. By finding the footprints of these development processes, readers can view new technologies in the overall trend of technological development, thus reducing the instinct to reject new technologies.

4. Reversal: new technologies also have their shortcomings. Some people will make up for these defects to form new technologies in the future. If you can find these defects and point out some possible solutions, you are likely to seize the future technological development trend. Do not worry about inaccurate predictions. People will only remember the correct predictions.

Let me give you an example: Echo 2 was released yesterday. How can we report this? Start from these four points. ECHOProgramUsers can write Web applications in an object-oriented way, as they write swing. Therefore, it enhances the expressiveness of web applications and can be used by Web applications with a large number of user interactions. Previously, Echo 2 provided these ready-to-use display controls and interactive means for JavaScript controls and frontend/backend interactions that require a large amount of interaction, therefore, it replaces the hand-written web rich client and workaround on other Web frameworks (such as struts), such as pageflow. The idea of ECHO has always been web rich client, but it was previously not done in Ajax mode, but brought a lot of data in the session, or based on the "Request/response" model, now Echo 2 has become Ajax, which is its development path, indicating that AJAX is the right way to do such applications. Echo 2 has two problems. The first is to use JavaCodeIt is silly to describe the interface. If you use XML to describe the interface, the amount of code will be much less. Second, its front-end/back-end communication protocol is not standard, it is a set of XML based protocols developed by itself. In the future, a unified communication protocol will be developed to allow front-end controls of different sources to interact with backend services of different frameworks, this Protocol is probably Hessian burlap; these two points will be the future direction or reason why Echo 2 will be eliminated.

As you can see, we only need to grasp these four points and add some conventional things, such as the release time, which is a great technical/product report.ArticleIt has a large amount of information and is very valuable. If an incorrect understanding is found, the reader may make comments accordingly, and the feedback will be more valuable.