I don't understand; how does theming your window manager help against this? I'm assuming the malware bit is *inside* the Google Chrome window, so even if you themed your windows with say a Pikachu theme, the *insides* of the Chrome window would still contain the rogue site, imitating Chrome's red and white-colored malware block UI.

The only way out of this is if crucial error pages are protected with some sort of "sign-in seal", like Yahoo uses for its login screens.

Don't know about NT4 (not used it since the 90s), but XP and up have SteadyState. Check out its disk protection feature, it's functionally chroot with a wipe after app exit.

> Release a hotfix to disable the hlp resource locator.. as you should have done as soon as you got the bug report.

There's one already, but it won't be delivered via Windows Update, users must opt in: On this page look for the Fixit Link ( http://go.microsoft.com/?linkid=9735564 ) The problem is that switching off a feature without fully testing repercussions -- which is what would happen if this was pushed out via Windows Update -- is not good and can cause other things to break.

Sort of off topic, but I've always wondered: Can I be on an Atkins diet and still be a pastafarian?

You must've not been check the stock markets lately, these days AAPL is almost as big as MSFT and gaining fast.

(via)

But Apple does in fact have a solution to the fact that iPhone original and 3G users don't get the latest and greatest. It's calling "upgrading" -- the same strategy they encourage in Mac-land. So far their "lifecycle policy" appears to be -- we'll support the latest version and the latest-1 version. Anything before that, don't expect much.

And in both Mac-land and iPhone-land, developers develop for the latest and greatest as a result, knowing that eventually the users they want to reach will upgrade.

I don't like it myself, but it's true -- people who stay with old OSes etc rarely buy stuff. Big-picture wise, it's a waste of time targeting them.

The Times and the Sunday Times are "just a start" according to News Corp. Presumably the Sun and the News of the World will also follow. However, the Sun's readership is solidly lowbrow and it's not a "quality paper" by any stretch of the imagination, I don't know how many of actually pay to get celebrity news and gossip online.

The interesting thing is that Murdoch's Sky News website remains free to access -- they haven't announced any plans to charge for that.

> Just wait, in ten years, Chinese firms will be outsourcing there.

They already are planning to do so (warning: the FT restricts how many pages you can view, even if you register)

But it's not surprising. After all, pretty much all the Japanese auto manufacturers now actually produce in the US.

IE8 doesn't install automatically in the same way that Chrome updates automatically from 2.x to 3.x or Windows installs security updates. You get a new dialog box prompting you to "upgrade your web experience with a new version of IE", or language to that effect. LOTS of of non-expert users just hit the [X] Close button at that point (for whatever reason -- fear of installing new software, having been taught that installing random new software off the Net is bad, and so on).

Browser upgrades ought to be invisible. But because of Microsoft's awkward IE 6 to 7 to 8 transitions, it isn't. And it keeps a lot of people from upgrading as quickly as they should.

> That big new Corvette Engine does not fit in 8 year old Chevy Cavalier, is that GM's fault?

Car analogies for software are imperfect. You can't fit a bigger engine retroactively into a Chevy Cavalier, but you can backport new software to older OSes. Microsoft even does it for their Windows Live software (Live Messenger has some very snazzy Windows 7-style graphics).

The real reason for not supporting IE9 on XP is that they don't want to. Imho this is stupid given the number of XP users out there (and XP is here to stay 'til 2014), but if they don't care about marketshare ... *shrug*.

While I agree with everything you say, I'll point out the following (and I usually support MS on many issues):

• Windows Live Messenger 14.x (labelled '9 series' or something) has lots of snazzy Windows 7-style visual effects and was backported to Windows XP (I am aware this is less elaborate than what IE9 is planning).
• Opera supports 2D acceleration under XP
• The technical arguments against backporting to XP are hogwash. Chrome has superior sandboxing on Vista/7, but gracefully downgrades on XP
• Microsoft is shooting themselves in the foot by effectively ceding the modern XP browser market to Chrome, Firefox and Opera. XP will still be around 'til 2014-2015. That's 4-5 years. If they think they can afford that, well, more power to them.

Excellent point. Last year I visited a customer with ~200 Windows 2000/IE6 desktops. They don't connect to the Internet and will get updates until July 2010. They'll probably move to Windows 7 in 2011, especially as virtualization can guarantee their old apps will continue to run.

These guys spent next to nothing on software and very little on hardware for the past 10 years. It doesn't work for everyone but they saw it as a good deal.

XP users savvy enough to upgrade to IE8 probably also have another browser. Very few corporate intranets have mandated XP/IE8. I foresee many developers having to support mainly IE6/XP and Firefox* in the near future, and maybe a quickie test on IE7 and IE8 if you have resources to do so.

* The idea is that if you wrote a reasonably standards-based site and tested with Firefox, it will work well in Chrome/Safari/Opera. Feel free to test with any other standards-based browser instead.

The CrunchPad was supposed to be a dead-simple, cheap $200 tablet. Closer to production, it looks like it'll cost more like $500. A $99 device would be nice, but I'll believe it when I see it. A decent screen + NAND memory + battery alone will add to the cost.

> When you're buying a web-based application, you make sure it works on every browser you can get your hands on.

_Every_ browser? seriously? Then we'd have to ditch this newfangled web thang and go back to VB-style client/server apps.

We do test for IE7 and Firefox, and are currently testing and deploying IE8. Chrome still has loads of site-compat problems. Opera has really improved over the years, but even with the latest 10.5 version things remain broken, even on well-trafficked public sites like Google and Facebook. It does work with the internal apps I've tried it with, but I couldn't put my hand on heart and swear it was compatible with _everything_.

We do have a simple rule to enforce security: our proxy blocks the IE user agent from accessing the external internet (and the desktops are locked down so spoofing isn't a problem). IE is an intranet browser for us. Those who need internet access (mainly devs) get Firefox.