Any sufficiently advanced vision piece is indistinguishable from Black Mirror.
Everyone who calls for WebKit in Internet Explorer is exactly the same kind of developer who would have coded to Internet Explorer 15 years ago (and probably happily displayed the best viewed in badge).
It’s happening again, and every petulant, lazy developer who calls for a WebKit-only world is responsible.
First, the browsers competed on having proprietary crap. Then, the browsers competed on standards support. Now, finally, the browsers are competing on what they can offer their users.
This a great step-by-step walkthrough from Rey on setting up a remote version of Internet Explorer for testing on Mac.
I mentioned this a little while back, but it’s worth remembering just how many people are using Opera Mini …and how many more are about to join them.
Bring it on!
This is fascinating—it looks like there might be an entirely practical reason for Microsoft to skip having a version 9 of Windows …and it’s down to crappy pattern-matching code that’s supposed to target Windows 95 and 98.
This is exactly like the crappy user-agent sniffing that forced browsers to lie in their user-agent strings.
Opera Mini is about to be installed as the default browser on a few more million phones.
One more reason why you should never sniff user-agent strings: Internet Explorer is going to lie some more. Can’t really blame them though—if developers didn’t insist on making spurious conclusions based on information in the user-agent string, then browsers wouldn’t have to lie.
Oh, and Internet Explorer is going to parse -webkit prefixed styles. Again, if developers hadn’t abused vendor prefixes, we wouldn’t be in this mess.
A good explanation of the litany of woes that comes from Internet Explorer 8 being the highest that users of Windows XP can upgrade to. It’s a particularly woeful situation if you are a web developer attempting to provide parity. But there is hope on the horizon:
2013 will see the culmination of all these issues; support for IE 8 will drop of rapidly, users of XP will find an increasingly broken web, the cost of building software in XP organisations will increase.
There is an elephant in the Microsoft store.
Nishant gives a great overview of the responsive redesign of the Microsoft home page, ably abetted by the Paravel gang.
Nicholas is inside my head! Get out of my head, Nicholas!
What makes the web beautiful is precisely that there are multiple browsers and, if you build things correctly, your sites and applications work in them all. They might not necessarily work exactly the same in them all, but they should still be able to work. There is absolutely nothing preventing you from using new features in your web applications, that’s what progressive enhancement is all about.
Well, I guess this is one way of encouraging people to upgrade their browser.
This vision thing commissioned by Microsoft shows a future-friendly networked world where content flows like water from screen to screen.
Paul paints a grim picture of our future support nightmares with multiple Internet Explorers, each one with multiple buggy “compatibility” modes.
Translation From MS-Speak to English of Selected Portions of Dean Hachamovitch’s “Native HTML5″ announcement [dive into mark]
Mark Pilgrim translates Dean Hachamovitch’s utterly bizarre and nonsensical announcement of IE10 that kept talking about “native HTML5.”
Microsoft, Mozilla and Opera have formally submitted the WOFF font format to the W3C.
Microsoft are trying to patent sparklines. Twunts.
Ben calls bullshit on Microsoft's defence of Outlook's rendering. Ben, as usual, is correct.
The 26 step process required to add +1 to a feature request in IE. Franz Kafka is alive and well and living in Redmond.
This is kinda sneaky but quite clever. Subtly encourage IE6 users to upgrade.
Bend over 'cause Microsoft is about to stick it to us standards-savvy developers. Again.
Schadenfreude by software. Every singe Zune on the face of the planet froze at exactly the same moment.
A handy microformats toolkit from Microsoft(!) making it easier for developers to write, style and find microformats (hCard and hCalendar in particular). Neat!
Håkon is not happy with the default settings in IE8. Deep in the preferences, "Display intranet sites in Compatibility View" is checked.
A very handy table of CSS support for versions of Internet Explorer from 5 to 8. Note that IE8 Beta 1 is listed separately to IE8.0.
Praise Jeebus! The IE team are doing the right thing regarding the default behaviour of version targeting in IE8. Thank you, thank you, thank you!
A nice analysis and skewering of Microsoft's proposed default behaviour for version targeting.
A superbly clear analysis of the proposed default version targeting behaviour in IE8+.
The madness of the default behaviour in IE8 explained in a beautiful koan.
The timeline behind Microsoft's latest announcement.... as told by stuffed lemurs.
Rachel adds her thoughts on Microsoft's broken implementation of version switching—and very good thoughts they are too.
Great news from Redmond: IE8 passes the Acid2 test.
PPK points out a potentially dangerous aspect to Opera's actions, one that that the rest of us have missed: "Without consulting anybody, Opera is trying to give a political body the right to decide what does and what does not constitute a web standard."
David Brent at Microsoft.
Good news everyone! ClearType is turned on by default in IE7.
Fairly amusing and strangely unbanworthy.
Possible ideas for IE's icon for RSS feeds. I like number five.
John Allsopp on the importance of open formats for documents.