WEB2.0 's one-hand rule

A previous article on the CSS is not too many people understand, the result is a long time in meditation on CSS piece of article How to write, so far has not come to a satisfactory answer. The new year, looking back on the days before; there are a lot of things in the company that have not written about technology for almost one months, and have not paid attention to the events of the group for a long time (shielding several). The two days back to the group to see, found that the quality of the decline, chatting more and more people, talking about 78 bad things are more and more people. ...... It seems to be time to write something out and inspire the website to reconstruct the morale of the people and set a clear goal for everyone.

Back to the subject, about WEB2.0. This noun should be no stranger to everyone. Over the past few years the Chinese internet has been noisy, some respected, some people think hype. But do all these people know about WEB2.0? Yes, I am not just pointing at the c[x]o of the Internet companies, but also those who want to rely on a piece of commentary bloger. Or everyone will feel that I am such a person, then we together first to see what we now know the WEB2.0 of several:

WEB2.0 is not a technology-led concept;
WEB2.0 is a series of web sites as a representative of the general;
WEB2.0 is based on the user as the content source;
WEB2.0 was born in March 2004 at the hands of Dale Dougherty, vice president of online publishing and research at Aureli Media company (O ' Reilly Press Inc.).
Here is to say is from here the author and the company. Dale Dougherty was one of the first people to propose APIs. For such a technical person to say a concept that is not technology-led, this alone can be considered an unbelievable scam. I remember the words EMU said: "A technical influence of the technical people, once engaged in the work of the loss of technical influence means that has no influence." Any work he does without influence loses confidence and then fails. ”

On the other hand, a series of web sites as a representative of the general designation. Is that according to the patterns and architecture of those websites called the WEB2.0 era site? So there are so many "dead WEB2.0". Because it is impossible to reach the so-called end point from the point of view of development.

3rd, many of the so-called content of the king, and then the user as a source of content. So where do our users come from? Is it that the domestic other than Tencent, Taobao and other companies with large user groups outside the company can not enter the WEB2.0?

You can see that on the "What is WEB2.0" (official translation) of the speech after the anti-tolerance Tim O "Reilly", the points of attention after being conveyed by the people are so porous. It's just like a book that no one in the page world knows about. "Web Refactoring" has become a div+css in China. But you do not know whether you have seriously read the book, which has Jeffrey Zeldman said such a sentence-"that is, the use of a lot of div tag as a structural element, there is no fixed standards and reasons to say no, but in fact this is a more advanced table abuse." "The original is" OK, if know anything about templates, you'll know that you can use tables or <div> tags. OK, it "s the same for nested templates. In other words, if your wanted to yank out of the tables and replace them with <div> tags, for your still can use nested temp Lates and it'll still work. There is no rule or technical reason this says can "T use <div> tags in templates or nested templates or library Items. " (The source of the network). So what really hinders our development is not the other people's books that we "take", but the ducks that are pinched by the invisible hand by Lu Xun's writings.

However, this article is not a single save as many people just say his problems and not solve him, that is, I want to let you know the WEB2.0 principle of the single hand. According to the second half of Tim O ' Reilly's speech and the intention of Dale Dougherty, we can refer to the following 5 points (such as RSS and XML merges to the XHML category, etc.) by referring to the technical merger similar terms in the historical order:

1. Api
2. Xhtml
3. Css
4. Ajax
5. Seo

We will name the above 5 technical points separately according to our finger's successively:

We all put up one of our hands again, just as you learn the "right hand law" and "left-handed rule" in physics class follow me to do a test: (Of course, based on a normal human being) bend any finger individually to close to the palm to see if the remaining four fingers can be straight and comfortable with the back of the hand. Have you found something strange: When a single finger is bent, only the thumb [API] can complete the specified action.

Let's take a look at what this means:
When the single technology is integrated into implementation, only the API can complete the task. However, the single API in our opinion should only be our users in the Internet, because these users will continue to open up their own "interface" (here without talking about the technical API), constantly output the information and information we want, At the same time our WEB2.0 can only rely on this point can survive first, that is, we common VC hit the money. In such a WEB2.0 era, the product has been very difficult to survive, the survival of the more difficult, and in a prolonged protracted war in a survival stage but do not know how to use these techniques to maintain their livelihoods, will not cut expenditure is tantamount to finding death.

For example, the description of one by one, such as the tail refers to [SEO] is common garbage station, there is no technical skills to make a static page, the number of garbage after being moved to stop the webmaster to be forced to transform into a server provider. Then the ring finger [AJAX], here would like to take Rice as an example, said that before in the group and people bet a meal they can not support two years, unless the transformation. The reason for not looking at him is because too much use of server operations, the page can not be static, static data, there will be too much traffic consumption and the server Spit page performance consumption. Again talk about the middle finger [CSS], The corresponding form of the past WEB1.0, for a business to open up a new terminal platform will need to recruit a group of development team; in WEB2.0 's time, we just need to use a development team and an excellent page refactoring staff, through the page of the CSS connected media properties connected to the Screen "," handheld "," TV "and so on to show different performance, so as to achieve income and expenditure.

This shows that in the WEB2.0, to be truly invincible must be five fingers bent together, is five-like technology to catch. Then many people would be surprised that both SEO and Ajax technology are inherently conflicting, so how can they coexist in the WEB2.0 technical field? We look at our hands, the ring finger [AJAX] and the tail refers to [SEO] close, connected. In our product form, such States only appear on our "Portal" and "client" side. We should be for the user to access the most (for the whole station) client side do Ajax, static templates, dynamic pull data, but also with the help of Ajax not be indexed by the search engine to protect the user is not publicly published, encrypted and point-to-point information and content On the other hand, we should be in the portal side of the page file static, so that users want to release the information more easily to be indexed by search engines to increase the site and the popularity of users and information cohesion. (This is about the information itself rather than the users themselves, as many so-called WEB2.0 sites do today, but there are some technical details here.) On the other hand, the use of sophisticated XHMTL (including semantic page files and RSS) to represent the structure of the page, and the use of multi-directional CSS as a platform for low-cost expansion of multi-platform terminals. Finally, use a multiple-support plug-in and a standardized API (which refers to the technical API) to nibble on the Internet that is not your domain, like the meal no Plug-ins (11 blog service providers), as well as the chirp of the input channel (9) and API this one personally feel very successful. , compared to the current other big brother has shown a "laurels" flavor, such as "moving Tool" BLOGCN, the input path of the surging ... Wait a minute.

This rule has been in my house for almost a year now. has been the spirit of watching 3 do 2 say 1 of the way, however, this 3 has been done for almost a year, until now to tell him all because of the temporary heart has not seen a higher 3. However, I believe that "willing"-there will be some, just as the first thought of these before is also experiencing such a period of No 3. But now the situation is really need to write him out. We can also see that the five of the technologies mentioned here are the responsibilities of our website refactoring personnel (refers to the site refactoring rather than page refactoring and page production), so we should have the responsibility and obligation to do the Chinese WEB2.0. Although we are just technology to face, and the real WEB2.0 of course there are other levels of certainty. However, some of the implementation details of this rule is because the principle of commercial confidentiality is not open, I hope everyone can forgive.