OStatic

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.

Via OSNews comes word that the developers bringing Chrome to Linux have opted to use GTK over Qt as the browser's framework.

The development team's decision wasn't an easy one. The questions they addressed about Chrome's appearance and behavior, what end-users need and expect, and how to make it work smoothly on the Linux desktop are highly subjective, and in some cases, emotionally charged. The FAQ on the Chromium developer's site states that while both toolkits are capable of doing the job (WebKit handles most rendering with the exception of some form controls and dialogs), the team opted for GTK due to their level of familiarity with it.

Microsoft Watch's Joe Wilcox, in solemn observance of Friday the 13th, compiled a list of Microsoft's ten most unlucky breaks. The strokes of misfortune chosen were weighted according to heinousness (with #10 being least signficant, and #1 the most).

Checking in at #7 is the development of the Linux kernel. Putting aside Microsoft's whole Schrodinger's cat sort of approach to Linux over the years (Linux is not a threat. Linux is a threat), it is interesting Wilcox (and the analysts who helped him narrow down the list) focused on the kernel as the bad break.

The end of the year is a self-indulgent time, when those who write about technology stop making lists of the best, worst, and most mind-numbingly mediocre applications they find and pause to make lists about tech trends in the upcoming year.

Assessing the past is easy: it has been an interesting year for open source software. Predictions that come to pass, unless suitably vague, just fall into the lucky guess category. The one prediction I am sure of for 2009: Open source software will hold its own when it comes to growth and adoption.

My other predictions? What do you think?

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.

The Mozilla Foundation's Mitchell Baker reported yesterday that Mozilla's revenues were up approximately 12% in 2007 over 2006. She also mentions a few matters that are worrisome. Though eWeek's Joe Wilcox's predictions of Firefox's demise are premature and without a doubt require a sizeable grain of salt, he makes a good point concerning revenues coming from Google versus Google's commitment to the Chrome browser.