This has been circulating around the internet for the past few days. I wanted to post it here:
From the poster:
Dear Web Developers,
We are so very sorry about IE6.
Come, talk to us during one of the sessions, and we will show you why Internet Explorer 9 is way better.
Lee Matthews writes, in his article, Microsoft decides to automatically update Internet Explorer for everyone:
Good news, everyone! Microsoft has decided that the time has come to make sure that all users of Internet Explorer are using the most current version possible. To accomplish that goal, they’re turning on automatic updates.
If only they would force all IE6 users to update to IE9.
According to statcounter, Chrome overtook Firefox globally for the first time.
My traffic still has Firefox at 25%, Chrome at 22.6% and Safari at 28% for overall traffic (most likely due to the high number of iPhone visitors, 25% of seangw.com traffic is mobile).
Good to hear folks around the world are abandoning Internet Explorer.
Paul Irish, wrote Browser Market Pollution: IE[x] is the new IE6, which details the complexities we have coming up for us as web developers.
I’m glad to see someone fully thought this through. Browser half life is a significant issue for website accessibility.
When was the last time someone asked you to get your site working in Chrome 9? Well, that was 3 releases ago, as was IE6 (I’m even ignoring the fact that Chrome 9 was February 2011, and not August of 2001 for IE6). I’m constantly hearing that a client is asking for IE6 support. I do all I can to dissuade them (logic, reasoning, and finally .. a 30% surcharge as it requires much more time to debug and handle), but IE6 support is still an issue. Why?
Because of the half life of Microsoft browsers.
Ran across an article on MSDN (I know, right?) about the problems with synchronous XMLHttpRequests, and how it actually causes 8.4% of all hangs in IE9.
Synchronous is easier to work with, as it flows just like a user would expect. Asynchronous is slightly tougher to use, as it requires handling the response out of sync with the rest of the page’s code.
You can find some helpful information about the problem, along with some examples, and fixes at Why You Should Use XMLHttpRequest Asynchronously.
An excerpt from the article:
8.4% of all hangs in IE9 in the past month are caused by XMLHttpRequest objects blocking the UI thread with a synchronous request. That’s a huge number! With some manageable code changes, these hangs can be avoided, and developers can give their users a better experience across their websites. We’ll get into what’s happening here, what you can do about it, and we’ll give a little demonstration to see firsthand what can happen when a synchronous request hangs the browser.
Happy to hear, Google has announced that as of August 1 (2011), they will no longer support:
- Firefox 3.5
- Internet Explorer 7
- Safari 3
This means that new functionality (which will probably roll out sometime this summer) may not work perfectly in those browsers. It’s a nice move as those browsers are getting old, and the web has to set expectations as to which browsers should be supported.
ConceivablyTech has done a good job summarizing the data from NetMarketShare.
Google’s Chrome had another successful month and ended 2010 with 10.70% market share, according to Net Applications and almost 16% according to StatCounter. Microsoft’s Internet Explorer continued to lose market share on a fast pace while Mozilla’s Firefox is fighting and tightly holding on to the market share it has.
Way back when, in the times of HTML 4, and CSS was just getting started we worked with IE6. IE6 required us to do everything differently, because of the ways things were implemented. They just had to be different.
Fast forward to 2011. The world is rapidly expanding use of an incomplete spec, HTML5, and things seem OK. Browsers support it, the implementations seem pretty consistent.