Also, like Google’s Chrome, Mozilla has planned for a 16-week development cycle. So, we can expect to see a new version of Firefox in about 4 months. Which is about the same time when we can expect a new version of Internet Explorer.
Oh wait, never mind…
Visit ArsTechnica for a review.
Microsoft released Internet Explorer 9 a couple of days ago. There are various sites such as Ars Technica where you can go read reviews and benchmarks. I have tested it in my HTML5/CSS 3 test page and no changes have been made. It shouldn’t be surprising since the last version I tested was the Release Candidate. I’m sorry to say but Microsoft still has not addressed how they are going to go about updating the browser. Of course they will release patches if any security holes come about, but I’m more interested in holding Microsoft at it’s word that they are going to follow web standards. Microsoft has said that they will not add support for unstandardized web specifications. What happens when they become standardized?
Also, Google released Chrome 10 and are well on the way to releasing v. 100,000 sometime in 2014. Just like IE9, Chrome has no change to my test page. However, Chrome now natively supports CSS 3 box-shadow! No more -webkit prefix for Chrome. The same cannot be said about Safari though so, for now, -webkit-box-shadow remains.
As I read via Computerworld, Microsoft has launched it’s IE6 watch site. It’s purpose is to monitor IE6 usage drop via NET Applications. While it’s great that Microsoft is truly bent on seeing the demise of IE6, I can’t help but point out that they slowed the progression of the Internet by continued support of the almost 11-year old browser. But, hey, at least you get half a cookie for finally trying.
Now, how about addressing how you are going to update and upgrade Internet Explorer 9 after it comes out?