Slashdot Mirror
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.
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.
Nice troll. Looking at bonsai, of the eleven distinct patches checked in on trunk during the last day, two originated with people without CVS access (aka, third parties).
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!
Nice troll. I'm personally as unqualified to comment on Mozilla source code quality as you are, and I'll definitely not claim everything is perfect (there's been too much abstraction in the past - hence lots of deCOMtamination work now), but every patch that goes into the Mozilla tree gets reviewed critically at least once - most often twice - for code quality, and to point to an example metric that doesn't say much of anything (but neither did you, so that should be familiar ground) - the coverity scan found fewer defects in the Firefox code (0.355) than the average baseline for open source projects (0.434).
In my experience, any large software system is very, very difficult to get your hands around if you didn't create it yourself. If the source code looks bad to you, the odds are one reason is that you didn't write it yourself and so you don't understand the techniques used.
For example, I like dumping things in one directory instead of having anal directory structures that take time to navigate. Others prefer having things all in their place. Neither style is particularly right or wrong. My style probably doesn't scale well to projects done by more than one developer. Their style makes it more time-consuming to get to know the code.
But in any event, I can't pass judgement on this source code, since I can't find it. I looked through the source he linked to and I couldn't find a single C file. In fact, I couldn't find anything that seemed to deal with the browser's core funtionality, such as rendering pages or putting up menus or toolbars.
I didn't find anything about what I saw in the JavaScript that seemed too bad. It seemed reasonably straightforward to understand, but of course the numerous options made it more complex than I'd like. That's inevitable in this kind of project, so it's not really a fault.
Is there any kind of guide to the source code, that would explain where the heart of it is?
D
If you look in the layout, view, xpcom and xulrunner directories, you'll find a lot of the core code. The browser directory is for the JavaScript and XUL files which make up the interface and product-specific parts of Firefox. :-)