Last year Mark Pilgrim released a free e-book/site called “Dive Into Html5” (http://diveintohtml5.org/). The site/book has served as a valuable resource on a recent Html5 project we’re working on here at AIS, and I have frequently gone back for details on topics such as local storage and canvas. It is an excellent book for any bleeding edge web developer. It is so choice. If you have the means, I highly recommend picking one up.
This week, Mark posted his observations on how publishing a free e-book (which is also purchasable in print format) works well for him, and that it gives great insight into what parts of the book are being read, and by whom. He then makes the following observation:
6% of visitors used some version of Internet Explorer. That is not a typo. The site works fine in Internet Explorer — the site practices what it preaches, and the live examples use a variety of fallbacks for legacy browsers — so this is entirely due to the subject matter. Microsoft has completely lost the web development community. (emphasis mine)
I forwarded this internally within AIS, and a nice debate ensued. One common complaint was the hyperbole of the statement, and I agree; a more accurate line would likely be "Microsoft as a browser vendor has lost significant mindshare in the bleeding edge web development community."
For instance, our Html5 app is backed by ASP.NET MVC 2 and SQL server. We do all our development on Windows, in Visual Studio – we’re looking to deploy to Azure. Clearly we’re MS developers. But we could just as well have done the app in Php against MySql running on linux and apache, and we’re taking cues from folks using python, java, Rails, Node.js, php and God knows what on the backend.
At the same time I haven’t used IE by choice for about 5 years, maybe more…
I was asked what I thought MS could do to gain back some developer mindshare – so here goes:
- My thoughts are that if Html5 and the set of bleeding edge technologists that go with it are any kind of priority for MS, they need to do some or all of the following:
- Find a way to upgrade the legions of IE 6, 7 and 8 users to IE9. This will obviously not be easy, but they could do something similar to what Google did with Chrome frame (i.e. make IE9 a plugin for the older browsers), or they could do something like the makers of the “IE Tab” Chrome and Firefox extensions do, allow IE to be hosted inside Chrome, and only activate it for certain sites. Or let users install IE9 side by side with the older versions. All of these would have as goal to encourage end users to use the latest possible browser for the task they need it for, and to make them install IE9 instead of Chrome or Firefox.
- Make IE9 the paragon of standards compliance. (They are actually getting close to this...)
- Bring IE9 to WP7 and whatever tablet software they're coming out with.
- Reduce the focus of Silverlight as a browser plugin, and make it more about web-deployed desktop apps.
- Evolve the Dev tools in IE9 to become better than Chrome's inspector and the Firebug plugin.
- Separate the IE development from Windows to allow quicker iterations
- Do more things like the jQuery deal. The world of CSS is a mess (we desperately need mixins and code forks like those provided by media queries), MS could take the lead here…
The point is, whether Mark’s browser percentages are statistically valid as an indication of web developer’s preferences, or to what degree Microsoft is lagging/losing developer mindshare; these are not the pertinent questions. The fact is that Microsoft is now not a leader in emerging web development areas – maybe they never were – but should they want to be, they need to take action. IE9 is shaping up to be a great browser, and they need to push it aggressively.