Firefox 3

[TimberWolf]

I've had version 3.0 for weeks already

Me too. Well, dunno about weeks, but at least a week.

[realityhack]

Any easy ways to install and run two different versions at the same time, as there is with 'multipleIEs'?

[vhadiant]

I've had version 3.0 for weeks already

That would be Beta 5.

[Tensai]

Who's planning to download Firefox 3 when it is released later today (hopefully) and help them set a record for most downloads in 24 hours?

http://www.spreadfirefox.com/

Why, is there something wrong with Internet Explorer?

[voodooflux]

Why, is there something wrong with Internet Explorer?

Not much, not since IE7 was released anyway.

[NickFitz]

Not much, not since IE7 was released anyway.

IE7? The one Microsoft have abandoned development of, opting for a completely new rendering engine for IE8, because they've finally accepted that it's impossible to fix?

[NickFitz]

Any easy ways to install and run two different versions at the same time, as there is with 'multipleIEs'?

You need to install them in their own folders, then create a separate profile for each one.

Details differ slightly depending on OS, so JFGI

[voodooflux]

IE7? The one Microsoft have abandoned development of, opting for a completely new rendering engine for IE8, because they've finally accepted that it's impossible to fix?

It's a helluva lot better than IE6 was - it became much easier to achieve consistency between IE7 and Firefox.

[NickFitz]

It's a helluva lot better than IE6 was - it became much easier to achieve consistency between IE7 and Firefox.

It still has some truly awful bugs though, including some that IE6 doesn't have.

Agreed, it's an improvement, but not enough of one, which is why MS have now officially accepted that it's a dead code path. Apart from anything else, its reliance on the internal hasLayout construct means that some aspects of CSS2.1 could never be properly supported.

[voodooflux]

It still has some truly awful bugs though, including some that IE6 doesn't have.

Such is the path of software "progress"

Agreed, it's an improvement, but not enough of one, which is why MS have now officially accepted that it's a dead code path. Apart from anything else, its reliance on the internal hasLayout construct means that some aspects of CSS2.1 could never be properly supported.

Kudos to Microsoft for finally recognising that, although there is the danger that with a completely new engine we end up effectively having to target another browser.