| « Thumbnail the Vote | G-Toob » |
Popular theory goes today is "street" for Firefox 2.0. Though I'm sure there's some leeway in whether this actually comes to pass, I'm posting this anyway. I doubt there'll be any significant change in feature sets between "RC3" and the final version. My comments here will refer to the RC3 version, just to make sure all those sticklers for detail are satisfied.
I have made mention in a previous blog my preference for Firefox as my primary browser. It might then surprise you to know that I only recently sampled the release candidates for version 2.0. My first flirtation came with RC2, when everything was pretty much "baked". It's been a bug hunt ever since, presumably. That and "polish." Man, do developers love to talk about "polish" before something is released. It's hard to read a pre-release article, especially in the gaming industry, where the word polish isn't thrown around. It's like they're distributing the code on wing-tip loafers instead of CDs.
When I started looking at the feature improvements for 2.0, I wasn't really all that excited. Nothing really grabbed me as an improvement that would significantly impact my personal user experience. Don't get me wrong, I'm all for the update, I simply haven't found myself in drooling anticipation for it. I ended up installing the RC2 version at home in order to get a feel for it. Ironically, I do far less browsing at home than I do at the office, so it was a less "mission critical" environment in which to perform a test drive.
One of the reasons that keeps me weary of an office upgrade is that nagging fear all my precious extensions aren't going to function with the "new" 2.0 version. Again, as I mentioned before, I have heavily panderered my Firefox. Wow, there's that word again. Honestly, never thought I'd use it ever again. In any case, with so many wonderful toys I've come to rely on, I don't really care for the idea that I'll have to do without for some indeterminate amount of time until some unpaid developer gets off his butt and does an update. An unpaid developer whom I loved right up until he didn't fix his extension for the latest release. Fickle, I admit.
Mozilla needs some kind of preinstall extension compatibility checker. The current compatibility check happens after you install 2.0 (like all previous updates), informing you of your results in the compatibility lottery long after it's too late to turn back. I did pretty well at home, but I haven't added much to the home install. Granted, you can always reinstall an older version if you truly can't stand to live without some version of an extension, but I'd prefer to be given the choice up front, with all cards on the table, instead of regretting the decision after I made it.
"This is it?" or "The New Features"
Let's check the list, shall we?
Let's see... Improved Add-ons manager... okay, I guess, the last one worked fine for me. JavaScript 1.7... whatever, I don't use the previous versions. Extended search plugin format... okay, bottom of the barrel, do you feel me scraping...? Updates to the extension system... right... SVG text... "Now on a curve!" I don't recall ever seeing a website with SVG text, period... New Windows installer... well, that's useful... once...
I suppose I should reiterate I love Firefox, despite the tone of this blog. We only viciously criticize the ones we love. I'm just a little disappointed in the new feature set. It didn't grab me. It seems I could have simply gone on with 1.5 and still have everything that makes me love Firefox. In fact, if I wasn't able to "fix" the tab "improvements" I may have done just that. The Inline Spell-Check is pretty much the only "must have" on the list, for me at least.
What have we learned? I love ellipsis. And Firefox, too. Only... maybe they should have just called this Firefox 1.75 and I would have had appropriately scaled expectations. Instead, it's "2.0" and I'm just a little unimpressed.
Trackback URL (right click and copy shortcut/link location)
Comments are closed for this post.