With regard to the status quo and the future HTML 5 change the views of the collision

HTML 5 are basically ready. This process from 10 years ago, has already begun, to date has experienced repeatedly. HTML 5 on the status and future development, this paper presents several different point of view.

51CTO Recommended topics: HTML 5, the next generation of Web development standards Xiangjie

If you have been concerned about the Web, you might think that Flash Player and Silverlight has entered the countdown to life, while the HTML 5 is under rapidly changing Web, everything. However, the fact that many people being evaluated in HTML 5 does not fully understand the current field. Do you know HTML 5 standard editor Lan Hickson once said, "In 2022 before the HTML 5 will not be in all browsers fully achieved?" You know, iPhone developers can now fully use the HTML 5? Do you know all the features in HTML 5 are from Web plug-in? Do you know Google Wave in its products are used in a Web plug-in do?

We need to HTML 5, as well as its significance to conduct a Web open and frank discussion. Unfortunately, you will not get any of the parties from the fanatical truth, but we need to check all the facts and evidence, and then draw our own conclusions. I have spent a lot of time to analyze this fact, in the process I have come to a couple of points.


After the efforts of many dedicated developers work, HTML 5 has been basically ready. This process from 10 years ago, has already begun, to date has experienced repeatedly. Today, HTML 5 has been in a number of platform / browser ready. However, not all the browser implements the full functionality of this standard, but some browsers have not even announced when it will achieve its full support for HTML 5. In fact, iPhone OS 3.0 is currently the only fully support the HTML 5 stable version of the operating system. For developers, this means that, for most developers who, HTML 5 is still a very long way off.

When in September last year, to see Jeff Croft's "2022" when I say shocked. It reflects a number of developers of Web standards as a whole disappointed. I have not discussed this issue with Jeff, I have been a fan of his research. After learning to achieve its full support for HTML 5 deadline, when this cruel, Jeff said, "HTML 5 is the next week or next month or in the next 15 years after the launch, this is not important. For those of us in this industry who are engaged in practical work , it is important that people really are using a browser which supports standards and technology. "

To provide customers with solutions that developers do not care about theories, they are concerned about is the reality. According to this view, if a solution of target customers is only 10% of all customers, it is not a successful solution; if it can only be 90% of the customers, also not a good solution. Customers want Web sites or applications can target customers for each member, and is now able to meet. This is my first point:

View 1:

Until at least 2014, the developer will not be able to provide customers with solutions for the use of HTML 5 (unless they are in a particular platform as described above). As for the solution to use the full functionality of HTML 5, you will be more later.

Developers can create at the same time to consider the use of HTML 5 and the current HTML / JS model solution. However, this means that developers will have to create a single solution:

1, the browser can automatically detect and identify the user with the ability to use HTML5;

2, a view of the current or older versions of the browser's full-featured HTML 4.1/XHTML 1 application:

(1) The number of support IE6, IE7, Firefox 3 and Safari 3 of the CSS file;

(2) is compatible with all browsers listed above, the JavaScript

3, full support for HTML 5 applications (which will work with HTML 4.1 almost no overlap between the application code)

For those fanatical CSS and JavaScript on the application developers, this just add another layer of complexity. In fact, the traditional developers, up until more than 90% of the networks to support HTML5 browsers when, HTML5 will enter their choice. Keep in mind that, even though IE6 as early as 8 years ago (2001) had been introduced, but most sites are still checking IE6 users.

Plug-in truth

This discussion is the core of the network we use today plug-ins. Many recent articles claim that HTML5 will be the eradication of the traditional network plug-ins one by one. In fact, this is far from the truth. Before I address this issue directly, we need to carefully look at what is a network plug-ins.

When the network plug-ins are listed, most people will realize that commonly include Adobe Flash Player, Microsoft Silverlight, and JavaFX, etc.. However, in practice also includes Google Gears, Google local client (Google Native Client), Google Earth plug-in (Google Earth plug-in), and Google audio / video chat plug-in plug-peer network. In addition to Google's plug-ins, as well as countless other vendor plug-ins. Because these plug-ins are "closed source" projects, the fact that they often have been criticized. The truth is, plug-ins have a quick development cycle to guide innovation. I'm not saying it is in the open-source projects can not happen, but I really need to develop the most advanced customer solutions, I can not look forward to truly innovative networking standards, more are already being implemented by the network standards:

