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.
- DevOps meets ALM in the Cloud - Cloud DevOps PaaS To improve software delivery performance and effectiveness, teams need automation, governance, architecture best practices, and increased team collaboration. Find out more.
- Coding with JRebel: Java Forever Changed With JRebel, developers get to see their code changes immediately, fine-tune their code with incremental changes, debug, explore and deploy their code with...
- What Developers Want: The End of Application Redeploys Eliminate application restarts in Java with JRebel! JRebel is a JVM plugin that eliminates application redeploys from the Java development cycle, a process...
- How a German energy company saved 1 day per week of development time with JRebel Check out the following case study to see how Heliocentris, a global energy supply and efficiency company deployed a development solution that was...
- Top 4 Digital Signage Fails Join RMG Networks for a look at four of the most common reasons digital signage fails in corporate businesses. Learn about strategies to...
- It's not too late...Get Your Mobile Questions Answered Live! How can IT provide seamless and secure mobile communications and collaboration for all? Join this live Webcast as IDG asks an expert panel... All App Development White Papers | Webcasts