New Firefox makes browser war a fair fight

If you regularly read this space, you'll notice how the Google Chrome Web browser kind of grew on me, and after my initial reservations I've come to love it. Something about its speed.

But now Firefox, with its new 3.6 version, has seen enough improvements to almost make it a fair fight.

Some of the benchmark tests comparing the two intrigued me. When you figure in that impossible stability+speed combination, reviewers are calling them almost neck and neck.

Now, we don't do that benchmark stuff around here. I don't have time to mess with all that, and I'd rather put a piece of software through its paces. I'd rather max it out, try to break it, and take note of my findings. I'm not smart enough or geeky enough to plug the whole thing to an oscilloscope or whatever it is those propellerheads do.

So, take any speed or stability tests I run with a grain of salt -- or maybe even the whole shaker. Whatever test results I get depend on what mood I'm in at the time, and what I'm trying to do with the software. But I will try to max it out.

I'm one of those computer users who runs underpowered equipment (scary to think my netbook is the most muscular computer I have) and overclocks it like crazy. And to do the things I want to do, I go for lightweight, faster programs when I can. Even my usual graphical interface -- Fluxbox -- is really little more than a plain background, taskbar, and menus that I write myself from text files. That's why I was so eager to get my Chrome on, because of its simple and fast interface.

Being the experimenter that I am, after reading some of the reports I had to download Firefox 3.6. I've always liked the 'fox, used it even in its beta days when it was called Firebird (or was it Phoenix?), and kept going back to it after trying other browsers. But I knew 3.6 would really have to show me something to dislodge Chrome from the front line.

But I'm pleasantly surprised. I'm not sure what the developer did, but it's a whole lot quicker than Firefox used to be. It's not quite in the Chrome league, but this new version might be as fast as Opera.

From what I've noticed, Web pages don't seem to get lost in that nether world that's probably populated by everyone's stray socks.

Lifehacker recently ran some tests of some of the favorite browsers available, with several versions of Chrome, Firefox, and Opera, and Safari. Sorry, Internet Explorer wasn't in these tests, which takes away a lot of comic relief. That would have been like bringing a duck to a cockfight.

Here's the stuff according to Lifehacker, with my comments:

• Boot-up and warm loading; Winner: Opera - No surprises; Opera always was a fast loader.

• Tab Loading; Winner: Chrome Stable - I use version 4.0.249.30 for Linux, which is in beta but built from the stable version. And there's no dispute there; it's the fastest "name" browser I've seen in a while.

• JavaScript; Winner: Opera 10.5 Pre-Alpha.

• DOM/CSS; Winner: Chrome Developmental version.

• Memory use, no extensions; Winner: Firefox 3.6 - This is a surprise, and certainly worth my attention.

• Memory use with extensions; Winner: Firefox 3.6 - An even bigger surprise here. Firefox has always been fairly quick until I start loading in my extensions. Then my browsing experience was like watching paint dry. If this test holds up in real life, then Firefox just made up for a lot of lost ground in the browser battle.

• Overall winners, in order: Google Chrome Developmental, Google Chrome Stable, Firefox 3.6, Firefox 3.5.4: Opera 10.5 Pre-Alpha, Opera 10.01, Safari 4.0.4.

Will this new Firefox become my prime browser?

It's hard to say. I've always liked how you could add extensions to Firefox, but Chrome is starting to head in that modular direction too. And I like the independent tabs in Chrome; if one Web page gets stuck you only need to close that tab rather than shut down the whole browser. In Chrome I haven't run into the memory problems I used to encounter with Firefox. There's a lot to be said for both browsers.

Besides, it's still too early in my test flight for me to render a decision. I haven't broken Firefox yet. Or Chrome. Ask me then.

But if speed and memory use are your needs, it looks like this may finally be a fair fight.

###

Got my Chrome on -- finally!

After a whole bunch of testing, tweaking, and head-banging, Google Chrome is now working on my Linux box.

At issue was an nss file; I'm not real sure what it does, but it makes Chrome work. That's all I need to know.

I couldn't find it on any of my Vector Linux repositories, so I had to do some serious Web searching to dig it up. But it's there, on a web site called slackfind.net -- of course, it is now bookmarked in my system.

Here's the file:

Keep in mind, this is for a Slackware version of Linux, specifically Vector Linux, which is the one I use. It's in .tgz format, for me a breeze to install.

And Chrome is as fast as I knew it would be.

Firefox? What's Firefox?

###

Chrome becomes headache on Linux box

I'll admit it. I had my early misgivings about the Google Chrome browser when it was first coming out. Like, what's Google doing in the software business?

But after using Chrome a few times on Windows systems, it sort of grew on me. It's one fast browser, maybe even faster than Opera. It's less likely to blow up in memory like Firefox. I have a Portable Apps version that I use on borrowed Windows machines, though it doesn't seem to save my bookmarks.

On my Linux box, I'm always experimenting with browsers. I have Firefox, Seamonkey (which is built off the old Mozilla code), Dillo, Lynx, and Opera available to browse the Web, and I use them all. For the past few months Opera has been my go-to, and even that feels poky next to Chrome.

So I put myself on the Chrome mailing list, waiting for the Linux version to come out. A few weeks ago, the first version for MacIntosh and Linux was released, with all the warts.

Now, understand, this version is in beta. Which means it may or may not work. That's what happens when you go for such bleeding-edge software. You're volunteering your services as a crash-test dummy.

So far, only binaries of Chrome seem to be available in Linux; I haven't seen any source-code bundles just yet. I use Vector Linux, which runs with .tlz and .tgz binary packages, but I like to compile my programs from source. Best I was able to do was to download the .rpm binary (which Red Hat and Fedora use), and convert it over to .tgz. Here's what I did, from the root shell:

root:# cd /home/eric
root:# rpm2tgz google-chrome-beta_current_i386.rpm

From there, I was able to install it directly into my system. I was ready to go. I had my seatbelt buckled and my Tony Stewart racing gear on, 'cause this was going to be one fast browser.

A problem, though. I could only go so far; the sandbox (a security tool) wasn't configured right. My command shell told me what to do, so after a few days of deliberation I went ahead with the fix. Here's how, again from a root shell:

root:# su /opt/google/chrome
root:# chown root chrome-sandbox
root:# chmod 4755 chrome-sandbox

Then fired Chrome up from the command shell -- success, for a minute.

As it stands now, I can work Chrome all day, as long as I don't use it to go online. That's when it quits.

Seriously. Here's what I get in the command shell:

eric:$ google-chrome
[7241:7253:703254262:ERROR:/usr/local/google/home/chrome-eng/b/slave/chrome-official-linux/build/src/base/nss_init.cc(89)] Error initializing NSS with a persistent database (sql:/home/eric/.pki/nssdb): NSS error code -8174 Assertion failure: lock != NULL, at ../../../../pr/src/pthreads/ptsynch.c:205 Aborted

In non-technical language, that means it crapped out. Back to the drawing board.

Might need to download the next version, maybe attack one of the nightly builds. And if anyone has any ideas of their own, I'm willing to try them. But despite my early misgivings I see Chrome in my future, and I'm not talking about a chrome dome here.

I'm gonna keep trying, because I'm stubborn and enjoy fooling with software when it's in beta. Face it. I make a good crash test dummy.

###

(You tell me: How about the rest of y'all Linux users? Have you had any better luck than me? Use the comments section below.)