Google’s Chrome browser has been beating out IE usage on weekends since March 18. People are choosing Chrome for their home browser, while being forced to use IE at work during the week.
Due to Chrome’s automatic updates, more people are using Chrome 18 now, than any other browser version. It’s a delight for developers to know people are automatically going to be using the most recent version of a browser. Probably why I’d expect it to be the most recommended browser by web developers. The graph is amazing to see how quickly use of the “old” (Chrome 17) browser drops off and the new browser jumps up. Compare that to the IE8 and IE9 graphs. They are slowly switching (over years, not days).
Chrome has been experiencing slow but unstoppable growth in browser usage.
Thanks to StatCounter for the cool graphs.
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.
jQuery 1.7 was released today, November 3rd, 2011.
Check out the post on blog.jquery.com for details on the update.
- New Event APIs: .on and .off
- Better performance on delegated events (almost a 50% improvement)
- Better support for HTML5 in IE (blech, IE)
- AMD (Asynchronous Module Definition, this guy describes AMD well) support (it will work with AMD compliant loaders)
- Added jQuery.isNumeric()
I would love to thank the jQuery team for the regular updates to a platform we all love (don’t we? leave comments yes or no)
You can use the following CDNs to link / get the code:
- Google CDN:
Not Live Yet – https://ajax.googleapis.com/ajax/libs/jquery/1.7/jquery.min.js
- Microsoft CDN (Go Microsoft for getting it up so fast!):
- Official jQuery CDN:
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.
Apple and Microsoft both have a thing against Flash.
Most of my clients ask for jQuery or other non-Flash alternatives (and so far, I haven’t ever really missed Flash).
Now it sounds like Windows 8 will officially not support browser plugins in IE10.
A huge push for HTML5 and CSS3 by Microsoft, we may also see Silverlight disappearing alongside Flash.
The big problem seems to be concerns for mobile platforms, as battery life is cited as a major reason (along with security).
Windows 8 is shaping up to be a bold move for Microsoft. Will it make me an Apple user on my desktop? Will Windows 7 become the new “Windows 98” (people still never acknowledge Windows ME ever happened)?
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.
I’m usually not a fan of the opinions of investors, but I think Roger McNamee, of Elevation Partners, hits on quite few good points. Business Insider has some good bullets from the video, but watch the video:
Some ideas I agree with/find intersting in the video include:
- Shift in search technology requirements
- The greater focus on HTML5
- Why indexed search is becoming less important
- Social Media startups are useless, they should be just assumed functionality by now
- Microsoft has lost it’s control over internet connected devices
Being sick for a few days, I was late in hearing the news.
Google is shutting down the Google Translate API. Right now it’s just deprecated, with a full shutdown not occurring until the end of the year, but still … it’s happening.
They say it’s because of abuse. Abuse? On the internet? I don’t believe it.
Fortunately, there are still options for those of us who wish to use a service to translate text. › Continue reading