If I had name the biggest difference between the attitudes at Microsoft vs Apple as to how they build their operating systems, it’s that one of Microsoft’s primary concerns is backwards compatibility, whereas Apple isn’t afraid to jump off the cliff to a better place, knowing it can’t go back.

A lot of what is going on underneath the hood of Windows involves shims, workarounds, and downright kludges to allow old apps and a gazillion third-party devices to work. From a purist’s point of view, it’s got to be ugly. — Ed Bott

You wouldn’t see Microsoft making a jump across processor lines like Apple did to Intel, saying a (prolonged but firm) bye-bye to anybody who bought a Mac before this year. Microsoft would get crucified for such behaviour.

But now that Microsoft has mature, stable (and free) virtualisation technology, maybe they can make a leap. What’s to stop them totally re-engineering Windows to remove all the messy stuff (some of which dates right back to the early versions of DOS) and telling anybody who wants to run an old application that they’ll have to do so on a virtual machine?

(From an idea out of a discussion with Matt.)

• The history section of Raymond Chen’s blog documents many things in Windows that are the way they are because they always have been. The PC clock being on local time instead of UTC, for instance, dates back decades.

The Commonwealth Games are looming, as is the week’s extension of summer time in Eastern Australia.

Microsoft have issued a patch for most (but not all) versions of Windows. What they haven’t done is made it an automatic update for affected users, nor made it easy to find — it’s not shown on the Microsoft Australia home page, for instance, you have to search for it. They also haven’t provided a smooth way of reverting to “normal” summer time for next year: users have to remove the patch and manually set the timezone.

Meanwhile Apple have done… nothing. Charles Wright has tracked down how to fix it on Macs, which involves going an finding a timezone update file on an ftp server, untarring and ungzipping, running an obscure (if you’re not a Unix god) command… jeez.

Ask yourself: is the typical non-geek computer user going to seek out these solutions, and even if they find them, are they going to bother to figure it out and do it? I’m betting not. I’m betting a lot of computers will be an hour out during the week of the summer time extension.

This is very sloppy behaviour from both sides of the OS fence, and something the millions of Australian computer users won’t be too happy about in March. (Though most will have forgotten about it by late-April, no doubt.)

PS. 29/3/2006. Still getting a lot of comments here, but there is a later post on this topic here.