For those of us who work on the ‘front end development’ side of things, there’s a careful balance we hang in regarding new browser releases. The short version is that as new browsers approach their release candidate status, we need to be checking and double checking our work in them to make sure that their change logs don’t break our work.

At the same time, there’s a known issue with the fact that, more often than not, running the latest beta or release candidate alongside with the production version (and, if you’re a really good developer, one previous version back from the most current production release to take care of things). Internet Explorer is notorious for this and I recall the headaches I went through beta testing it. I essentially resolved to (and continue to resolve to) use multiple virtual machines, one for each version of IE.

[Dave Martorana] created a little launcher app that, when copied to your Apps folder along with the accompanied Firefox3.app file (appropriately renamed so it wont overwrite the stable version), will let you create and/or select an additional profile, as well as the version of Firefox that you wish to use. It’s clean, it’s simple, and it works.

Neat. I have to run 2.0 for web development, but the rest of my crap can go in 3.0