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.'"
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.
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
What I find so interesting about this post is that it's exactly why companies are nervous about using open source for mission critical projects. You're absolutely right - since people pay nothing for the software then they can make no demands of it. I've even posted bug reports on open source projects that start out saying something like "I know that I haven't paid anything for this so I have no right to complain, but..." So give me one good reason, after reading this post, that any IT manager would want to bet their future or the future of their company on open source? At least with proprietary software you have the right to demand that things get fixed, and if you don't get what you want then you can find an alternative.
If you don't want crime to pay, let the government run it.