Firefox 3.1 delivery slips; developers question TraceMonkey progress
Their comments came as Mozilla's head of engineering acknowledged that the browser's final delivery date will slip.
In a message posted to a company message forum, Firefox developer David Baron wondered how long Firefox 3.1 should be held up by TraceMonkey problems. "Without TraceMonkey, we probably could have shipped 3.1 final by now, or, if not now, within the next month," he said. "I think there should be a limit to the amount we're willing to slip 3.1 to accommodate TraceMonkey, and I think we should decide what that limit is."
Graydon Hoare, a Mozilla developer who works on TraceMonkey, agreed. "I have to concur here," he said in a message on the same forum thread. "TraceMonkey is really cool tech, and a remarkably quick initial development, but it's not the whole enchilada of the browser." However, Hoare said it made more sense to disable TraceMonkey by default -- an approach used through Beta 1 -- rather than pull it from the product.
The biggest bug now delaying Beta 3's release is a TraceMonkey issue.
But Mozilla will probably not pull the engine, said Mike Shaver, Mozilla's vice president of engineering, in an interview Saturday. "We're always looking at all of our choices, but I don't think it's likely," he said. "TraceMonkey is a big part of Firefox 3.1, and a big part of what we want to have for users."
Saying that Firefox 3.1 in its current form is "quite a stable product," Shaver said patience is a development virtue. "We're taking the time to get this worked out," he said. "No one will remember when Firefox 3.1 shipped other than the guy who writes the Wikipedia entry. But people will remember how Firefox 3.1 runs."
Comments by developers such as Baron and Hoare are in no way a "revolt" by programmers, said Shaver, who added that such discussions are normal at Mozilla and during software development in general. "There's always talk about what we should trade off," he said.
Mozilla conceived Firefox 3.1 as a "fast-track" update to June 2008's Firefox 3.0, but the new browser's progress has been much slower than originally planned. At one point, Mozilla was shooting for a final release as early as the last months of 2008, and the company hinted that it would use just a single beta to do so.
- Ten Factors Shaping the Future of Application Delivery Download this research report conducted by Enterprise Management Associates (EMA) to learn how those that are seeking to accelerate application delivery are leveraging...
- Using Continuous Delivery to Improve Software Delivery Learn more about the challenges impacting organizations and how continuous delivery processes can be a key success factor in accelerating software delivery.
- Global Bank Improves Quality of Application Development Read how this financial institution centralized build assets, cut development time in half and added additional security controls.
- HTTP Status Code Cheat Sheet Look at the Graph, Find the Code and Boom - You're Solving Problems. Identifying and understanding common HTTP status codes can go a...
- Cloud BI in Action: Recorded Webinar of Customer, Kony, Inc. See how Kony, Inc., a leading enterprise mobility company, is using TIBCO Jaspersoft for Amazon Web Services and Redshift to achieve embedded analytics...
- Cloud BI Overview: Jaspersoft for AWS Check out this overview of Jaspersoft for AWS, to easily and affordably build business intelligence solutions as well as embed visualizations and analytics... All App Development White Papers | Webcasts