Internet Explorer 9 launches tonight, we've got your early look
engadget.com
engadget.com
— HTML5 forms. More precisely, <input>s with types of "search", "tel", "url", "email", "datetime" (even more, anything of /^date.*/), "number", "range", "color"; <select>, <datalist>, <progress> and <meter> elements. Also no support for :valid, :invalid, :optional and :required selectors.
— "placeholder" (!), "autofocus", "autocomplete" and "multiple" attributes.
— HTML5 history API (let's all enjoy the hashbang kludges)
— HTML5 drag and drop
— HTML5 app cache
— Microdata
— IndexedDB
— FileReader and FileWriter APIs
— WebSockets
— WebGL
— Web Workers
(Source: http://habrahabr.ru/blogs/ie/115460/#comment_3739820 [in Russian]. The list contains only features that are supported by at least one browser.)
I would like to be able to just try it out instead of asking basic questions but first I would have to make a Windows 7 VM etc. etc.
See: http://blogs.msdn.com/b/ie/archive/2011/02/15/user-experienc...
[1] http://ie.microsoft.com/testdrive/IEBlog/2011/Feb/uellr-imag...
I guess they'll get the current IE8 users, hopefully even convince some people to get new machines or upgrade to W7 -- all good for a web developer. But as an actual competing browser? I don't think so.
Also, most IE users run Windows XP. IE9 will never be available for Windows XP, so those users are stuck (unless they switch to a third party browser or buy a new computer).
3rd party developers target older OS versions all the time; Microsoft should be in a great position to support XP. And even if they don't want to, they should still have an official stance that encourages the use of some modern browser, even if it means they have to suck it up and recommend Firefox for XP users. Better still, issue a service pack for XP that installs Firefox automatically; then IT groups can be sure that a modern browser is on all their machines, and internal apps can finally target the modern browser and require its use.
Microsoft has been pushing people off of XP for ages, but many people hold the misapprehension that XP is 'good enough' in some sense. This is further complicated by the fact that most people who still use XP don't want the system to change. If Microsoft were to release such a service pack, the first thing that nearly all of the IT groups of whom you speak would do would be to block it from automatically installing. Those that wouldn't would have already set up the base install to have a modern browser (IE8, Firefox, Chrome).
Who are you including in that category apart from Apple? Compatibility with 30-year-old OS features is often considered a worthwhile goal among current UNIX descendants.
> I see very few people complaining that Apple killed the PowerPC line, and XP far predates that.
Is WinXP compatible with x86 and x86-64? Is Win7 not compatible with those? I don't see what point you're making by mentioning CPU architectures. And the 'universal binary' made this switch largely transparent to owners of either CPU.
> many people hold the misapprehension that XP is 'good enough' in some sense
Leaving aside the accuracy of this, surely if it is a misapprehension then it should cause problems only for those people. Instead Microsoft have made it clear that it's a problem for their own profit growth and that those users need to be coerced into upgrading.
But even that's being done in a half-assed way that makes it more of a problem for web developers. Which other Microsoft titles are being developed to be XP-incompatible? Certainly not Office 2010. Aside: backwards compatibility was largely maintained under Mac OS Classic from 1984 to 2001. The break, coming with OS X, was necessary, not contrived.
On XP, Microsoft could add tons of value by supporting a solid IE9 update. This is where browser improvements are truly needed. Let that be where their engineering talent goes.
You're right that forward-looking IT groups are already well aware of how to deploy a modern browser. It's the other companies I'm wondering about.
Consider what would happen if Microsoft announced these plans, and basically said that in 6 months they would start deploying IE9 by default on XP "for security" (which would basically be legitimate). Once both IT managers and contractors alike can see Microsoft's plans, the writing would be on the wall, like a mini-Y2K; there would be plenty of people you could call to have your broken IE6-only web apps updated, probably enough to keep the prices reasonably low. Obviously I'm speculating on that, but my point is that Microsoft is in the best position to set this ball rolling. A lot of the problem could solve itself. Putting IE9 on another OS isn't really going to tempt anyone using these ancient PCs.
It's true in some sense. Vista really made Windows users question further upgrades. I personally couldn't wait to move from Windows 3.1 to 95, 98 to 2000, 2000 to XP. Super excited for these upgrades. I had no such enthusiasm for Vista after seeing initial reports and usability findings. Thankfully Windows 7 is far superior to Vista and XP and definitely a much more inviting experience.
Sometimes you don't just cut the cord, you evolve the old and the new.
Chrome 12: SunSpider: 417.5ms Peacekeeper: 7030 Points
FF4 RC1 scores 97/100 on the Acid3 test, IE9 scores 95/100. We don't need to go into the accuracy of the rendering, they both fail. It would be nice if they caught up, Apple has been shipping an Acid3 compliant browser for 21 months already. Then there's SunSpider, the results of which differ as different hardware is used, but in all the reports that I found, IE9 scores better than FF4 RC1. And lastly, there's Peacekeeper. FF4 RC1 is dead last in that test, by quite a long ways.
So it didn't really matter whether Engadget used FF 3.6 or FF4 in their tests.
UPDATE: IE9 is out now: http://www.beautyoftheweb.com/