OStatic

The Mozilla Foundation has posted its financial statements and tax info for 2008, and a FAQ on the topic for those of us with short attention spans. While plowing through financial statements may not be the most exciting topic for Free and Open Source advocates, it's worth taking a look at what Mozilla has achieved as an independent project, where it's going, and how other projects might be able to emulate Mozilla's success to fund more and more FOSS development.

The good news is that, as of the end of their 2008 fiscal year, Mozilla is weathering the lousy economy pretty well. According to Mitchell Baker's post, reported revenues were up 5% from 2007, and the bulk of that revenue comes from the Firefox search functionality linking back to Google, Yahoo, Amazon, and eBay. But Moz got dinged by the financial crisis in 2008, losing nearly $8 million of its long-term portfolio.

Though the Opera browser isn't open source, it's free and its new server-in-a-browser feature, Unite, is really making significant inroads toward online collaboration. If Chrome and Firefox are to keep their edge over Opera, their development teams had better sit up and take notice.

Opera's Unite technology lets users run chat rooms, host Web sites, and share files that even people not using Opera can access. The interaction is all done via a central Opera Unite server ? Opera Unite uses a proxy between the server and its clients (found at operaunite.com) to avoid the need for any special firewall configuration, writes the development team. Unite launched today with six features but is calling on the Opera community to design and create any new services they'd like to see available.

Read on to have a look at what Opera unite can already do and why Google and Mozilla haven't cornered the market on browsers just yet.

Late last week, Sam took a close look at the rapidly changing browser landscape. In one of the posts linked therein, Keir Thomas speculates that Firefox may well have just given up the ghost, what with an alpha version of Chrome now being available for Linux (or, at the very least, Ubuntu).

I don't think it is, nor is it going to be, quite that easy. Firefox isn't without issue -- or momentum. And Chrome for Linux? In all reality, it doesn't exist, yet. Chrome may have a number of advantages over other browsers, including Firefox, on other platforms. But if it's still too early to call this fight on Windows, declaring the superior browser on Linux is pretty much a coin toss.

According to Mike Arrington at TechCrunch, several sources say that the Mozilla-based social browser, Flock, will soon shed its Mozilla code base and start using Google's Chrome framework for future releases.

Flock's CEO, Shawn Hardin, responded to Arrington's post, saying that the browser's upcoming 2.1 release is being developed, and will be released with, its traditional Mozilla underpinnings. Hardin does not explicitly say that Flock will move to Chrome, only that the browser space has been heating up rapidly in the last few months, and that the Flock development team will continue to make architectural decisions that balance what's best for our users and what's best for Flock as a business.

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.