Firefox Losing Its Way?
An anonymous reader writes "NeoSmart Technologies has a recap on Firefox 2.0 and its shortcomings. Aside from the technical aspects, the article raises some good questions about the Firefox 'community,' it's future, and what it's goals are at the end of the day. Their conclusion? Firefox 1.5 was a much better open-source project/community model than 2.0 ever will be, and that 'It seems Firefox has lost its way somewhere along the passage to fame.'"
Here, allow me to post a short summary of the article to save you some time:
I think the new theme and start page is ugly, and there are a few weird bugs that haven't been fixed yet, and they haven't implemented a feature I want in a way that I want it. Therefore, it sucks.- Don't like the default theme that comes with Firefox? Go get another that you like better. Don't like the first run page? Who cares? You only see it one time!
Last time I checked, Firefox was still open source software. If they're not fixing bugs fast enough for your liking, by all means, download the source and fix them yourself. That's not meant as a smart-ass excuse for not fixing a bug, but the article's author says:
No, the best way to help is to go through the source and fix the bug! Don't talk about it, do it, and solve everyone's problem with having it!
- The feature the author wants implemented better is an RSS feed reader. I have some news for you: it's supposed to be a basic implementation that gives you the bare essentials. If you want one with bells and whistles, go get an extension that suits your needs better. This isn't a sign that Firefox has lost its way, its a sign that it's principles haven't changed much at all.
- Last, but not least, I'm not sure what the author of this article is proposing we all do. Switch to IE7 or Opera? Yeah, that will help the open source community.
Point is, while Firefox 2.0 was never pitched as the last version of Firefox that we'll ever need as a result of its attaining perfection. Personally, I wish that they would fix the bug that causes only the first page of web pages with absolutely positioned elements to be printed. I wish I had the skill to fix it myself; I would if I could. But I'm sure they're working on it, it doesn't change the fact that Firefox 2.0 is, in my humble opinion, the best damn browser out there right now, and the last thing I'm going to do is undercut the extraordinary efforts of its developers and contributors by posting a whiny blog entry about how because there are still a few things I don't like about it, it's somehow "lost its way somewhere."
Sheez. Talk about ungrateful.
The complaints raised here are trivial features. Not the performance or stability problems I had with 1.5 but instead things like RSS & aesthetics which to me aren't too important when it comes to a browser. I'm sure for some other people RSS or theme might make a world of difference but I'm not that person and I don't wager there are many people like that.
The concern that it makes itself the default browser is valid but using the word 'hijacking' is a bit strong. Honestly, I didn't even notice this but I was going from 1.5 to 2.0 on most of my computers so that might explain why this was a non-issue for me. Perhaps they assumed if you were going to 2.0, you were coming from 1.5? Either, I agree with this qualm though I find it to be the most serious offense listed in the article.
So you may ask if Firefox has lost its way but I counter that there have merely been a few miss-steps along the way. I'm keeping an eye on IE 7 & so far it hasn't lured me away from Firefox 2.0 so I guess that's a good sign as I consider my standards to be pretty high.
My work here is dung.
Some flamebait article from a blog no one's ever heard of, probably submitted by the blogger, passes for news? The major complaint is that the blogger doesn't like the default theme and start page! Pick others!
I must say, I'm having a feeling akin to the one I had when Netscape went over the 3.0 version number: things feel somewhat slower and buggier, with more bling that I don't really need. One of the most irritating "features" I keep hitting is whenever I open something with an extension, be it a pdf with Acrobat reader, a flash animation, a video with mplayer or a java applet: about 1 out of 10 times, the cpu goes to 100% and FF is dead in the water. I know the usual answer, which is that it's not FF's fault but the extensions', but it happens with all the extensions the same and it didn't happen so much, if at all, with earlier versions.
I don't know, perhaps there's a pattern with very large, popular open-source projects: the more popular they grow, the more developers tend to focus on adding features instead of correcting bugs...
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
Last time I checked, Firefox was still open source software. If they're not fixing bugs fast enough for your liking, by all means, download the source and fix them yourself.
We hear that reasoning a lot from open source advocates. But when it comes to Firefox and Mozilla in general, it just isn't a case. Their code is a mess, regardless of whether it's C++ code, or whether it's JavaScript code. Look for yourself: http://lxr.mozilla.org/seamonkey/source/.
I don't follow the project closely enough to know why the quality of their code is so low. It may be due to inexperienced or untalented developers. It may be due to rushed development. It may be due to a lack of refactoring. But the end result is that it's very difficult for most programmers to come up to speed with the code even just to fix a small bug, let alone implement entirely new functionality.
The poor quality of the Firefox and Gecko codebases could be indicative of why we've seen to many quality and security problems with Firefox as of late. Firefox does suffer from pretty horrendous memory leaks, even when not using any non-default extensions. The number of serious 0-day security glitches has increased dramatically, as anyone on any notable security bulletin mailing list can attest to.
Quality software builds upon a quality codebase. And until the Mozilla project can obtain that quality codebase, we will continue to see them produce poor-performing applications that suffer from frequent security flaws.
Hopelessly misleading blurb. Here's the edited-for-truth version. The italics indicate the original text:
An anonymous reader A NeoSmart staffer writes:
"NeoSmart Technologies has a recap an attack article on Firefox 2.0 and it's shortcomings we say some things that we thought would get some traffic.
Aside from the technical aspects the things we don't understand but will criticize anyway, the article raises some good questions ridiculous mischaracterizations about the Firefox "community," [Editor's Note: Why the "sarcasm quotes"? Are you saying it isn't a community?] it's future, and what it's goals are at the end of the day we inserted a meaningless sports metaphor here.
Their conclusion sophomoric trolling you can safely ignore? Who cares!
There. Now what was so hard about that, Slashdot eds? Oh, and while you're at it, "its" was incorrectly spelled three times out of three.
To change it back to the old setting (x on the right of the tabs bar) go to about:config (in your address bar) and change the value of browser.tabs.closeButtons to 3. .tabMinWidth settings
For the issue of tab size and overflow managing, you can edit the browser.tabs.tabClipWidth and
There hasn't been a *single* patch to fix flaws in FF2. Not. A. Single. One.
There haven't exactly been a lot vulnerabilities found either. The only one I know of found in Firefox 2 since its release is marked as less critical by Secunia. I'm sure that if you can find critical errors in Firefox, they will be fixed quickly.
I'll probably be modded down for this...
The article is slashdotted, but I think the main problem here is that Firefox has pretty much reached perfection. Firefox was intended to be a stripped down version of the Mozilla suite with just the browser. Now there seems to be a bigger push for built-in gee-whiz features.
I guess the community has just gotten board and went home. Specifically I have noticed:
* Mozillazine almost never seems to have any news anymore.
* The SpreadFirefox image galleries have been screwed up for ages now and people keep posting crap that never never gets cleaned up.
* The Mozilla store seems to have been having problems lately (it would hang and timeout when placing an order) and there Firefox CDs are still at old 1.5.0.4 version. (A physical factory pressed CD you can hold in your hand can go a long way convincing a PHB that this is real software!)
* And where is Thunderbird 2.0 anyway?
Come on folks! We still have an evil browser from Microsoft to crush!
I noticed our library hasn't upgraded to Firefox 2.0 at Umass Boston. I thought it was interesting and asked the reference librarian why. She said the IT people didn't think it was significant enough to bother upgrading and people also didn't like the way it looked. Interesting, I thought to myself.
n t=c_linuxseafox.php and add an extension to enhance the UI like MonkeyMenu http://markbokil.org/index.php?section=tech&conten t=c_linuxmonkeymenu.php and you have a better browser than Firefox 2.0
This is one of the reasons I switched back to the Mozilla Seamonkey Suite. It uses less memory when you run Mail and the Browser together than Firefox and Thunderbird. I like the more community orientation of the development also. All you need to do is throw on a good theme like SeaFox http://markbokil.org/index.php?section=tech&conte
Have you ever tried out Opera?
Let's look at the facts for Opera:
CHECK 1. Stops popups automatically
CHECK 2. constant updates and improvements every x months
CHECK 3. better security than IE
CHECK 4. the option to easily clear cookies, history, temp files, etc on close
5. Is faster, more standards compliant, and more stable than FF or IE.
6. Includes nearly everything needed for the average user in the core build so no downloading and installing of extensions is needed.
IMHO The Opera browser is the best browser available and I wish more people knew it existed because the majority of people I know think the only choices available are IE and FF, many of them have never even heard of Opera.
Hey, there is only one Return and it's not of the King, it's of the Jedi.
According to the site Bill's Big List of Firefox 2.0 Extensions, in only 40 days, the number of Firefox 2.0 compatible extensions has jumped from 677 extensions to 1449 extensions.
If this is in any way a reflection of the Firefox development community, it looks like the community is thriving pretty well.
Brendan Eich addresses most of these issues http://weblogs.mozillazine.org/roadmap/archives/20 06/10/mozilla_2.html
You should know that they do intend to compete in the mobile web space. That means they have no choice but to clean everything up without the excuse "oh memory is so cheap anyway.."
Firefox Power http://firefoxpower.blogspot.com/
So they are your slave? It is not their job. Most open source developers are volunteers. Maybe if you were paying the develper to write code for the project, you'd have an arguement, but it sounds to me like you are not. You just want them to be your slave because they publish a useful program for free.
I suppose if you were homeless and went to a soup kitchen, you would demand they hand feed you and wipe your ass after you use their bathroom too.
The Mozilla codebase is a mess. However, it is getting better. Did you look at it at all when Netscape first released the source? It was absolutely terrible. The Mozilla guys have done a good job at cleaning it over the years, but it's still a mess. They really should have just started from scratch and used the old codebase as a reference.
Hold on a minute! They did do that. They rewrote the whole damn thing starting on October 1998, a mere seven months after the initial release of the source code. One year later, mozilla shipped nothing, and JWZ resigned citing lack of progress. In 2000 -- two years after the rewrite started -- mozilla released the new layout engine, Gecko. Jaws all around had to be picked up off the floor. It was a horribly buggy. (The most obvious bug to me was the fact that scrolling to the bottom of a page, then back up, then back down a second time, caused TWO copies of the page to appear in the window. Repeat N times, and you got N copies. I discovered that bug within the first five minutes of use.) FOUR years after the rewrite, Mozilla released version 1.0. Now four years after 1.0, 8 years after the rewrite that is widely considered the biggest blunder of mozilla's history. A blunder that is made all the worse since it's outcome was immediately forseeable.
Now you're not seriously proposing the repeat their old mistakes are you?