Mozilla Deprecates ThunderBird

Mozilla is cutting development on ThunderBird.

And where's Chandler when you need it?

Seriously though, it's probably an inevitable move from Mozilla. Desktop email clients that look like Outlook are a legacy product. And Mozilla has to husband its scarce resources very carefully these days.

Though, actually, there are two bold and exciting moves that someone *could* make with email clients.

1) Scrap the desktop GUI and write your new UI in the browser with the standards of  HTML / CSS / Javascript (or CoffeeScript). I'm not saying that TB should move to being "webmail". Keep TB as an installed client on your local computer. But use the browser as its front-end.

Going forward, that would be cheaper to maintain, more fun, and make it easier to follow the slickness of things like GMail.

2)  Upgrade TB to be a more general communication client talking Twitter, Jabber and FB too.  Start to do what GMail is doing : integrate emails into the general stream of other media. Everyone wants a way to post things via multiple channels. If email clients don't evolve to talk these other protocols, some other messaging client will expand to swallow email. (As FB are threatening to at the moment.)

Mozilla Jetpack

Programming your browser in native web (html, css, javascript)

ZDNet is calling this Browser Wars 2.0 ...

I've been saying that browsers are not (and shouldn't be thought of) as a site for strategic competition. But it looks as though I may be wrong on this one.

The reason I thought that there was no room for competition there, is that I saw (and still see) standards (HTML, Javascript, CSS) rather than differentiation as dominating. There's no mileage in a slightly different HTML or scripting language.

All web-applications want to be runable on all browsers ... anything else is just suicide. And all browsers want to be able to run all applications ... and so ...

But I underestimated the part about a better experience for the users which isn't related to the browser content. Browser features such as speed, privacy, off-line caching, new UIs such as Enso-like "ubiquity". All the browser makers have demonstrated that they can create some excitement in these areas.

Also, what's becoming clearer is that "privacy modes" can disrupt the kind of cookie tracking which allows, say Google, to serve relevant adverts, which makes browser innovation in this area a direct attack on Google's revenue. (And so also makes us realize how much of an interest Google have here.)

So, I think I was still right about standards in web content (at least for the moment). But as the browser really starts to replace the desktop operating system it takes over a whole lot of other responsibilities as well. And there's clearly some room for differentiation there.