Fuck Firefox 14

It had been a few weeks since I last used Firefox because it sucks so fucking hard. Instead, I've been using Safari. With my recent upgrade to Mountain Lion I checked out Safari 6 and wondered what Firefox 14 was like in comparison. I decided to approach it with an open mind and did the old launch-check-install-relaunch routine that I've done over a dozen times in the last year or so.

Firefox Sucks! Unlucky Thirteen Is Useless

I just started up Firefox and, once again, there was another whole-number version update waiting to interrupt my use and enjoyment of the world-wide web.

Didn't Firefox 12 come out about a month ago?

Once I applied the update and got running again, nothing was changed. Not a thing. Okay, well, a new tab homepage. But seriously? Showing me a few sites that I visit frequently? I know how to use browser bookmarks and history, thank you. But in addition to useless new “features,” Firefox 13 also screws stuff up.

The damn thing won't load new pages to about:blank now, even though I've tried to configure it to do so. The Firefox team also fucked with page scrolling, so that now instead of moving in discrete increments, they have some half-assed “smooth” scrolling that tears across screen refreshes on OS X.

These are just a few in a laundry list of many complaints about Firefox that I have compiled since Firefox developers think that wasting my time is some kind of design goal. Here's what doesn't work as of Firefox 13.

Another Day, Another Firefox Update

I am often away from my computer for weeks at a time, digging at archaeology sites, before I return to clean, sort, and catalog my finds. And every time I launch my browser of choice, I have to sit through yet another Firefox update.

No More, Namoroka: Firefox 3.6 Sucks

The Mozilla development team released Firefox 3.6, codenamed Namoroka, on 21 January 2010 after some anticipation; Firefox 3.5 was a step forward in features but two steps backward in performance. As a minor update, Namoroka was a chance to optimize the last release.

So, now that it's out, did it alleviate some of these problems? Well, let's find out by looking at what 3.6 offers over 3.5.

Firefox Has Too Many Developers

In its last several releases, everyone's favorite Open Source browser has become an unstable mess of add-ons, plugins, and other hacks that chew up memory like a fat kid with a chocolate-dipped corn dog. In fact, just last week, SecurityFocus released news of a devastating exploit in Firefox 3.5.5 that they blame squarely on its unstable architecture.

From its infancy Firefox has been the product of collaborative effort, unifying code from hackers worldwide. But thanks to the Hayes Law, we see that there is a "sweet spot" to such a development style, and that Firefox has long since left it behind. In the chart below, we can see that the number of Firefox developers has increased exponentially since 2002, and that number will more than double in 2010.

But it's time to be honest: either Firefox, as a modern web browser, will have killer performance on 64-bit, multicore Intel chips or it's not worth downloading and installing. And since, as we have seen in the recent past, that Firefox is actually getting slower with each release, Firefox is certainly a waste of time for anyone who takes their web browsing seriously.

Some Questions & Comments About Firefox 3.5

I have to say that Firefox is getting a lot worse lately. The user experience is in serious need of improvement and development is the pits. I installed the latest "big deal" Firefox update on June 30th. (For some reason they skipped a full four secondary updates, but whatever.) Upon restarting, which took several minutes, I began using Firefox 3.5.