Point 2:

Web standards will not always be innovative, they will only have succeeded with the implementation of those plug-ins. This stems from the fact that: standardization process is by Microsoft, Google and Mozilla dominated by such companies, unless these companies have in some product development, a place, otherwise they will not invest in the establishment of a standard in this regard. Terminology Standardization means that you get over what already exists, and then to implement it to establish a unified process.

In addition, many developers do not recognize the plug-in HTML 5 standard role. This led me to another point:

Point 3:

HTML 5 in each new feature is the reason why the increase is because the developers need to plug one has been implemented as functions. This includes the offline cache (Google Geas), canvas (Flash Player), media player (Flash Player, etc.), drag and drop (Flash Player, etc.) and so on ... ...

At the forefront of this debate is that Google Wave, a recent Google IO conference, in its announcement of this product. The rich Internet application has been referred to as the role of Web standards is a great example. However, no one pointed out that it needs a plug-in to run this fact. Indeed, the proof of what can be done HTML5 examples of Google Gears needs to demonstrate its function. In fact, it is only a small part of the functionality, but it reveals an important point.

Point 4:

Google may choose to pass the standardization process, to try to add before the launch of Wave Drag and drop functionality, but they believe that the absence of this feature, the user experience will become worse. So they choose to use plug-ins to provide the best overall user experience.

In fact, the plug-in within a year to "upgrade the network." In real life, an idea through production, quality evaluation and dissemination to the user, and then in 16 months was extended to more than 85% of the network. But the Web standard is difficult to do this:

Point 5:

As it relates to large enterprises and entities, any major change (requires your browser distributor in a uniform way to change the browser's capabilities), from initial idea to the actual implementation (in all browsers) requires at least a decade. Plus use the old version of the browser users to upgrade time, the process needs to spend more than five years.

If HTML5 is currently all the major browsers fully support, and if all of these users of these upgraded browser, Web plug-in will be subjected to a heavy blow from the HTML5 (but even so, it will not completely eliminate them) . In real life, HTML 5 and Web plug-ins or even the lack of competition, because it is the only viable solution for the fixed platform (like iPhone).

Quality and Standards

This topic makes me angry the main point is that many developers overlook in the pursuit of Web standards Shique quality. This is a video codec at the heart of controversy (around HTML5, there are many examples of such problems). Developers to choose the basis of relatively open up assessment solutions, rather than on its actual function. Over the past five years tell us? We eventually will enter an era of supreme user experience, but now a number of developers in order to open at the expense of quality. This is my personal opinion the strongest:
Point 6: Many open-source solutions in their respective fields at the top level (Apache, MySQL, Linux, Flex Framework, etc.). Inferior solutions (such as the Ogg codecs) can not be simply because they are "open" should be tolerated. If you want all browsers implement a video codec, it would make a better than H.264 for. The use of "open" solution, developers must not sacrifice user experience, enthusiasm.

When a potential customer evaluation of my work (or my company's work), they do not care about Web standards, they will be concerned about the quality and functionality. In addition, when users of my application software, they do not care about "openness", but only care about the overall functionality and user experience. As a developer and the company's employees, I can not recommend low-quality solutions. I must be able to maintain a competitive edge based on the function to evaluate all the solutions. This means that if HTML5 will be able to provide better functionality, I would think it is a good solution, but I will not simply because it is open to select it. HTML5 will work with other solutions to compete on an equal footing.


I hope these views fully clarify this issue. The question is: a specific platform, developers can now enjoy the HTML5. Now they should embrace it, and began studying the work of HTML5 and use HTML5. Traditional developers will have to wait about five years to real choice HTML5. At that time, we may already have Flash Player 13, Silverlight 5, and JavaFX 3. Who know that these versions will include? However, we can guess that they contain features likely to be included in future versions of HTML.

分类:Web 时间:2009-02-13 人气:373
blog comments powered by Disqus


iOS 开发

Android 开发

Python 开发



PHP 开发

Ruby 开发






Javascript 开发

.NET 开发



Copyright (C) codeweblog.com, All Rights Reserved.

CodeWeblog.com 版权所有 闽ICP备15018612号

processed in 0.285 (s). 12 q(s)