Fri Mar 28
With the vast difference in standards compliance between Internet Explorer 6 and 7, and the recent announcements about even greater things to come in Internet Explorer 8, the time has come to get rid of the bane of web developers once and for all. That’s right: save a developer; don’t use Internet Explorer 6.
I wouldn’t even be able to start to count the number of hours I’ve spent fixing things for IE6, and as it’s been 18 months since it’s replacement was released it really is time to get rid of the old dinosaur. There are plenty of great alternatives out there, so make sure you upgrade – and make sure your family and friends (who you act as “tech support guy” for) upgrade as well.
Together we can fix the web.
Tue Mar 18
A long but worthwhile read on the history (and histrionics) surrounding the current great New Web War by the estimable Joel Splosky.
Thu Mar 6
The web world is currently alight with discussion around the new Microsoft Internet Explorer 8 software slated to be released later this year. The bulk of this conversation has been about whether IE8 will display pages with its much improved (it passes the Acid2 test) standards-complianct rendering engine. It seemed that we would have had to do some fiddling to get this to work but now it appear we don’t have to. That’s a good move, well done Microsoft.
I’ve just been and had a look at the website for the IE8 developer beta, and noticed something pretty interesting. they’re introduing a new feature called WebSlices which are like feeds for certain parts of web pages. Developers who add the required code to their pages will allow visitors to subscribe to updates of those sections of the page, which many of the same facilities afforded to RSS publishers.
My initial thought was that they’d have used some horrible proprietary syntax to make this happen, completely ignoring the established ways of doing this. But I was wrong. Almost.
Looking at the whitepaper for WebSlices it appears the IE8 team have taken large slices (excuse the pun) of the hAtom format to build their new feature. The main change being using a “hslice” rather than “hatom” class on the parent element of the feed. I’m not sure why they’ve done this, hAtom seems to do everything they need. Maybe it’s just Microsoft wanting to keep some level of control, maybe there’s something more to the story.
At any rate, this is is going to make it easier for developers to provide subscribable content on their web pages. Hopefully it will bring microformats – and web standards in general – to the attention of people traditionally deep inside the Microsoft world.