Can Firefox Be Saved? Two Proposals

The lackluster performance of Mozilla Firefox 4 suggests the browser may have lost its way.
(Page 1 of 2)

After spending months on end watching Mozilla Firefox 4 go through eleven-and-some-odd betas, I’m less than impressed with what I’ve waited for all this time. The first time I launched a fresh install of Firefox 4 and navigated to the homepage of the New York Times, it hung for almost a minute on end – and then every ad block on the page burped with a “Flash plugin has crashed” message.

This is progress?

I know I’m not alone in this, either – many folks I know who had been suffering through successive Firefox betas were disillusioned with the quality of the release product. They’re either rolling back to Firefox 3.6 or ditching it entirely.

Me, I’d ditched Firefox for Chrome back around revision 3.4 or so. Maybe earlier.

Like too many other software projects before it, Firefox is starting to suffer from the very things it was originally developed to avoid. It’s falling victim to the exact stagnation that plagued Netscape before it. The competition – not just Chrome, but even lowly old Internet Explorer, now in its ninth version – is outpacing it in greater strides.

In short, there’s now less reason than ever to be a Firefox user.

That’s a shame, because Firefox isn’t a bad piece of software. It’s just increasingly suffering from third-wheel syndrome, which it hasn’t found an effective way to lick yet.

Google Chrome, by contrast, has come from behind to eclipse Firefox in a whole slew of ways. On the same hardware, it launches and browsers more quickly and with less inexplicable lag than Firefox. Flash doesn’t hiccup or stall, and hasn’t bombed on me at all for a few versions running now.

Google Chrome’s add-on architecture is a lot easier to work with and requires a prospective software author to jump through far less hoops. Its page debugging and inspection tools are remarkable; I rely on them constantly. And while running each tab in its own process is more memory-hungry than Firefox, at least I know that memory’s being put to good use: if one tab stalls, the rest don’t.

But wait: I’m not just here to bury Firefox and praise Chrome. If anything, I’d like to see Firefox rise all the more to the challenge and give Chrome a run for its money. I just don’t see that happening with Firefox’s current development cycle.

Mozilla is talking about ramping up their releases to match Chrome’s, but I’m not sure that’s enough. What might be needed are solutions that are either far more precise than what Mozilla is dreaming up, or way more radical than they will aim for.

Make a break from the past

When Firefox came along, it was a welcome relief from the tired and stagnant Netscape. Here was a browser that threw out everything that didn’t need to be there, gave the user a snappy browsing experience, and offered a far more appealing alternative to Internet Explorer.

The whole reason all this was possible was because Firefox was a radical break from the past – an experimental branch of Mozilla that overtook the parent. Firefox left behind more baggage than it kept, and the end result was a massive success story.

Maybe it’s time to do that again. Let’s have a spinoff of Firefox that is to that browser what Firefox itself was to Netscape. Not just another iteration in Firefox’s development, but a clean slate – a way to get back to the basics that the original iterations of Firefox prided itself on and were valued for in the first place.

This is something that might only be possible by a third party, though. Only a third party might have the distance required to take Firefox, strip out everything that no longer needs to be there, and start over again with as little of Mozilla’s existing baggage as possible. The hard part isn’t getting the code (Firefox is open source, after all). The hard part would be assembling a development team willing to commit to a project of that scope.

Much as I like to believe in the romance of open source, a project like this isn’t something you can do on nights and weekends – not in a competitive fashion, that is. That might well prove to be a bigger obstacle than writing the code: finding and supporting people who can do it and get it out the door in a timely way.

Ship smarter, not more often

Maybe kicking off a whole new branch of Firefox is too radical a suggestion for most people. Barring that, I took a look at the Firefox roadmap for 2011 to see what Mozilla itself has in mind.

Page 1 of 2

1 2
Next Page

Tags: open source, Internet Explorer, Chrome browser, Mozilla Firefox, Firefox 4

0 Comments (click to add your comment)
Comment and Contribute


(Maximum characters: 1200). You have characters left.