OStatic

There are many reasons to love the open source approach. The events chronicled in an article on NetworkWorld surrounding an exploit affecting Firefox outlines, quite elegantly, how open code outwardly appears risky, and -- well, wide open -- and how that same quality generates faster fixes and stronger applications.

A security researcher discovered that Firefox is vulnerable to remote memory corruption, enabling attackers to execute malicious (or at least very much unauthorized) code within the context of the browser. While security researchers spend countless hours searching out bugs and vulnerabilities, it's not usually the case that the offending attack finds its way into the public eye. Yesterday, however, this little exploit was published on several security sites. The vulnerability affects Firefox versions 3.0 through 3.0.7, on all platforms. In less than 24 hours, developers issued a patch for the vulnerability, to be included in next week's 3.0.8 release.

Digital Arts Online has a thorough break down of some of the snags the Firefox development team has encountered as it continues work on the browser's 3.1 release. TraceMonkey, the JavaScript engine that's responsible for the browser's performance boost, seems to be what's holding its actual release back.

According to the forum posts the article points to, both Firefox developers and those focusing specifically on TraceMonkey agree that a decision has to be made -- but whether it's better to release Firefox 3.1 without TraceMonkey, release Firefox with TraceMonkey disabled by default, or give the developers a set amount of time before making the decision at all -- might be a sticking point.

When Google's Marissa Mayer told TechCrunch's Michael Arrington that Chrome would drop the beta designation less than two days ago, the implication was that it would happen pretty quickly. When you consider the length of some beta stages (and drawn out, fanfare driven gold releases), Chrome's 1.0 release yesterday was fast and relatively quiet.

InformationWeek shares a little of my aforementioned concern that taking an application out of the testing stage prematurely can have some serious consequences, and it does offer some insight into Google's thought processes.

TechCrunch's Michael Arrington is reporting that Google's vice president Marissa Mayer told him in an interview that Chrome will be coming out of beta.

Mayer didn't give a definite time frame, but one would assume that this would mean sooner rather than later. This announcement is a little surprising for a few reasons.

On Monday, the Mozilla team announced the general availability of Firefox 3.1 beta 2 for testing. Aside from increased localization support, a new Private Browsing mode, new tab switching and preview behaviors, and support for a number of new web technologies (such as the W3C Geolocation API and offline applications), the new beta release uses the TraceMonkey JavaScript engine by default, and has made tweaks to the Gecko engine to speed content rendering.