In fact, we wonder every day when IE6 will really die, but since its release in 2001, IE6 has always dominated the domestic browser market, and until now it still occupies more than 50% of the domestic browser market share. But I think, whether you are an ordinary user, a website developer, or a domestic browser developer, we should all take some measures to jointly promote the demise of IE6. If you are a loyal user of IE6, please upgrade your IE6 as soon as possible.Give you a reason to upgrade IE6? All right:
(Partial reference from: http://mashable.com/2010/01/18/5-more-reasons-why-ie6-must-die/ ) If these reasons are not enough, please take a look at the reasons why foreign users insist on using IE6. Of course, there are some jokes here. If you happen to be one of them, please don’t be angry :):
Of course, in the country, users who insist on using IE6 may still have two other reasons:
Front-end developers can strive to abandon IE6 compatibilityIf you are a glorious front-end developer, I hope you can do as much as possible to make IE6 die faster:
Browser vendors should take more responsibilityA sentence that comes to my mind: There are a lot of rich and stupid people here, come quickly! This is of course just a joke. However, it is said that the number of Internet users in China has now reached 360 million! And this number is still growing. This is obviously a huge market. Therefore, major companies have recently entered the browser market and launched their own brand of browsers. After years of competition among Maxthon, The World, Tencent TT, and Green Browser, Sohu Browser, Sina Browser, and 360 Browser have emerged. However, all of them are based on IE as the kernel (Maxthon and Sohu browsers have versions with IE and WebKit dual kernels), and they do not have their own kernels. So, dear netizens, don't think that your computer is safe just because you use a so-called "safe" browser. Its kernel IE itself is not safe, so how can these shell browsers be safe? However, some browsers will add some features to prevent you from operating them incorrectly. For the domestic browser market, I think this "Warring States" situation is very good. At least it can popularize some "browser" knowledge and improve netizens' awareness of the Internet and Internet security. But I think domestic browser manufacturers should take more responsibility. Your browser product does have many features, many useful or cool functions, and it pays more attention to the usage habits of Chinese people. But when users are attacked due to IE vulnerabilities, will you take responsibility? Or should we put the blame on Microsoft? This seems a bit unfair. For IE, the most secure, powerful and stable version should be IE8. If you can encourage users to upgrade their kernel to the latest version, it will definitely reduce the security risks you have to bear. In addition, reducing the support for one kernel will also reduce your development and maintenance expenses. SummarizeIt will take time for IE6 to exit the stage of history. Users are lazy and unwilling to upgrade on their own initiative, and Microsoft's browser upgrade model is so old (Firefox's upgrade prompt and Chrome's background automatic upgrade model save a lot of trouble). So we can only rely on our own strength to promote the demise of IE6. |
<<: Docker enables seamless calling of shell commands between container and host
>>: Using HTML+CSS to track mouse movement
This article uses examples to describe how to cre...
How to solve the timeout problem when pip is used...
How to obtain SQL statements with performance iss...
Table of contents Overview 1. Clearly understand ...
I didn't use MySQL very often before, and I w...
Table of contents Introduction Install 1. Create ...
During the development process, we often use the ...
I'm currently working on my own small program...
Tab switching is also a common technology in proj...
Table of contents Array destructuring assignment ...
Cookie It is a standard way to save the state of ...
Benefits of a programmatic approach 1. Global con...
Disabling and enabling MySQL foreign key constrai...
A registration page template implemented with HTM...
Table of contents 1. MySQL time type 2. Check the...