News flash: I still think all browsers suck, to varying degrees. Some of the following is my fault, as you’ll discover as you read, but I think a significant chunk of the reason it happened is probably just the overly complex edifice it has become, pursuing competitiveness with IE.
Months ago, when I should have upgraded my FreeBSD 6.2 system to 7.something, I didn’t. The SigO was planning to get a new laptop, and her old laptop is exactly the same model as my laptop. I figured I’d just wait on upgrading the FreeBSD version, and after she got her new laptop and migrated everything to it, I’d just install FreeBSD from scratch on her old laptop, then migrate my own stuff onto that. There are a number of minor reasons to do things that way, but nothing really major.
Well . . . there were some issues with getting her new laptop set up, at first. We finally got those ironed out sufficiently, and she was playing World of Warcraft on Debian again. More time passed as she hesitated to completely commit herself to the new laptop, waiting to see if problems would arise with the way the system was installed, so that it wouldn’t be too difficult to reinstall stuff if there was a problem — which meant she kept the old laptop as her primary. In the meantime, my own laptop waited.
I don’t blame her at all for the problems I’m currently having with Firefox, of course. It’s not her fault in any way. If I had similar problems getting a new laptop set up to my liking, I’m sure I would have done much the same that she did. I might have moved a little faster, but I’m also a bit more experienced and comfortable dealing with technical issues with Unix-like systems.
Disclaimer aside, recently a Real Problem has arisen.
Firefox 3.0.x has had some issues keeping up with my browsing habits, of late. Apparently, it doesn’t like it when I keep 100+ tabs open all the time. When the number of tabs starts getting higher, Firefox 3.0.x starts getting crashy. Luckily, it’s quite good at recovering all those tabs the next time I start it after a crash, so nothing is lost other than time.
I heard good things about the speed of Firefox 3.5.x, and hoped some of the minor issues with Firefox 3.0.x might have been fixed, so I decided it was time to upgrade. I backed up my
.mozilla directory and went about the process of moving to a newer Firefox version. Then, when I tried to start it up, it failed.
There’s a note in the
/usr/ports/UPDATING file on FreeBSD saying that you have to load the
sem module to make sure that FreeBSD won’t crash. I tried to make sure that would load, but it turned out that (for some incomprehensible reason) it wasn’t on my system. It was in the source tree I had on the computer, though, so I compiled it and then made sure it loaded. Of course, Firefox still crashes.
I found some references to the fact that a few people (particularly on FreeBSD 6.x) are having some problems with HTML 5 content crashing the browser, so I used the FreeBSD ports system to install the NoScript extension. Suddenly the browser started, and ran stably! Excellent! Now, I just had to deal with the fact that all my tabs from the last pre-upgrade session were gone. Luckily, I had backed up everything in the
.mozilla directory, which should include those tabs. I haven’t bothered checking on that, though — I’ve had other things to do for the last couple days. I guess, if the tab session isn’t saved, I’ll just deal with it. I’ll probably need some of those tabs from the previous session today, so I’ll find out for sure later today, I think.
Okay, so now I have Firefox 3.5.x on the system, and it doesn’t crash when it’s running with NoScript.
Oh, yeah, and I tried re-enabling to Awful Bar (the people at Mozilla call it the Awesome Bar) again. I figured there’s no way the new operation of the address bar in Firefox as of 3.x was as bad as I remembered, and I probably only needed to get used to it to find it useful. After playing with it for twenty minutes, though, I’ve come to the conclusion that it’s even worse than I remembered. It literally couldn’t find anything I wanted it to for URL completion. Nothing. Terms that used to come up automatically, at the top of the list because they’re the terms I used most often, simply failed to come up at all, no matter how many times I tried to “train” the Awful Bar to find those terms for URL completion instead of whatever irrelevant crap it was finding instead.
Of course, I can’t turn off the Awful Bar completely, unless I just want to do without any kind of address bar. It’s baked into the browser now. What I actually do is use the “oldbar” extension. It’s not perfect, but it’s definitely a lot better than the Awful Bar. It takes more training to come up with useful results than Firefox 2’s address bar, but at least it can be made to come up with useful results. I turned on the oldbar extension again, and figured that’d solve everything.
Actually, I discovered that just turning on the Awful Bar again (or, more accurately, disabling the oldbar extension) had wiped out all the “training” I had put into the oldbar-enabled Firefox 3. I had to start over! It still isn’t quite up to snuff, though I’ve been working pretty diligently; it still tends to give me URL completion options in the wrong order almost as often as in the preferred order of likelihood that I’ll want a given result. It’s clearly on its way to being back to the state it was in before I decided to give the Awful Bar another chance.
Fool me once, shame on you. Fool me twice, shame on me.
Firefox sucks. The only positive things I can say about it are “At least it’s better than Opera,” where I can slot in the names of almost all other browsers in the world. Problems aren’t particular to Firefox and Opera: all Web browsers suck to varying degrees. About the only Web browser I’ve used that I both don’t find more loathesome than Firefox and can use to do all the things I tend to need to do on the Web from day to day (including research for work-related purposes) is Chrome, but the Chromium browser (that’s the open source project behind Chrome) hasn’t been ported to FreeBSD yet (or even finished getting ported to Linux), so that’s not really an option for my primary browser choice.
There is, supposedly, someone working on ironing out the crashing problems with Firefox 3.5.x on FreeBSD (which are apparently pthread related), but I don’t know what progress is being made on that front. I hope it’s progressing to a point of “solved” very soon.