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.'"

494 comments

  1. No, it's not "losing its way" by KingSkippus · · Score: 5, Insightful

    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:

    If I have the time, I'll go through the source, but I think the best way to help is to bring it to attention.

    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.

    1. Re:No, it's not "losing its way" by Marcion · · Score: 2, Informative

      The article, which I read here, doesn't really say what "its way" is.

      I have been shifting between Firefox and Epiphany, as it looks rather nicer on my GNOME system.

    2. Re:No, it's not "losing its way" by hackershandbook · · Score: 1

      I love firefox and have yet to download and install 2.0 because I am waiting for my extensions to catch up. After this debate - its time to go and download firefox 2.0 and extensions be damned .. it goes on a trial server tonight ...

    3. Re:No, it's not "losing its way" by Tankko · · Score: 1, Insightful

      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:

      You know, not everyone on the planet is a programmer. I know you find this hard to believe, but it is true. Your comment is arrogant and typical of a lot of programmers that don't feel someone has worth unless they can code.

    4. Re:No, it's not "losing its way" by hahafaha · · Score: 2, Informative
      Your comment is arrogant and typical of a lot of programmers that don't feel someone has worth unless they can code.

      How? All the comment was saying was that if you do not like how something works, and the developers gave you every right and convenience of fixing it, then the only thing you have a right to do is to fix it yourself. If you do not know how, then learn. Many programmers out there are self-taught (myself included). Worst case, hire a programmer to do it for you.

      No one is forcing you to use Firefox. But if really want something to be fixed, and the source is provided for you, then go and fix it yourself

    5. Re:No, it's not "losing its way" by KingSkippus · · Score: 4, Insightful
      Your comment is arrogant and typical of a lot of programmers that don't feel someone has worth unless they can code.

      No, it's not. As I posted above, the reason I brought it up is because the author of the article implied that he has the skill to fix at least one of the bugs that he's complaining about. While I agree that he's under no obligation to do so if he doesn't want to, I also think it's extremely bad form to sit around complaining that no one else will.

    6. Re:No, it's not "losing its way" by caitriona81 · · Score: 5, Insightful
      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:
      This assumes that the people affected by bugs are actually capable of fixing them, and is an example of one of the worst qualities of open source software - elitism. Not to mention, the Mozilla development processes are so overburdened with red tape that an outside developer would have a very difficult time contributing effectively - while I understand why the review/supereview process is needed, it serializes development to the point where even when developers want to help, and contribute code for features that are highly desired by end users, by the time anyone gets to look at it, development has progressed to the point where any patches submitted are useless. For an example of this, look at the various bugs for roaming profile support - its been years since it was removed from the old netscape product, there was a large userbase for that feature, and major outcry to have it back - but we still don't have it, even though numerous patches have been submitted - if it's not a priority for the developers on the inside of the project, it probably doesn't get done even if someone is willing to provide code. That said, despite the issues, I've still found Firefox to be the best browser available to me - I just hope the project wakes up and listens to the community before its too late.
    7. Re:No, it's not "losing its way" by Greventls · · Score: 0

      Firefox crashed constantly on my laptop until I rebuilt it. So what? It is one anecdote.

    8. Re:No, it's not "losing its way" by Danga · · Score: 3, Insightful

      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.

      I don't know exactly what the author was proposing people do since I cannot get the page to load now but as much as I think open source is great I will be damned before I use an open source alternative that is inferior just to "help the open source community.". I will use whatever software I feel works the best for me and if that means I do not have access to the source so be it.

      Personally I have used Opera for about the last 5 years and the reason I chose it then was because IE was a POS and Mozilla was slower and neither IE nor Moz supported TABBED BROWSING. Now that both IE and FF support tabbed browsing I have given both a shot and while I will not be using IE for obvious reasons (although it now seems to perform faster than FF) I still won't switch to FF for the simple reason that I have gotten used to Opera and it still is a faster and more stable browser both in my experience and from the comparisons that other people have posted online. The thing I like the best about Opera compared to FF is that if I setup a new computer I just install the latest build of Opera and it includes all the bells and whistles I need where FF requires some extensions to be downloaded and installed to get to the same level. This is just a convenience factor since I am somewhat lazy but I still think it is relevant.

      Even some of the diehard FF users I know are considering switching to another browser because they seem to feel FF has started to become bloated and FF's performance is suffering. It is one thing to add a lot of features in the core build but not suffer performance wise like Opera has done but quite another to start adding them and have the user experience suffer. I know the OS zealots will not budge and switch over to Opera but for many FF users I know if it does not cost them any money to switch to a better performing browser then they will in a heartbeat. The main reason many of the FF users I know who are complaining about its performance have not even tried another browser is because they think the only alternative is IE, Opera is just not well known to the masses. It is going to be interesting to see what happens in the next year since the Wii includes Opera and hopefully will get some more exposure out there.

      --
      Hey, there is only one Return and it's not of the King, it's of the Jedi.
    9. Re:No, it's not "losing its way" by shmlco · · Score: 1

      First you say, "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."

      But then, "I wish I had the skill to fix it myself; I would if I could."

      I like that. In one post you state that no one should criticize or complain about it, they should just fix the problems, and at the same time you acknowledge that not everyone has the skill, time, or knowledge needed to do so.

      I guess they should just huddle silently in a corner then, thankful for their cold bowl of porridge?

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    10. Re:No, it's not "losing its way" by Computer+Guru · · Score: 0

      But the whole point of this is that 1.5 from a community and Open Source point of view was *better* than 2.0. Not that Firefox in general sucks, but that in between 1.5 and 2.0 something went wrong?

    11. Re:No, it's not "losing its way" by westlake · · Score: 3, Insightful
      Don't like the default theme that comes with Firefox? Go get another.

      The default theme is the user's introduction to the browser. It should have the look and feel of his native GUI.

      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!

      Advice useful only to a programmer and likely only to a programmer on the Firefox team.

      I have some news for you: it's supposed to be a basic [RSS] implementation that gives you the bare essentials. If you want one with bells and whistles, go get an extension that suits your needs better.

      IE7 has raised the bar a little higher than this.

    12. Re:No, it's not "losing its way" by prandal · · Score: 1

      That printing bug is a bummer. It's Bug 154892.

    13. Re:No, it's not "losing its way" by JWW · · Score: 1

      The default theme is the user's introduction to the browser. It should have the look and feel of his native GUI.

      OK, which platform's native GUI should they use? A native windows GUI look would look like shit on OS X.

    14. Re:No, it's not "losing its way" by chawly · · Score: 1

      I'm with you, friend.

      --
      How many beans make five, anyhow ? ... Charles Walmsley
    15. Re:No, it's not "losing its way" by Gilmoure · · Score: 1

      You mean things don't get fixed faster by someone pointing and going "that sucks!"? Weird. I thought that's how Western Civilization has progressed. Next thing you're going to tell me is that it's all due to people going out and 'doing stuff'.

      --
      I drank what? -- Socrates
    16. Re:No, it's not "losing its way" by mccoma · · Score: 1

      I would imagine he / she assumed that if I am running on Windows XP, then give me the Windows XP theme. If I am running on OS X, give me an OS X theme.

    17. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0

      So what you're telling me is that I should know how to program if I want something fixed, rather than depend on the developers of the software to fix it?

      I should step away from all the expertise I have in my own field of study to cater to some one whose job is to do what I'm learning, just because it's open-source and they don't want to deal with it?

      This is the biggest complaint I have with open-source software.

    18. Re:No, it's not "losing its way" by Blakey+Rat · · Score: 1

      Oookkkk... assuming this is actually true (mine works fine), what the hell relevance does this have to the topic? We're talking about FIREFOX losing its way, not IE7.

    19. Re:No, it's not "losing its way" by Monkelectric · · Score: 3, Informative

      I disagree heartily. There has been a bug on OSX for *two years* which makes firefox almost unusable.

      --

      Religion is a gateway psychosis. -- Dave Foley

    20. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0

      So you are saying that if I can't fix Firefox bugs I'm not worthy of using it? Maybe that should be added to the license agreement.

    21. Re:No, it's not "losing its way" by Blakey+Rat · · Score: 1

      OK, which platform's native GUI should they use? A native windows GUI look would look like shit on OS X.

      Are you seriously suggesting to us that Firefox *does not know* what platform it's being installed on? Seriously?

      OF COURSE Firefox knows what platform it's being installed on-- THEY COME IN DIFFERENT DOWNLOADS! Your post has to be about the dumbest thing I've ever read. It's like you're trying to make "make it look like the host OS" into some horrible technical process that has to happen when each OS already has its own installer.

      And, as a Mac OS X user, I can safely say I'd much prefer a Windows Vista-looking theme to Firefox than the crummy one it actually comes with. Vista-themed apps aren't all that out-of-place in OS X, except possibly for the colors. The Firefox 2 theme just looks like some weird alien application.

    22. Re:No, it's not "losing its way" by hal9000(jr) · · Score: 3, Interesting

      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:

      This is such an elitist position and really hurts both opensource in general and Firefox specifically. I am going to go out on a limb here and say that a large marjority of Firefox users, myself included, don't have either the chops nor the time to gain the chops to fix bugs. Also, even if I had the chops to fix bugs, I don't have the time to get familiar with the source tree to be effective. It's not like debuging is a 5 minute deal.

      I updated to FF 2.0 and downgraded to 1.5 wihtin a few days because 2.0 kept freezing and crashing and to be honest, I didn't seem any new features that made upgrading compelling.

      Now I think FF is a GREAT browser, I use it all the time and only revert to IE when I have to. And I have themed it and added extensions. I reccomend it to friends and spread the word. But, yeah, I have to agree, 2.0 was less than I had hoped for.

      However, I also want to sincerly thank for Mozilla Foundation and any volunteers working on the Mozilla projects for all their effort because people like me can't build this stuff.

    23. Re:No, it's not "losing its way" by Blakey+Rat · · Score: 1

      Except for the people who KNOW how to fix it can do it in a matter of hours (probably, depending on the bug), but the people who have never worked with programming before will take literally months to do it. It's not a very efficient use of people's time if you respond to every bug with "fix it yourself." In addition, it's rude to burden somebody with months of work to improve a project that you (supposedly) support and want to see succeed.

    24. Re:No, it's not "losing its way" by cofaboy · · Score: 1

      Welcome to Slashdot
      Where the readers never RTFA and they've stopped reading the bloody comments properly as well.

      --
      In the end, It's all bovine dung you know
    25. Re:No, it's not "losing its way" by caitriona81 · · Score: 1

      Apparently, I chose a bad example - the roaming functionality did make it into seamonkey, but not into Firefox or Thunderbird. I stand partially corrected.

    26. Re:No, it's not "losing its way" by hahafaha · · Score: 1

      Right, but the writer of the article implied that these are very important bugs, since they are causing Firefox to lose its way. Since they are not fixed, we can assume that the Firefox development team does not agree. However, they are providing the source to fix it. Therefore, he can either...

      1. Ignore it
      2. Learn how to fix it himself
      3. Hire someone else to fix it

      None of these are ridiculous, BTW. If it is that important to him, learning how to fix it is not out of the question. If he does not have the time, he can hire someone to do it for him.

    27. Re:No, it's not "losing its way" by JebusIsLord · · Score: 1

      Yes, offtopic, but yes; mine crashes quite a bit too. Not several times an hour, but once every few days and a lot more than IE6 did.

      --
      Jeremy
    28. Re:No, it's not "losing its way" by ralphdaugherty · · Score: 1

      You know, not everyone on the planet is a programmer. I know you find this hard to believe, but it is true. Your comment is arrogant and typical of a lot of programmers that don't feel someone has worth unless they can code.

            It's valid when the only worth is criticism.

        rd

    29. Re:No, it's not "losing its way" by fatphil · · Score: 1

      Which bit of 'native' do you not understand?

      --
      Also FatPhil on SoylentNews, id 863
    30. Re:No, it's not "losing its way" by aevan · · Score: 1

      You left out one, the choice of 'older people' and people who just want a browser for a browser, not a pet project inspiring a few years learning coding...

      4- switch to another browser that has the feature they want.

      If my mother doesn't find the feature she wants in an app, she just goes to make some tea, then find an app that offers it.

      Not saying your choices aren't valid, merely that people are prone to bandwagon jumping just as oft as to brand loyalty. Firefox can't cater everything to everyone, but the knee-jerk reaction of some of its fans of 'fix it yourself if you have an issue, instead of complain' just won't help Firefox with market share.

      Like Linux, sometimes I think half the stigma regarding it isn't the product, but the users.

    31. Re:No, it's not "losing its way" by Fnkmaster · · Score: 1

      Even some of the diehard FF users I know are considering switching to another browser because they seem to feel FF has started to become bloated and FF's performance is suffering.

      This strikes me as so factually inaccurate I can't believe it. FF 2.0 may be more featureful, but it's far faster than FF 1.5 on every piece of hardware I've tried it on. And it has fewer memory leak issues.

      You can argue about FF getting too much feature-bloat if you want, but unless you have some specific benchmarks to prove your point about FF getting slower, that claim strikes me as terribly wrong-headed.

    32. Re:No, it's not "losing its way" by FyRE666 · · Score: 1

      Funnily enough, the guy missed out the worst bug in Firefox (for anyone using a CMS anyway), which is that it auto-pre-fills any field in a domain named "password" with a single stored password. That might be ok for an end user, but when a CMS uses this field to say edit a user account, Firefox prefills that too, and if you don't realize, you've just set an admin password for the user (user can then request their password, and see yours, unless you generate random passwords on the fly). This recently caused me a headache as a client said every time she edited a user they could no longer login! The only "fix" is to globally disable auto-fill. There's no option to ignore specific sites... which would at least be a start...

    33. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0
      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!


      Which will almost guarantee that you will experience bogus bugs in future versions when you fail to remove your old profile, themes and extensions prior to update.

      Don't like the default theme? Get another browser. Installing a custom theme and expecting it's author to keep pace (or even continue releasing at all) with future versions is just plain silly. Themes and mods as applied to a broad range a of software are fatally flawed as a model and guaranteed to cause problems.

      Firefox's main problem? Dependence on javascript. Javascript is totally asinine as a concept, period.

    34. Re:No, it's not "losing its way" by hahafaha · · Score: 1

      Your argument is a good one, but it is only valid in a closed-source product. Then, it is the duty of the owner to listen to the demands of the users and change the program accordingly. In an open source product, however, it belongs to the community of people who own it and use it. Therefore, it is just as much your mother's duty to fix it as mine. Of course, there are different ways to fix it. She can, for example, donate to the Mozilla foundation so that the people who actually spend their day working on it, fix it sooner.

      It is, of course, her right to leave Firefox for another browser. However, the OP is doing nothing to help. He is merely pointing out problems, not solutions.

    35. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0

      I think the point is, both Firefox and IE have seen better releases than their current versions.

      IE7 is a true piece of... work. Try opening a zero-byte HTML file on your local drive, and you get an "unsafe content" warning. That breaks a lot of apps that use HTML files for help/docs.

    36. Re:No, it's not "losing its way" by yuriismaster · · Score: 1

      While I agree with you that this is a horrible bug that needs to be fixed ASAP, your statement that "There's no option to ignore specific sites" is horribly wrong.

      When you first enter a password for a site, a dialog comes up asking "Would you like to remember the password?" and options "Remember Password", "Never for this Site", and "Not Now". I think that middle option is the one you're looking for :)

    37. Re:No, it's not "losing its way" by kimvette · · Score: 1

      so? Don't use IE7 to read helpfiles for reading open source documentation. ;)

      (I'm kidding)

      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    38. Re:No, it's not "losing its way" by Danga · · Score: 1

      This strikes me as so factually inaccurate I can't believe it. FF 2.0 may be more featureful, but it's far faster than FF 1.5 on every piece of hardware I've tried it on. And it has fewer memory leak issues.

      Well the people I know who were complaining about the slower performance of FF noticed it with 1.5, not just 2.0. Anyway I found two somewhat recent articles showing a comparison of FF 1.5 to 2.0 as well as comparisons to Opera 9 and IE 7. NONE of them show FF 2.0 being "far faster" than FF 1.5 and for the most part 1.5 is faster or just slower by a marginal amount:
      http://www.extremetech.com/article2/0,1697,1990855 ,00.asp

      This article clearly shows how FF has a pretty significant increase of memory usage after just opening 6 tabs, FF 2.0 nearly doubled its amount of memory usage while FF 1.5 nearly tripled the amount of memory used and yet FF 1.5 still used less memory. Opera actually ended up using LESS memory after opening 6 tabs than it used with no tabs, and it still used less memory overall than FF 2.0 or 1.5 with 6 tabs open.

      Here is the next article:
      http://www.howtocreate.co.uk/browserSpeed.html#win speed

      Here it can be seen that FF 2.0 is slower than FF 1.5 in nearly every category except the cold startup time which did have a significant improvement since it dropped from a rediculous 17.26 seconds to a still very unacceptable 11.64 seconds. Why does it take so damn long to start up a freaking web browser? I mean IE 7 even beats it with a time of 7.8 seconds. Opera 9.01 kills them all with a cold startup time of 2.74 seconds which is as fast or faster than FF 1.5 and 2.0's WARM startup time. When I go to surf the web it is nice to have the browser come up almost instantaneously, I don't want to be waiting around for over 10 seconds, that is just crazy and if I don't have to do it I won't so that is one reason I prefer Opera.

      Face it, the only real reason to keep using FF is if you are used to it and the extensions you use with it and/or you seriously care if you can take a look at the source or not (which IMO I don't care about as long as the software performs better). Now that Opera has something to compete with FF's extensions (the widgets), it performs faster and is more stable than FF, and it adheres to the standards better why would you not use it?

      --
      Hey, there is only one Return and it's not of the King, it's of the Jedi.
    39. Re:No, it's not "losing its way" by NickFortune · · Score: 1
      Here, allow me to post a short summary of the article to save you some time:

      If you're going summarise, you might include the question of third party cookies and how the option to block them as disappeared from the configuration screens. That's great news for doubleclick and for Mozilla Corp's friends at Google, but it does strike a dischordant note among those of us who've been using Firefox as the browser you can trust. I don't think you can really dismiss such a basic privacy related feature not implementing a feature the way the author wants it. IHMO he raises a valid concern.

      I also don't see where he said the new theme was ugly. Just in passing,

      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.
      Fair comment. That said, are we not allowed to be concerned about the direction Firefox development is taking? My personal impression is that the FF devs have been moving steadily away from the basic idea of a minimal framework with lots of plugins, and toward a heavyweight browser with a large preset feature set that can be overriden with difficulty.

      I think I liked it best about 0.7. They've done some good stuff, and some needed stuff since, but I think I liked the browser best about then.

      --
      Don't let THEM immanentize the Eschaton!
    40. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0

      Get a clue. Firefox sucks. Why do you think "plugins" are so popular? And if that's not bad enough, 99% of its userbase is made up of rampant fanboys.

    41. Re:No, it's not "losing its way" by BiggyP · · Score: 1

      Epiphany is very nice but for the fact that keyboard shotcuts aren't, by default, predictable or sensible, default textbox focus when opening new tabs also used to be an issue, hitting Ctrl+t and having to follow up with either a mouseclick in the address bar or, wait for it, 3x Shift+Ctrl+Tab followed by 1x Ctrl+Tab to tab between the page and the address bar... nice. Of course this behaviour has probably been fixed in more recent versions.

      My Bigest problem with FF2 is that it breaks the user interface for all of the existing userbase, where did this whole close button per tab thing come from, and what's that strange new button where the close button should be? not only is it fiddly to close tabs by clicking on individual Xs, if you turn the old behaviour on then your habit of automatically seeking the right hand edge of the tab bar and clicking causes problems. Not that i don't like the new style tab bar, I can just see a lot of problems with it for less technical users who have ventured into the world of tabbed browsing with FF 1.x.

      Oh, the theme is washed out and drab, that's its other big problem, IE7 and Opera both look far more appealing to your average user when compared to the new FF2 theme.

    42. Re:No, it's not "losing its way" by JWW · · Score: 1

      I know they know what OS they're being installed on. I just don't think they should waste the effort to have the installer pick the theme to go with your OS and include a different one for each OS. I'd rather they put the time and effort into functionality and not the default theme. I always get a different theme and am confident that if an OS specific theme were selected FOR me, I'd still probably get something different.

      Anyway the basic point is bitching about the freaking default theme for Firefox is ridiculous.

    43. Re:No, it's not "losing its way" by shaitand · · Score: 1

      "Your comment is arrogant and typical of a lot of programmers that don't feel someone has worth unless they can code."

      True, although coding is the most obvious way to contribute to the project there are other ways. Of course, if you are contributing in any of those ways then I am sure the developers will recognize it and be more considerate of your concerns. If you aren't, then you are just another freeloader and from the perspective of the open source community you truely are worthless, right?

      Non-developers can also pay developers to fix things for them; paying a developer for a few hours of his time will get your concerns focused on right away. If you aren't sure how to go about this then search for open source bounty on google and you will find sites that let you post bounties. Even if you have little money and no skills you could start a grassroots advertising campaign.

      Simply because you are not a developer doesn't mean you are worthless, but if you aren't worthless from the perspective of (insert any open source project here) then you are contributing and will be able to get developer focus.

    44. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0
      If the goal of the Mozilla project is to have more and more people using the browser, then the project must respond to consumers as if Firefox were a closed-source, profit-driven product. If the goal is, as you suggest, just to throw Firefox out there and see who sticks to it, then there is no need to give a damn what the people want. The disenfranchised will just turn to browsers that do give them what they want. This is, after all, exactly why Firefox gained popularity in the first place, because it provided something the Leading Brand did not.

      However, the OP is doing nothing to help. He is merely pointing out problems, not solutions.
      There is a scorpion in your shoe.
    45. Re:No, it's not "losing its way" by Darren+Winsper · · Score: 1

      "The default theme is the user's introduction to the browser. It should have the look and feel of his native GUI."

      OK, let's look at the competition on Windows. IE7 doesn't look or feel like a standard Windows application and neither does Opera. Oh well...

    46. Re:No, it's not "losing its way" by zopf · · Score: 1
      The default theme is the user's introduction to the browser. It should have the look and feel of his native GUI.

      Perhaps. Are there any other browsers that do this? I don't know if I've ever seen one...

      I have some news for you: it's supposed to be a basic [RSS] implementation that gives you the bare essentials. If you want one with bells and whistles, go get an extension that suits your needs better.
      IE7 has raised the bar a little higher than this.


      I suppose they have in a sense, but they're also forcing every user, whether novice or advanced, to download a more complex newsreader whether or not they'll ever use it. I for one use Google Reader - thus, I would likely never use the newsreader of either program. I'm assuming that IE7's news reader has a significantly larger memory footprint than Firefox's. I'd much rather have the option to easily download a more complex newsreader than be stuck wasting my valuable system memory on technology that I'll never use.

      I think that Firefox's audience is composed of more power-users than IE7's, and thus the developers assume that users will simply download extensions that afford the features that they need. In my opinion, the Firefox team should focus on improving memory management and adding useful new features. Their kingdom was built on great features and word-of-mouth momentum. They've already got a big audience now, and there are some demographics they'll just never reach. Powerful yet simple features are what Firefox needs to stay ahead of the curve, and I wish them best of luck.
      --
      Did you see the pool? They flipped the bitch!
    47. Re:No, it's not "losing its way" by toddbu · · Score: 1
      Why is it bad form? Maybe the author is already contributing to another open source project and doesn't have time to fix the bug. Maybe he spends his nights and weekends feeding the homeless in his community. Maybe he's just had his first child and needs to take care of his new family for a while. There are lots of good reasons to point out issues without making any further contribution.

      I think that it's a mistake to assume that everyone should care about Mozilla in the same way. There are going to be lots of great coders out there that never contribute to the project, but are willing to test new builds. They offer a valuable service to the community. If you say that a person with coding skills should fix bugs then you'll drive off a lot of reporters.

      --
      If you don't want crime to pay, let the government run it.
    48. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0
      However, the OP is doing nothing to help. He is merely pointing out problems, not solutions.

      Pointing out problems that you do not have the ability to fix is not helpful? I guess we'd better close down every QA department in the world then. That's all they do is point out problems for other people to fix. Ungrateful bastards.

    49. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0
      Which bit of 'native' do you not understand?


      I have a choice between KDE, Gnome, WindowMaker, BlackBox, and 3 or 4 others, for each login session. I can even make different choices for different but concurrent sessions.

      Please define 'native' in a manner that applies to the above.

      Thank you.
    50. Re:No, it's not "losing its way" by hahafaha · · Score: 1

      As I already pointed out, the OP *does* have ways of helping fixing the problem. One is hiring a coder to do it. Another is donating money.

    51. Re:No, it's not "losing its way" by FooBarWidget · · Score: 2, Insightful

      Then are the complainers willing to pay someone to fix it for them? Are they willing to do anything at all besides complaining?

    52. Re:No, it's not "losing its way" by mahonri5 · · Score: 1

      Which is apparently due to the Carbon interface Firefox uses, as the comments on that link say. I just played around a bit on v2.0 on my Intel Mac, and I'm not even seeing any sort of cpu "spike". So either they fixed it in v2.0 or the Intel version of OS X doesn't suffer from this carbon related issue.

    53. Re:No, it's not "losing its way" by fatphil · · Score: 1

      For almost all users who have a 'Desktop Environment' then there is an underlying native style and widget set, obviously.

      The people for whom 'native' is not clearly defined is a small minority (non-Gnome/KDE users) of a small minority (linux users). One I don't mind ignoring as being insignificant to the argument, despite being a member of it.

      --
      Also FatPhil on SoylentNews, id 863
    54. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0

      IE7 has raised the bar a little higher than this.

      LOL... That comment makes no sense in context with the quote given. *cough* troll *cough*

      IE can't even lift the bar anymore, much less raise it.

    55. Re:No, it's not "losing its way" by JacksBrokenCode · · Score: 1
      Then are the complainers willing to pay someone to fix it for them?

      Of course not. Realistically we know that MS changed that landscape forever and no browser will stand a chance of widespread adoption on desktops if it is not made available for free. If Mozilla is going to have to spend money to fix a problem, it needs to learn how to be creative with its partnerships instead of trying to tax the end-user - at least that seems to be the business model the Slashdot community normally advocates.

      Are they willing to do anything at all besides complaining?

      Sometimes there are only 2 options - complain, or stop using the product. Do you really want Firefox to lose marketshare because the developers haven't bothered to fix the cut/copy/paste bug yet? Perhaps you don't copy/paste much, but I do and that bug causes me to use IE7 instead of FF. I could complain, but the bug is already logged and apparently ignored. I don't have the familiarity with the project (or the time to aquaint myself with it) to fix the bug myself and, from what many here have said, my patch probably wouldn't be accepted anyway. Even if I could fix the problem myself, what sort of message is that to send to your consumers? "If you don't like something about our product, fix it yourself or stop complaining."

    56. Re:No, it's not "losing its way" by dwarfsoft · · Score: 2, Insightful

      I am grateful they put a close box on each tab, I kept closing more than one tab because my mouse was a bit funky. I installed Tab Mix Plus on 1.x and it added the close buttons to the tabs, and also changed the tabs to scroll horizontally when you had many open, instead of trying to cram them into the available space.

      Of course, most tabs I close are done so with a Ctrl-F4. I do see your point though for people who would prefer to keep the right hand tab closer, but I see the button per tab as a blessing personally.

      --
      Cheers, Chris
    57. Re:No, it's not "losing its way" by VGPowerlord · · Score: 1

      First things first, I'm going to note that I hate skinned apps.

      I hate that web browsers have gone the way of media players in the whole "we have to be skinned" point of view. If a user wants a skin for their app, I'm not going to say that it's a bad thing, but the default should resemble the windowing system's defaults.

      Oh, before I forget, I use Opera with the Appearance changed to the native scheme for my OS.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    58. Re:No, it's not "losing its way" by Shawn+is+an+Asshole · · Score: 1

      Try the iFox theme. With that Firefox doesn't feel as out of place. Still, no theme fixes the Windows 95-ish form controls that every non-Windows system gets. XP gets native-looking forms. Why can't Linux and OS X?

      --
      "It ain't a war against drugs.it's a war against personal freedom" --Bill Hicks
    59. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0
      OK, lets try this again and see if it gets deleted again this time.... grrrrr! (Slashdot doe not edit or delete posts.,... suuurreee...)

      Don't like the default theme that comes with Firefox? Go get another [mozilla.org] that you like better.


      Then you'll fail to remove your old themes profile and extensions when you install the next version of firefox and experience dozens of bogus bugs that do not occur on a clean install.

      Don't like the default theme? Use another browser.

      Themes and mods for software are a horrifically bad idea. There is no guarantee that the theme/mod/extension author will keep pace with software releases or even continue releasing updates themselves at all. Thus you are stuck with an outdated version of the software if you insist on using old mods, worse, if you do update you'll experience all kinds of bugs and attribute them to the core software instead of the theme you are using.

      Not to mention that themes/extensions/mods are not subject to the same QA as the core product and you have zero assurance that it is of sufficient quality.

      Themes and extensions are evil. Those who suggest that functionality of software should be offloaded to extensions clearly have not though it through. The last thing you want is to depend on a feature that is not part of the core software which will probably not keep pace with the core software versioning or even be maintained at all. Locking yourself into outdated versions of the core software or bugging out newer versions when you insist on using outdated themes and extensions of poor quality.

      The whole theme/extension model of software is critically flawed and is surefire recipe for disaster and failure.

      Further Javascript being the basis for the Firefox extensions system is just plain asinine. Javascript overall is a totally stupid idea and should not come anywhere near quality software that is expected to be reilable and perform well.

      In summary: extensions/themes = bad, javascript = pure evil.
    60. Re:No, it's not "losing its way" by JacksBrokenCode · · Score: 1

      You are being ridiculous. There are nearly 400 themes available for download from Mozilla's website. It would not take a substantial amount of work to have the Mac build default ot a Mac OS theme, the Vista build default to a Vista theme, etc.

      Regardless, it's not ridiculous to bitch about the default theme. If people are detered from switching because the default theme doesn't match their OS, or is ugly, or in any other way sours their experience, they might as well have been turned away by poor functionality or performance. At the end of the day, when you are tallying marketshare, the reason people failed to adopt your browser is relatively unimportant. The fact that they did not switch over to your platform is. (The specific reasons are important for analyzing problems and planning strategy, but when news articles mention that Firefox has claimed 13% of the market they don't add a footnote that an additional 2% declined simply based on the theme.)

    61. Re:No, it's not "losing its way" by FooBarWidget · · Score: 1

      OK, let's see:
      1. Firefox has issues.
      2. People complain about the issues, yet these people do not want to or can't fix the issues.
      3. The people who *can* fix the issues either don't want to, or don't have enough time/resources to fix all of them.

      So basically, people expect a quality product for free, without any effort from their side, not even in the form of money. Don't you think there's something very wrong with this?

      Imagine yourself being a Firefox developer, and you have to deal with these complaints on a daily basis. What would you think?

    62. Re:No, it's not "losing its way" by KDEWolf · · Score: 1

      Using Ctrl + W is much easier. =)

    63. Re:No, it's not "losing its way" by Per+Abrahamsen · · Score: 1

      > This is such an elitist position and really hurts both opensource in general and Firefox
      > specifically.

      No, what hurts free software is people who think whining (as opposed to proper bug reports and feature requests) is a form for contribution. It drives the volunteer developers off the projects, leaving only the paid developers. Nobody think it is fun to give your work away for free, only to have people complain about it

      No I don't forbid you to whine. It is covered by your freedom of expression. Just don't pretend that you are contributing to the solution rather than the problem when you do so.

    64. Re:No, it's not "losing its way" by pinpoint23 · · Score: 1

      bull. i just tried this on my G4 Powerbook running Firefox 2.0 and can't reproduce it.

    65. Re:No, it's not "losing its way" by JacksBrokenCode · · Score: 1

      Actually, I generally don't expect quality products for free. I've been blasted several times on this site for suggesting that quality code/coders are worth money. However since Opera, IE, & Safari are available for free it removes the ability to gather needed revenues directly from the end-users in the form of software licenses.

      I'm not overly familiar with the structure of Mozilla Foundation & Mozilla Corporation, but I did find an interesting article where a Mozilla staff member is quoted as saying moneys from Google allowed them to hire an additional 10 people between 2004-2005. It's partnerships like that where Firefox should be deriving funding to fix bugs.

    66. Re:No, it's not "losing its way" by DerekLyons · · Score: 1
      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:

      This is such an elitist position and really hurts both opensource in general and Firefox specifically. I am going to go out on a limb here and say that a large marjority of Firefox users, myself included, don't have either the chops nor the time to gain the chops to fix bugs. Also, even if I had the chops to fix bugs, I don't have the time to get familiar with the source tree to be effective. It's not like debuging is a 5 minute deal.

      Not only that, but the Mozilla [Corporation|Foundation] is marketing Firefox as a replacement for IE - once you start marketing, it's time to think like a corporation rather than like a bunch of guys in their parent's basement. I.E. being responsive to your user community rather than to simply following your whims or doing what looks to be fun or easy.
       
       
      I updated to FF 2.0 and downgraded to 1.5 wihtin a few days because 2.0 kept freezing and crashing and to be honest, I didn't seem any new features that made upgrading compelling.

      After better than a decade as an unpaid beta tester - in the mid 90's I got off the upgrade treadmill, and don't upgrade until version x.3 or so. FF 2.0 is a clear example of the reasons why I did that.
    67. Re:No, it's not "losing its way" by KDEWolf · · Score: 1

      You can just you this extension: http://users.blueprintit.co.uk/~dave/web/firefox/n ightly Or even do this: http://lifedev.net/2006/10/firefox20-extension-upd ate/ Then you can keep all your old-forgotten-etc extensions.

    68. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0

      Advice useful only to a programmer and likely only to a programmer on the Firefox team.

      It really depends on your level of expertise and what the bug is.

      As an example if you use the nightly builds of Firefox and on day 0 there's no bug and on day 1 there's a new bug then you can feasibly look at the changes and rebuild Firefox with each patch applied in series until the bug is there. Then you can submit a bug that details this finding.

      A lot of work? It can be, depending on the circumstance.

      Does it help the developers out to know what patch is the cause of a bug? Definitely.

      Do you have to be super experienced to provide some if not all of this information? Nope.

    69. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0

      The default theme is the user's introduction to the browser. It should have the look and feel of his native GUI.

      I think you're exactly correct here which is why IE7's interface was like a slap in the face. Even Opera and FF's interface, while not OS default, are much gentler on the eyes/brain.

      Advice useful only to a programmer and likely only to a programmer on the Firefox team.

      I think you're partly right. I'm a nerd who doesn't code. But I can help identify broken areas and then report them to whomever will listen. I dislike when the common reply is "go fix it yourself" and I wish it were replaced with a question of "well, do you think you might be able to help us solve it?" However, there are programmers out there who can help. Microsoft never even gives you the choice.

      IE7 has raised the bar a little higher than this.

      I guess there are still some personal preferences floating around out there. I, for one, like to have FF without weird RSS ribbons on most of my installations. And on the one computer where I want an RSS reader, the Sage extension is absolutely superb for my needs.

      In any event, those folks who like the IE7 implementation of RSS should think carefully for tossing out phrases like "raised the bar" which comes across as droidspeak.

    70. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0

      - But I'm sure they're working on it

      Don't be. Firefox is a hell of an achievement and one of the finest browsers in the world, but fixing bugs is not always as good as it should be. For example, the very annoying undersizing of PRE text that was introduced & reported & noted for fixing way back in Moz 1.0, has still not been fixed. There are definitely gaps in the system.

      (Some developers may not have noticed this bug and are raising eyebrows. That's because it only bites if you specify generic monospace, but not if you spec a particular monospace font. Hence your experience so far may have been trouble-free.)

    71. Re:No, it's not "losing its way" by Angostura · · Score: 1

      Imagine yourself being a Firefox users. What would you think? Aside from "I think I better use something else".

    72. Re:No, it's not "losing its way" by BenoitRen · · Score: 1

      But have you tried the more recent Mozilla suite, or the new SeaMonkey (Mozilla 1.8 in disguise)? It sounds like you did so only a long time ago, because tabbed browsing has existed in Mozilla for many years now.

    73. Re:No, it's not "losing its way" by matw8 · · Score: 1
    74. Re:No, it's not "losing its way" by zsau · · Score: 1

      But much scarier—Ctrl+W always used to close the window. Now I never have any idea what it'll do, and I just use my mouse. I wish they used a new command, like Ctrl+T instead of Ctrl+N for a new tab vs window. (This is a problem in (?almost) all tabbed web browsers I've used, so I suppose it's too late to change.)

      --
      Look out!
    75. Re:No, it's not "losing its way" by 75th+Trombone · · Score: 2, Informative

      I think Firefox's Ctrl+W does exactly what it should.

      In Multiple Document Interface apps, it closes the app's active subwindow. For instance, in Photoshop it closes the current focused document, not the entire application window. Tabbed Document Interface is a somewhat different paradigm from MDI; tabs in TDI are analogous to windows in MDI. Therefore, Ctrl+W should close the current tab.

      'S how I see it, anyway.

      --
      The United States of America: We do what we must because we can.
    76. Re:No, it's not "losing its way" by bill_mcgonigle · · Score: 1

      They used to use the old mac event loop but switched to Carbon events in the 1.8 timeline. 2.0 uses Carbon events. To be fair to the whiners, it took about five years to get this done - to be harsh to the whiners, the work probably could have been done five years ago if somebody had just put up and shut up - the years of whining weren't really effective.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    77. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0
      "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!"


      Hey no offense, but why the hell would he want to take care of Firefox bugs or lack of features? He's writing a review about the program, and I see no reason why he shouldn't be pointing out its setbacks!

      Maybe there's some people out there that just doesn't have the time to code for every open source program they use!
    78. Re:No, it's not "losing its way" by Anonymous Coward · · Score: 0

      i'm confused. afaik that bug is fixed in ff2. why are you harping it?

    79. Re:No, it's not "losing its way" by misleb · · Score: 1

      There is a little more to adhering to the look and feel of an OS than "themes." Most OS "themes" that I have used are actually very superficial. Normally I avoid cross-platform applications such as those built on Java because they never seem to look and feel quite right. A web browser, however, is in a rather unique position such that adhering to the native OS look and feel isn't nearly so important as with other apps. I mean, the vast majority of your interaction is within the rendered HTML, which, presumably, looks pretty much the same everywhere.

      Anyway, complaining about the default theme if Firefox is pretty lame. Yeah, sensible default are important for an application, but geez.

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    80. Re:No, it's not "losing its way" by Llywelyn · · Score: 1

      Sure.

      Use another web browser. Perhaps another free one (I use Safari), or pay a nominal fee to a small company that might actually listen to bug reports.

      Easy.

      --
      Integrate Keynote and LaTeX
    81. Re:No, it's not "losing its way" by misleb · · Score: 1
      Face it, the only real reason to keep using FF is if you are used to it and the extensions you use with it


      You say that like it isn't a damn good reason. Extensions are the reason I use Firefox. I don't care if one browser is a little faster than another or if one uses more memory than another. RAM is cheap and my CPU is fast. I just will not surf the web without my Adblock Plus w/ Filterset-G, for example. Sometimes adblock leaves "holes" in pages. For that I have the Remove It Permanently extension. With it I can easily remove any element from any web page. I've browsed the web on other people's computers without proper filtering and I am horrified. Just horrified.

      In a way I am "used to" the extensions that I use, but I use them because they aren't available elsewhere. Not even Opera. AFAIK, Opera's "widgets" can't really do what you can do with a FF extension. FF extensions modify the basic operation of the browser... adding to the menubar or context menus or even acting transparently. For example, I am currently using the Slashdotter extension that allows me to highlight text in a comment and generate a reply with the selected text quoted. Sure beats copy/paste/insert HTML tags. Widgets are just windows with specific information in them. There really isn't much comparison.

      -matthew
      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    82. Re:No, it's not "losing its way" by misleb · · Score: 1

      Sounds to me like it is actually a Carbon problem, and not a FF bug. The only issue I see here is that the bug wasn't closed with the appropriate explanation for why it won't be fixed. Either way, I don't think the problem is quite as serious as your article suggests. Who cares if my CPU jumps to 90% when I click and hold the mouse? What else is my computer doing? OS X has good enough multitasking that my system won't grind to a halt because one app wants a lot of CPU for a short time. I certinaly never noticed any problem. And I run FF on a G4.

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    83. Re:No, it's not "losing its way" by zsau · · Score: 1

      Thanks for explaining the justification. I switched to Linux back when Netscape Communicator 4 was latest-and-greatest, and X apps generally don't have Windows-style MDIs. And considering that tabbed browsers allow multiple toplevel windows, I've always thought of it as a special kind of SDI thing...

      --
      Look out!
    84. Re:No, it's not "losing its way" by FooBarWidget · · Score: 1

      I am a Firefox user. And I don't think 'better use something else'. What am I supposed to use besides Firefox? IE 7? Opera? The fact that Opera has even less market share than Firefox despite that there are less people complaining about Opera says a lot.

    85. Re:No, it's not "losing its way" by FooBarWidget · · Score: 1

      "Listen to bug reports"? Do you really mean "listen to bug reports" or "fix every possible bug report that people have ever posted"?
      If it's the former, do you really think Firefox listens to absolutely no bug report? Or maybe, just maybe, it's because they can't fix everything and have to prioritize things?
      If it's the latter, please show me a single company that has the resources to fix all reported bugs.

    86. Re:No, it's not "losing its way" by VENONA · · Score: 1

      "It should have the look and feel of his native GUI." What if your GUI is themed? My KDE looks nothing like an out of the box KDE. I have no problem with expecting people to be willing and able to download a frapping theme. If we dumb things down to the point where *that* is regarded as too much of a burden, we have gone *way* too far.

      >>I have some news for you: it's supposed to be a basic [RSS] implementation that gives you the bare essentials. If you want >>one with bells and whistles, go get an extension that suits your needs better.
      >IE7 has raised the bar a little higher than this.

      One persons feature is another person's bloat. Danga, in a post above, didn't like having to download extensions when loading a new system--nor does he like bloat. Well, building everything in obviously increases bloat, and I personally like the flexibility of the extension model, as you seem to. Not that I'm saying that FF has no bloat without extensions...

      But I'll go further--leave out RSS as well. There's no particular reason for it to be in the Web browser. To me, that's an artifact of primitive desktops--where you have only one desktop. If you can have several, it's often more convenient to keep mail, calendar, Usenet, RSS, etc., (basically, all of the communications and news stuff) on one desktop while reserving another for the Web browser. Notifications via the panel work fine, and this keeps all of that stuff out of my way when I'm trying to work.

      Granted, when I click an item in my standalone RSS app, another instance of my browser (Konqueror) is created to view it. But that only takes (literally) a second, under normal system loads.

      Maybe that's just me, and my work habits. But maybe it's also a decent argument for carrying the Unix philosophy of small, sharp tools onto the desktop, insofar as such a thing is possible.

      --
      What you do with a computer does not constitute the whole of computing.
    87. Re:No, it's not "losing its way" by WuphonsReach · · Score: 1

      This strikes me as so factually inaccurate I can't believe it. FF 2.0 may be more featureful, but it's far faster than FF 1.5 on every piece of hardware I've tried it on. And it has fewer memory leak issues.

      Try this simple test... fire up FF 1.5 or FF 2.0 over a dial-up line. Open up a page in the background and watch the entire UI freeze while FF does the DNS lookup and opens the initial connection to the web server.

      Which basically makes background loading of tabs near useless.

      Especially when you're doing search engine stuff and opening interesting links in the background while you continue looking for more interesting links.

      There's no reason that the UI should block while processing background tabs.

      --
      Wolde you bothe eate your cake, and have your cake?
    88. Re:No, it's not "losing its way" by Llywelyn · · Score: 1

      Every point against Firefox is not some holy grudge match. The question is: What works for you?

      You can pay a nominal fee for OmniWeb, and it provides a lot of features that FireFox doesn't. Their support lines are excellent (in my prior experience with the company), and they use webkit so they are compatible with everything that is compatible with Safari. Because they have a smaller customer base, they do not need the support something the size of Firefox does.

      Do they fix every bug? No, but at least they have a product they are selling and thus prioritize bugs differently than a group of open source developers would. Not necessarily better in the cosmic ethereal sense, but possibly better for me.

      --
      Integrate Keynote and LaTeX
  2. A Few Miss-Steps Maybe by eldavojohn · · Score: 5, Insightful
    "It seems Firefox has lost its way somewhere along the passage to fame."
    I think "lost its way" is too strong of a phrase. Sure, some of these points are negative but I haven't really experienced that much of a negative experience. It's good to criticize this project (with constructive criticism) so that it stays as great as it is. But to say that it's lost its way I think is going too far.

    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.
    1. Re:A Few Miss-Steps Maybe by dvice_null · · Score: 4, Informative

      > I think "lost its way" is too strong of a phrase.

      I agree. The developer are mostly focusing on Firefox 3.0 anyway, because of the major improvements it will have. The 2.0 was just a small upgrade in the middle, mostly because of the PR. Because the changes in 3.0 require a lot of development and a lot of testing, they didn't want to hurry it. So I wouldn't judge Firefox because of the 2.0. Better wait for 3.0.

    2. Re:A Few Miss-Steps Maybe by ralphdaugherty · · Score: 1

      The concern that it makes itself the default browser is valid but using the word 'hijacking' is a bit strong.

            Just FYI from my recent experience, I installed Firefox 2.0 on my clean Win XP Pro and I'm fairly certain Firefox asked if it wanted me to make it the default browser just like all my previous Netscape installs on prior PC's did.

        rd

    3. Re:A Few Miss-Steps Maybe by ildon · · Score: 1

      I wouldn't underestimate the average user's ability to judge a piece of software based on how good it looks. The question is whether or not they're going to realize they can change the theme and then change it to something they like before they just give up on it.

    4. Re:A Few Miss-Steps Maybe by Cl1mh4224rd · · Score: 2, Interesting
      So I wouldn't judge Firefox because of the 2.0. Better wait for 3.0.
      Ugh! I'm a fan of Firefox, but that line pisses me off. Arbitrarily declaring which stable, public releases of a piece of software shouldn't matter is absolutely asinine.

      And before that you claim it was merely a PR stunt. What the fuck, man? How did that get modded Interesting and Informative? Seriously. Microsoft gets absolutely blasted for less than what you just implied the Mozilla Foundation did with Firefox 2.

      The Mozilla Foundation judged it to be worthy of a public release. It was put out there for all people to evaluate. For the first time ever I saw Firefox in my local newspaper (comparing Fx2 to IE7).

      You can't seriously claim that the browser shouldn't be judged based on this release.
      --
      People will pass up steak once a week, for crap every day.
    5. Re:A Few Miss-Steps Maybe by kraada · · Score: 2, Interesting

      > I wouldn't judge Firefox because of the 2.0. Better wait for 3.0.

      When 3.0 comes out will you say not to judge it because of the major changes scheduled for 4.0?

      Not trying to troll here, but what we should judge a software by, imho, is the current released stable version. You can't judge a game by what the game will end up looking like when they finally patch the bugs; what they release is what you have.

      Especially if they're going to make a huge PR push for people to use 2.0, they really ought to consider that a version people should judge by.

      That said, I like FF 2.0 just fine, but maybe I'm easily pleased?

    6. Re:A Few Miss-Steps Maybe by Anonymous Coward · · Score: 0

      Try is too strong a phrase.

      Along with your, poster's, and loser.

    7. Re:A Few Miss-Steps Maybe by dvice_null · · Score: 2, Interesting

      There is a big difference between 2.0 and 3.0. The 2.0 is only getting small changes and some eye-candy, they never accepted any bug fixes to 2.0 that could potentially make it unstable. In the 3.0 they are changing the whole rendering engine to a complitely new one. 4.0 is too far away, but currently I do bulieve that Firefox 3.0 will be a much greater success than 2.0 ever will be.

      And yes, I agree with you. I don't hate 2.0, but I think it was a mistake to release it, just because they think the release cycle between 1.5 and 3.0 would have been too long. Then again, I'm a programmer and Firefox has had a pretty good history in marketing, so I think they know better than I. After all, it is the marketing that has given the Firefox the status it currently has. AFAIK majority of the people like 2.0, but I think there have been more complaints about 2.0 than there were about 1.5. Then again the user base is increasing constactly which could be the reason for this.

    8. Re:A Few Miss-Steps Maybe by dvice_null · · Score: 1

      > Arbitrarily declaring which stable, public releases of a piece of software shouldn't matter is absolutely asinine.

      I just mean that the development of the 2.0 and 3.0 was started pretty much the same time. No big changes were accepted on the 2.0 and I've seen a lot of complains about 2.0 not being much of an improvement when compared to 1.5. Which is true, because all the big improvements have been implemented in the 3.0.

      The thumb rule is that when the major version number of the gecko changes with the new version, then there have been some real effort behind that version, so you can expect some changes. 2.0 uses almost identical version of the gecko with 1.5 (both use 1.8.x). In the 3.0 there will be new version of the gecko (1.9).

    9. Re:A Few Miss-Steps Maybe by gad_zuki! · · Score: 1

      >The concern that it makes itself the default browser is valid but using the word 'hijacking' is a bit strong.

      Its there for comedic effect. I wanted to download an extension for thunderbird. Firefox assumes the xpi is for itself and tries to install it. The ff developers removed the "save as" button from the xpi download window. The mozilla web people made the extension website so you cant just right-click and save as to download an extension. Instead of trying to find the ftp depository, the right version, etc I had to use IE to download an xpi. Now thats funny.

      Toss in the dumbed down interface (larger tabs, tab scrolling) and dumbed down options, well, Im concerned.

    10. Re:A Few Miss-Steps Maybe by Americano · · Score: 2, Interesting
      I agree. The developer are mostly focusing on Firefox 3.0 anyway, because of the major improvements it will have. The 2.0 was just a small upgrade in the middle, mostly because of the PR. Because the changes in 3.0 require a lot of development and a lot of testing, they didn't want to hurry it. So I wouldn't judge Firefox because of the 2.0. Better wait for 3.0.


      s/Firefox/Internet Explorer/g
      s/3.0/7.0/g
      s/2.0/6.0/g

      If somebody made THAT argument in public, they'd be strung up. But because it's Firefox, it's okay? Come on. 2.0 is a MAJOR release. If it was a temporary / bugfix release, it should have continued as 1.5, 1.6, 1.7, 1.8, and so on... and the "3.0" version should have been labeled 2.0.

      Clearly, Mozilla felt this release was "the second MAJOR release of Firefox," with all that that statement implies. And the generally sluggish performance & horrendous memory footprint of the 2.0 version of Firefox is the main reason I switched *back* to using Safari for home use, and IE6 at work.
    11. Re:A Few Miss-Steps Maybe by arifirefox · · Score: 1

      Firefox 2 may certainly be judged favorably compared to other browsers like IE7. Most people have never tried Firefox and I'd rather have them try v2 than v1.5 On the other hand, v2 compared to v1.5 might not be such a big difference if you already have it. But who cares? it's free anyway

      --
      Firefox Power http://firefoxpower.blogspot.com/
    12. Re:A Few Miss-Steps Maybe by juhaz · · Score: 1

      I don't think it was a mistake to release it, but it was a mistake to call it 2.0. It should've been 1.6, perhaps with the old theme, to reflect the truth that it's relatively minor maintenance update. Jumping major version number got expectations way too high, and most people were thinking they're going to get something more than they did.

  3. Slashdot losing its way? by Anonymous Coward · · Score: 4, Insightful

    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!

    1. Re:Slashdot losing its way? by Albert+Sandberg · · Score: 1

      I agree, and I don't plan on stopping using firefox for any near future. And I don't plan on removing it form my moms puter neither. Just because I don't download it so often doesn't mean I'm not using it.

      As a sidenote, I think we should let firefox call home (as part of the update check) just to be able to keep a count on the number of firefox users to get an exact number... I'm not paranoid.

    2. Re:Slashdot losing its way? by An+Onerous+Coward · · Score: 4, Funny

      Hey, if you think there is a bug in Slashdot's story-selection algorithm, there's nothing stopping you from fixing it. :)

      --

      You want the truthiness? You can't handle the truthiness!

    3. Re:Slashdot losing its way? by Anonymous Coward · · Score: 0

      I tried submitting a patch for CmdrTaco, but he kept removing it. He said it itches.

    4. Re:Slashdot losing its way? by lobotomir · · Score: 2, Funny

      Firefox's default theme? Pimpzilla FTW!

    5. Re:Slashdot losing its way? by Dan+Ost · · Score: 1

      Create an extension that phones home. That way, only the people who care to be counted will be counted.

      --

      *sigh* back to work...
  4. I don't know about 'Firefox 2 Recap' by Unski · · Score: 1

    How about a 'web design recap' for NeoSmart Technologies, as having to fend off a popup which pointlessly informs me that "Mozilla 1.3 Beta is not supported! I'll try, though, but it might not work." has somewhat dampened my interest. Perhaps my 'Mozilla' is 1.3, but that's probably because it's a 'WebKit'.

  5. no subject by Anonymous Coward · · Score: 0

    Very lame article.
    Firefox 2.0 is better than 1.5 (and definitely better than MSIE).

    1. Re:no subject by Anonymous Coward · · Score: 0

      Well, you've convinced me.

  6. Re:JESUS FRACKING CHRIST by codegen · · Score: 0, Offtopic

    Somebody got up on the wrong side of the bed this morning

    --
    Atlas stands on the earth and carries the celestial sphere on his shoulders.
  7. Focus on Gecko by Muramasa · · Score: 2, Insightful

    The only things that should be added to Firefox are bug/security fixes. Leave all the bells and whistles stuff to the extension authors.

    Their bugzilla is so filled with ancient bugs that no one has eve nlooked at, and gecko is falling behind their competitors. They really need to get their priorities straight.

    1. Re:Focus on Gecko by westlake · · Score: 2, Insightful
      Leave all the bells and whistles stuff to the extension authors.

      which means that any reasonably useful configuration of Firefox is likely to crash because of some poorly written extension.

    2. Re:Focus on Gecko by dvice_null · · Score: 1

      They are focusing on the Gecko. Search Wikipedia article about Firefox and check the version 3.0, where the major development will happen.

    3. Re:Focus on Gecko by Bert64 · · Score: 1

      What we need is a packaging system, so you can roll your own firefox installer with a bundle of default extensions...

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    4. Re:Focus on Gecko by jesser · · Score: 2, Informative

      The people who fix bugs in and refactor parts of Gecko are mostly not the same people who add frontend features to Firefox. Those activities involve different skills and programming languages.

      --
      The shareholder is always right.
    5. Re:Focus on Gecko by hao2lian · · Score: 1

      I can't believe this people modded this Insightful.

      > The only things that should be added to Firefox are bug/security fixes. Leave all the bells and whistles stuff to the extension authors.

      This is tantamount to saying Firefox is feature-complete. There's no software project that's feature-complete. Ignoring users (not to mention every single new technology that the Internet churns out these days) and fixing bugs is ignorant and arrogant and only leaves a software project as a sitting duck.

      > Their Bugzilla is so filled with ancient bugs that no one has even looked at...

      It's a huge project. Of the 350,000 bugs filed with more coming in everyday, some bugs get left behind. The perfect project you describe where every bug is looked at with loving detail doesn't exist.

      > ... and gecko is falling behind their competitors.

      By what? Cool points? Ploids?

      --
      Pelé!
  8. typo by Unski · · Score: 1

    that should be "my 'Mozilla' is < 1.3."

  9. FF experience by Rosco+P.+Coltrane · · Score: 3, Insightful

    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
    1. Re:FF experience by kosmosik · · Score: 3, Interesting

      > 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.

      I don't know what you/need expect from a browser but from my point of view Fx 2.0 *is* faster and uses less memory. Also I find that few new features (improved tabbed browsing, closed tab history, more polished interface) simply nice and usefull to me.

      What bloat you are reffering to exactly? Since Fx 2.0 comes with very few new visible features and all of them are usefull for some people. And what bling?

      > 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:

      These are not extensions but plugins. Plugin is binary platform specific library that you load up into the browser. Extension is multiplatform XUL code running on top of Gecko/Fx engine.

      > about 1 out of 10 times, the cpu goes to 100% and FF is dead in the water.

      I can not confirm that. Have you tried your Linux (I assume Linux since you've mentioned mplayer) distribution's Bugzilla? I use Linux, I use features you mentioned and Fx does not crash on me. Neither I've seen reports similar to yours so.

      (...)

      > 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...

      To cut the bullshit. Have you filled a bug report about your problem?

    2. Re:FF experience by shmlco · · Score: 4, Insightful

      Personally, I think the team set expectations too high with a "major" 2.0 version number increase, when in actuallity there's little added that seemed to warrant such a major release.

      I suspect that if this had been released as FF 1.6 little of this type of criticism would be appearing, because then the implication would not have been that of releasing a new "blockbuster", but that they're simply adding improvements and features at a smooth, steady pace.

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    3. Re:FF experience by Cheech+Wizard · · Score: 1

      "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."

      --- Maybe it's your machine or machine setup, not FF. This doesn't happen on any of my computers, Mac or PC. I see this all the time: "Such and such sucks as a program". I check the computer and there are setup or other problems (the latest was a PC with a virus and the owner was blaming it on 'poor software' he was using).

    4. Re:FF experience by Ant+P. · · Score: 1

      The 100% CPU thing is usually caused by a brain-dead webserver admin incorrectly setting up the server to send them as text/plain (or worse, HTML). Firefox has a hard time parsing several hundred KB of binary garbage and rendering it as text, but then MS notepad is just as bad.

    5. Re:FF experience by shaitand · · Score: 3, Interesting

      I have experienced the same browser locks with FireFox for as long as I can remember (definitely goes back beyond the 1.0 mark). Usually what occurs is that the entire browser locks while the content is loading (be it a video, or pdf, or whatever) and you are unable to switch tabs. Sometimes the browser simply stays unresponsive.

      For me, this is the only severe issue I encounter with FireFox on a regular basis. If I am loading a video, pdf, or sometimes even a web page that is slow to respond or is unable to contact the server/resolve dns; I need to be able to open a new tab or switch to an already open tab and view something else while I wait.

    6. Re:FF experience by kosmosik · · Score: 1

      Maybe. I don't know. :) Main plugin that I use is Flash. It is embeded in most of the pages so I think I would notice problems with it.

      As for PDF and other plugins I don't really use them. I prefer to download the PDF and then open it in Acrobat. Also you haven't stated which platform are you reffering to - Linux? Windows? OSX?

      With Linux (my main platform) I can imagine such problems with *closed* *source*, *binary* plugins that are usualy *awkard* and use *old* ABI. I am sure that there may be a problem in such setup. It is not exactly Fx problem - I am sure Fx devs do what they can to make these things work but you have very much variables in typical Linux setup so probably it is hard to debug. I think the problem is mostly with using closed obscure plugins not with Fx itself.

      But still my point is that you can fill in a bug report (have you done this?). I strongly encourage you to do so. By filling a bug report (and if other users are submitting/confirming similar problems) you are getting developers attention and if this can be fixed I think it will be fixed in upcoming release.

    7. Re:FF experience by RAMMS+EIN · · Score: 1

      ``> 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.

      I don't know what you/need expect from a browser but from my point of view Fx 2.0 *is* faster and uses less memory.''

      That seems a common theme with Firefox 2.0: it's faster and leaner for some people, slower and fatter for others, and about the same for some people, too.

      ``What bloat you are reffering to exactly? Since Fx 2.0 comes with very few new visible features and all of them are usefull for some people.''

      That's pretty typical for bloat: it's useful for some. That's what extensions/plugins/modules/whatever are for: those who want the feature can get it, those who don't want it don't pay the price. Enforcing a modular design tends to result in cleaner code, too; something that Firefox could do with. And for those who believe Firefox is a "minimal base": it's still larger than Opera and Konqueror, which are comparable in features if they don't do more.

      ``> about 1 out of 10 times, the cpu goes to 100% and FF is dead in the water.

      I can not confirm that.''

      That doesn't really mean anything.

      ``Neither I've seen reports similar to yours so.''

      The post you're responding to is one. At least one reply to you claims similar issues. I've heard this kind of claim made before. I can't confirm or deny these claims, but they're out there.

      ``Have you filled a bug report about your problem?''

      Now there's some good advice. And in case someone else already filed that bug, I seem to recall Bugzilla allows you to somehow add a notification that this bug affects you, too. It's been ages since I last used it, though, so I could be wrong.

      --
      Please correct me if I got my facts wrong.
    8. Re:FF experience by shaitand · · Score: 1

      "Also you haven't stated which platform are you reffering to - Linux? Windows? OSX?"

      I am a computer technician who performs commercial and residential onsite service. I service hundreds of computers and almost all of them have different hardware configurations. Most systems are windows but since I am something of a linux geek there are no shortage of linux configurations either. I have never seen a system that did not have the previously discussed locking issue. Perhaps if you click on a link and a page is loading an embedded mpeg video you expect the browser to become unresponsive while the content loads? Or perhaps you do not heavily multi-task? I usually have a dozen or so tabs open and while that video says 'loading' or still has the grey box sitting there before it even says loading, I need the browser itself to be responsive.

      P.S. The problem occurs with flash content as well. I doubt it is a problem that all these services happen to have in common. It is certainly a FF issue. I suspect the code is blocking somewhere that it shouldn't and everything else is halted while waiting for a timeout or response.

    9. Re:FF experience by petermgreen · · Score: 1

      i don't think so.

      at least in my experiance on my laptop when i click on a pdf with acrobat not running the acrobat splash screen pops up very quickly indicating that firefox knows the document is a PDF

      at the same time my laptops fan goes to its highest setting, task manager indicates firefox at 100% CPU and firefox freezes.

      once acrobat finishes loading firefox usually recovers but every so often it doesn't.

      firefox does have problems in the rendering big documents area though, a good example of a document that is perfectly valid but makes firefox rather sick can be found at http://dev.icu-project.org/cgi-bin/viewcvs.cgi/*ch eckout*/charset/data/xml/gb-18030-2000.xml

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  10. Learn To Cuss by Anonymous Coward · · Score: 0

    Don't look now... but "frack" isn't even a real word... did somebody pee in your sixth cup of coffee this morning or what?

    1. Re:Learn To Cuss by Lord+Kano · · Score: 0, Offtopic
      Don't look now... but "frack" isn't even a real word... did somebody pee in your sixth cup of coffee this morning or what?

      Just because it isn't real doesn't mean that it doesn't exist. Kind of like the square root of -1.

      • frack - from Battlestar Galactica. Similar meaning to "fuck", but its use by children in a 1978 TV show suggests that it carries no more social weight than "rats" or "darn" within the universe of the show.


      LK
      --
      "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
    2. Re:Learn To Cuss by Anonymous Coward · · Score: 0

      FIRST of all.

      REGARDLESS of whether you spelled "frack" correctly (which you didn't, you couldn't, it's still not a real word).

      YOU spelled "minuscule" incorrectly.

      SECOND of all.

      WHY should I be the one that has to tell you that, just because you saw it on TV, doesn't make it right? They use "frack" because using "fuck" is illegal for them. But not for you!!

      IT'S not like you're really "spoofing" anybody... we all know what "frack" is supposed to mean... and quit using all of your shell accounts to make a bunch of garbage AC posts. Would you like it if someone did that the next time you misspell "minuscule" in one of your article submissions?

      Hmm?

    3. Re:Learn To Cuss by Anonymous Coward · · Score: 0

      'i' is taught in schools. Frack is not (because it's not a real word, nope, no more than gajillion).

      So you're the over caffeinated troll?

    4. Re:Learn To Cuss by Anonymous Coward · · Score: 0
      Three letter words that show up in every sentence, versus a 9 letter word that's relatively rare? You're really reaching aren't you? Why are you so defensive? You can't master a simple three letter word in a story you submitted? Nobody proofreads and edits my posts so who cares if I got one word wrong in a off-the-cuff spur-of-the-moment comment? It's and its are so common, so easy to master. Spell check would have caught my error.


      *I* would have taken the 3 seconds to spell check my story. And I master the dreaded its/it's. I also master "definitely".

    5. Re:Learn To Cuss by Anonymous Coward · · Score: 0

      Miniscule is an acceptable variation of minuscule. It's not wrong just because your spell checker doesn't recognize it.

    6. Re:Learn To Cuss by Anonymous Coward · · Score: 0

      I didn't submit the story, I manage to master the its/it's issue as well; you'll know if one of my stories ever gets accepted - I'll have spent hours making three or four sentences "perfect". Fuck, I do that with many of my posts (non-AC posts that is).

      I do however think the grammar gestapo should pick up and get out; y'all are not wanted here (as is evident from the moderation of this thread).

      Count the number of off-topic posts that exist because of your "off-the-cuff spur-of-the-moment comment". This is more unacceptable than a spelling error that 98% of people don't damn near have heart attacks over, the majority of which probably didn't even notice (if you read something and you understand what was being communicated, they wrote it 100% perfectly didn't they?)

      I'm having a good time with this; you're obviously a funny guy to pick on because you take everything so seriously and personally. I just hope you're not some poor shit's manager...

    7. Re:Learn To Cuss by Lord+Kano · · Score: 1

      'i' is taught in schools. Frack is not (because it's not a real word, nope, no more than gajillion).

      Schools teach plenty of things that aren't true and fail to teach many things that are. What does that prove?

      So you're the over caffeinated troll?

      I'm neither afraid to post while logged in, nor to use actual profanity.
      Just look at my recent posting history.

      LK

      --
      "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
    8. Re:Learn To Cuss by Anonymous Coward · · Score: 0
      Schools teach plenty of things that aren't true and fail to teach many things that are. What does that prove?

      I agree. We should ditch 'i' and start teaching "frack" as acceptable vocabulary.

      I'm neither afraid to post while logged in, nor to use actual profanity.
      Just look at my recent posting history.

      But since in both cases, you can do both simultaneously (not absolutely simultaneously, but you get the idea), this proves nothing.
    9. Re:Learn To Cuss by Lord+Kano · · Score: 1

      I agree. We should ditch 'i' and start teaching "frack" as acceptable vocabulary.

      Schools don't teach "fuck" as acceptable vocabulary, but I don't see you decrying it's use on the grounds that it's not a real word.

      But since in both cases, you can do both simultaneously (not absolutely simultaneously, but you get the idea), this proves nothing.

      Why lie? I'm not running for office.

      LK

      --
      "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
  11. I'm quite happy with 2.0 by BRUTICUS · · Score: 2, Insightful

    The only thing that bugs me is the new TAB OVERFLOW managing. Before it scaled the tabs down. YES, there was a limit to how many it could hold but it could hold more on the screen at once. A combination of both means of managing the overflow would have been the better way.

    1. Re:I'm quite happy with 2.0 by ehrichweiss · · Score: 1

      I second this. I also have become more than accustomed to clicking on the "X" all the way to the right of the window to close the current tab as well, and now I have to find the "X" that corresponds to the current tab. Grr. Other than that, I'm fine with it. I surely don't have nearly the issues with memory as I did before.

      --
      0x09F911029D74E35BD84156C5635688C0
    2. Re:I'm quite happy with 2.0 by Chrismith · · Score: 1

      There's a simple fix for this; type "about:config" in the address bar and look for "browser.tabs.tabMinWidth". This value dictates the smallest size that the tabs will shrink to before employing the scroll bar. I have mine set to 50, and this seems to be about the same value used in FF 1.5. So basically, you get the 1.5 behavior, with the added bonus that when the tab bar gets full you can scroll it.

    3. Re:I'm quite happy with 2.0 by Anonymous Coward · · Score: 1, Informative

      Get Tab Mix Plus, it will solve all your tab woes and then some:

      https://addons.mozilla.org/firefox/1122/

    4. Re:I'm quite happy with 2.0 by chaidawg · · Score: 3, Informative

      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.
      For the issue of tab size and overflow managing, you can edit the browser.tabs.tabClipWidth and .tabMinWidth settings

    5. Re:I'm quite happy with 2.0 by BRUTICUS · · Score: 1

      Excellent! Thanks for that. Props to Mozilla Firefox.

    6. Re:I'm quite happy with 2.0 by kailoran · · Score: 1

      User-friendliness for the win... It would probably kill the Firefix devs to put those options somewhere in the Options or preferences screen or whatever.

    7. Re:I'm quite happy with 2.0 by Anonymous Coward · · Score: 0

      thank you for your advice.

      -Sj53

    8. Re:I'm quite happy with 2.0 by Tim+C · · Score: 1

      Or explain it in the Help, or hell just include a single page of help text describing the core options in about:config (ie the ones used by FF itself, not extensions).

      I'm old and cranky; I don't think I should have to search the web just to find out that an option can be tweaked, let alone how to tweak it, what the valid values are and what each or them means.

    9. Re:I'm quite happy with 2.0 by hao2lian · · Score: 1

      Loading up an application's options or preferences--more often than not--decreases user-friendliness. Look at Microsoft Word's options.

      --
      Pelé!
    10. Re:I'm quite happy with 2.0 by ehrichweiss · · Score: 1

      If you were a girl and I weren't already married, I'd propose to you right now. Thanks for that.

      --
      0x09F911029D74E35BD84156C5635688C0
  12. neosmart.net losing it's way? by Anonymous Coward · · Score: 1, Funny

    Slashdotted biatch!

    Someone who can't even survive a slashdotting over thanksgiving weekend critising Mozilla?

    Hahahahaha.

  13. Firefox is slow by hardcampa · · Score: 0

    Firefox lost its way a long time ago. Firefox is easily the slowest browser out there. Just do a swift comparison between it and Opera 9. Both are freely available for download, so download and compare. Opera not only starts faster, it is more stable, and runs faster. Defending FF just because it's opensource is one thing but being irrational and actually using it is another.

    1. Re:Firefox is slow by Anonymous Coward · · Score: 0

      You name one other browser to support your argument that FF is the slowest browser, but you didn't even provide any detail to substantiate that comparison. Critical thinking and intelligent discourse aren't really in your repertoire, huh?

    2. Re:Firefox is slow by Anonymous Coward · · Score: 0

      I did that test for a couple of weeks and Firefox2.0 still felt faster than Opera and IE7, although I would agree that Opera is by far the better browser of the three.

      As soon as Opera-devs implement Firefox's tab-behaviour and middleclicking (which is the main Firefox advantage - saw several people switching from IE6 to FF because of it), then I'll switch to Opera permanently. In fact, I find it amazing that you can easily customize everything in Opera, except for these elementary actions which end up being a dealbreaker for me at the moment (and no, I don't want a keycombo or mousegesture substitute for what is supposed to be a simple mouseclick).

      I don't know why people are saying FF2.0 is worse than FF1.5, as nothing's really changed that you can't roll back through customization, and it's only gotten faster anyway.

    3. Re:Firefox is slow by Computer+Guru · · Score: 0

      When did you try Opera? 1989? Middle-Click on links -> open in new tab Middle-Click on tab -> close that tab Middle-Click on page -> scroll with mouse Just like every other browser. Gimme a break.

    4. Re:Firefox is slow by hardcampa · · Score: 0

      Well Mr Firefox fanboy, you should be able to spot the difference immediately if you just do what I said. Time the time it takes for FF to start compared to opera. Open tons os webpages and compare their speeds. Run them for a long time and compare crashes... I can't do it for you

    5. Re:Firefox is slow by Anonymous Coward · · Score: 0

      oops yeah -- it's the lack of middleclicking on UI elements (homepage button, history list, ...) that was annoying me.

      I'm not the Anonymous FF fanboy above, but I do find Firefox 2.0 a lot faster than Opera on most sites, like Slashdot (5-8sec in Opera vs. 1-2sec in Firefox). There was a webpage with speedcomparisons floating around the web a while ago which listed Opera as fastest - that's why I decided to give it a shot too - but can't say I came to the same conclusion, though that may just be due to the sites I visit (and the type of content/scripting on those pages).

    6. Re:Firefox is slow by Ash-Fox · · Score: 1
      The reality distortion field around him causes a temporal doppler effect with other browsers. For him, Firefox is the most fast.
      Open tons os webpages and compare their speeds. Run them for a long time and compare crashes... I can't do it for you
      I'd have to say I've not had Firefox 2 crash on me within the last... Uh, month maybe? Last time it crashed was intentional, by visiting a page (that I knew was) specially crafted to make Firefox crash.
      --
      Change is certain; progress is not obligatory.
  14. The source is a fucking mess! by Anonymous Coward · · Score: 4, Interesting

    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.

    1. Re:The source is a fucking mess! by Anonymous Coward · · Score: 2, Interesting

      I agree - the source is a giant freaking mess. (For real fun, look at the DOM code. It's a weird mix of XPCOM and JavaScript objects, all merged into one giant blob.)

      But the other reason trying to submit patches is a non-starter is that I've never actually seen them accept a third-party patch. I've seen patches submitted to bug reports plenty of times, but I've never seen one accepted. (I'm sure that after posting this someone will point to bug reports where third-party patches were accepted - but they're still dwarfed by rejected patches.)

    2. Re:The source is a fucking mess! by KingSkippus · · Score: 1, Insightful
      Their code is a mess, regardless of whether it's C++ code, or whether it's JavaScript code. Look for yourself

      *shrugs*

      Looks pretty good to me, and it seems to work pretty well. Is there anything in particular that you find messy?

      We hear that reasoning a lot from open source advocates.

      The reason I brought it up is because the author of the article implied that he has the skill to fix at least one of the bugs that he's complaining about. While I agree that he's under no obligation to do so if he doesn't want to, I also think it's extremely bad form to sit around complaining that no one else will.

    3. Re:The source is a fucking mess! by Anonymous Coward · · Score: 5, Informative

      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).

    4. Re:The source is a fucking mess! by Anonymous Coward · · Score: 5, Interesting

      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).

    5. Re:The source is a fucking mess! by Anonymous Coward · · Score: 1, Interesting

      This depends on how much of an egotistical moron the module owner is. Good module owners encourage devs and help them work patches into shape during review.

      The code and various API's could be leaner and cleaner but much of that was down to crappy C++ compiler support and the situation has improved. Hopefully Mozilla 2 will have a much cleaner codebase.

    6. Re:The source is a fucking mess! by hahafaha · · Score: 2, Insightful

      First of all, it is not Mozilla's fault if the patches it receives are crap.

      Second, you can always recompile Firefox yourself and run a customized version. Or, better yet, write an extension!

    7. Re:The source is a fucking mess! by mccoma · · Score: 1

      but don't call it Firefox (gotta love TM law and policies generated from it)

    8. Re:The source is a fucking mess! by MrDrBob · · Score: 3, Insightful

      I don't follow the project closely enough to know why the quality of their code is so low

      I would not agree with that at all. A not insignificant amount of the code is a mess, yes, but it's not low-quality. Being a mess never implies low quality, it just means that a decade or so of cruft has built up. There are several ongoing efforts at the moment to clean up Gecko, with the reflow branch being a major one.

      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.

      As has been discussed on Slashdot before, I'm sure you know that any large and complex project will suffer memory leaks and security holes until they're all plugged. (That's not to say this is good, though. :-P ) If you try to abstract away all the possible causes of such annoyances so that they cannot happen, you just end up with bloated and slow code, which nobody wants. I would agree that the messier parts of Gecko's codebase may contribute more to memory leaks and security holes, but they're also (coincidentally) the bits which are the oldest, and therefore have had the most time to be hacked into shape.

    9. Re:The source is a fucking mess! by daviddennis · · Score: 5, Insightful

      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

    10. Re:The source is a fucking mess! by Anonymous Coward · · Score: 0
      Commenting on the JS article on your blog because commenting is disabled there. You should create a stringBuffer class that does '+' style concat for NS and uses array elements for MSIE. A google search will throw up several examples. Generally the '+' operator is faster in spidermonkey but not (so I'm told) MSIE.


      Love the fixed background on your site :-)

    11. Re:The source is a fucking mess! by beuges · · Score: 1

      Why, does Mozilla have a policy of allowing anyone to commit patches without approval?

      If the patches received are crap, then the people who are in charge of receiving the patches and committing them should reject them, or pass them on to a 'de-crappifying' team who can look at the patch and rework it in a non-crappy manner.

      If crap patches get automatically committed and added to the code base, and no-one at Mozilla thinks this is a bad idea, then I'd agree... Firefox is most definitely losing its way.

    12. Re:The source is a fucking mess! by rudy_wayne · · Score: 4, Interesting

      "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."

      Exactly the problem with the "if you don't like it, fix it yourself" answer.

      The particular source code you are looking for (rendering pages or putting up menus or toolbars) is located in some directory whose name makes no sense except to the person who originally created it. You probably looked in the directory called "Browser", but, as someone who used to build my own customized versions of Firefox, I can tell you -- it ain't there.

      Unfortunately it's been over a year since I worked with the code so I don't remember where things are anymore and have no desire to go thru the whole process of finding them again.

    13. Re:The source is a fucking mess! by beuges · · Score: 4, Insightful

      "A not insignificant amount of the code is a mess, yes, but it's not low-quality"

      Maintainability is an extremely important aspect of development. If the code is a mess, then it is not high-quality code.

      "Being a mess never implies low quality, it just means that a decade or so of cruft has built up."

      Being a mess implies that it is difficult to maintain, which implies that it is of poor quality. The proper way to develop is to refactor during development, so that you don't accumulate cruft or messiness. I'd say that cruft by definition implies low-quality code.
      A very important aspect of development is design. A proper design phase for new features/code will also include looking at the existing design and how the new stuff can fit into it. You don't just go and tack your new feature on the end of what you already have, or you end up with unmaintainable, messy, cruft. You look at what you want to do, and you evolve the existing design to make the new code integrate into it, rather than be tacked on with sticky tape.

    14. Re:The source is a fucking mess! by chromozone · · Score: 1

      I uses Firefox a lot and like it. That said, I never understood why it hangs-up so easily in forums I go to. I often have to shut it down because it's hanging, and when I go to restart it I have to use the task manager first to shut it off from there because it will still be running despite having been shut down. I could list a lot of things I like about Firefox, and there aren't many I don't like, but for 2 years I have had to use the task manager to control this browser and it keeps me from recommending it to other people.

    15. Re:The source is a fucking mess! by William_Lee · · Score: 1
      As has been discussed on Slashdot before, I'm sure you know that any large and complex project will suffer memory leaks and security holes until they're all plugged. (That's not to say this is good, though. :-P ) If you try to abstract away all the possible causes of such annoyances so that they cannot happen, you just end up with bloated and slow code, which nobody wants. I would agree that the messier parts of Gecko's codebase may contribute more to memory leaks and security holes, but they're also (coincidentally) the bits which are the oldest, and therefore have had the most time to be hacked into shape.

      I think this is a cop out on the memory leak issue. The simple fact of the matter is that IE 6 & 7, and Opera 9 do not suffer from memory leaks anywhere near as badly as Firefox. I can't speak to the bloat, but Opera renders very quickly, and IE7 seems pretty fast also. Fixing sloppy memory leaks should be a top priority IMO.

    16. Re:The source is a fucking mess! by MrDrBob · · Score: 1

      Maintainability is an extremely important aspect of development. If the code is a mess, then it is not high-quality code.

      I would agree with that, although I wouldn't say that (!high-quality) == low-quality. However, as far as I'm aware, the messy parts of Gecko are the ones nobody really needs to touch very often, and hence they don't have to be maintainable (although it's nice).

      I'd say that cruft by definition implies low-quality code.

      I would disagree there. Cruft doesn't have to be low-quality, and neither does the code that surrounds it. Cruft is just code which has lost its way. :-P

    17. Re:The source is a fucking mess! by MrDrBob · · Score: 1

      I think this is a cop out on the memory leak issue. The simple fact of the matter is that IE 6 & 7, and Opera 9 do not suffer from memory leaks anywhere near as badly as Firefox. I can't speak to the bloat, but Opera renders very quickly, and IE7 seems pretty fast also. Fixing sloppy memory leaks should be a top priority IMO.

      (Just to point out, I'm not from Mozilla, and I haven't worked on Firefox for quite a while, although I used to triage bugs.)

      It could be taken as a cop-out, yes, and memory leaks are not excusable, but I think your argument is slightly off as well. IE 6 had bad memory leaks (for example, the nasty one where it wouldn't release the memory for event handlers). I don't know about IE 7 or Opera though. If fixing memory leaks was a top priority, Firefox would not be the browser it is today. Fine, it wouldn't leak memory, but since all the commonly-encountered ones (afaik) have been fixed, dev. time should be aimed at adding features where appropriate, and fixing other, more pressing bugs. Don't get me wrong – memory leaks should be fixed – but saying it should be a top priority is not the way to go about it.

    18. Re:The source is a fucking mess! by MrDrBob · · Score: 5, Informative

      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. :-)

    19. Re:The source is a fucking mess! by xTantrum · · Score: 1
      I think this thread started by the op is absolutely correct. IMHO this is a reason why a language such as python is recommended (obviously if there wasn't the speed issue involved). C and C++ lends itself to all manner of abuse and abstractions only the original developer can usally figure out.

      It doesn't even have to be a huge project. Take a look at some old C code you wrote maybe a year or even sevreal months ago - assuming its not a simple hello world app - and you'll realise that sometimes it takes you a while to figure out just what it is you did.

      The objects you created, certain ADT and algorithms - it can be overwhelming and a mess. I'm not trolling, nor am i intiating a redundant language war - i'm a die hard C and python coder - just saying this is why a elegant syntax and structured language like python would be preferabale when working on a huge project such as firefox. its so easy to get up and running perusing other ppls python code. my .02

      --
      $action = empty(PHP) ? backToC() : unset(PHP) ; "when the concrete cases are understood, the abstractions are readily
    20. Re:The source is a fucking mess! by bunratty · · Score: 1
      The simple fact of the matter is that IE 6 & 7, and Opera 9 do not suffer from memory leaks anywhere near as badly as Firefox.
      Then why don't you point out one of these Firefox memory leaks?
      --
      What a fool believes, he sees, no wise man has the power to reason away.
    21. Re:The source is a fucking mess! by daviddennis · · Score: 1

      Thanks for the tip! I find it interesting that another person who actually worked on it doesn't remember where it was, which makes me feel a bit better. Obviously I'm not alone.

      So I glanced through a bit of it and I don't see it as that confusing, but it seems to be all wrappers around wrappers and I'll bet finding a section of it that actually does anything, and tracing through all the layers would be a titanic migraine despite the slick HTML cross-referencing scheme.

      On the whole, then, I don't know if I'd call it bad, since I'm sure there are reasons why it would be written that way but difficult to work with seems like a given.

      D

    22. Re:The source is a fucking mess! by NickFortune · · Score: 2, Informative
      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/.
      It's not entirely fair to compare SeaMonkey with Firefox. One of the drivers factors behind the foundation of Firefox (then Phoenix) was that the Mozilla inherited from Netscape was borked beyond redemption, and recoding from scratch was the only way forward.

      SeaMonkey, whose repository you linked to. is a continuation of the old Mozilla codebase. It was brought back from the dead after the mozilla project decided to junk it. Part of the reason for that was that a few old fossils like myself have a certain affection for the mozilla suite, but mainly it happened because a ot of corporate players had a significant investment in the old Mozilla package, and since this is open source they don't have to migrate if they don't want to.

      The tone you take in your post leads me to suppose that you should have known all this already. I'll just add that if you want people to take you seriously (as opposed to just another AC astroturfing for Microsoft) then you should at least link to the correct repository. Don't you think?

      --
      Don't let THEM immanentize the Eschaton!
    23. Re:The source is a fucking mess! by Bert64 · · Score: 1

      Which forums? I've never had such issues, firefox seems pretty solid for me..

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    24. Re:The source is a fucking mess! by h4rm0ny · · Score: 1


      I've never looked at the source code and I don't know if it's a mess or not. But anyone that says code being a mess doesn't mean it isn't high-quality doesn't know what they're talking about.

      --

      Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
    25. Re:The source is a fucking mess! by Anonymous Coward · · Score: 1, Informative

      Uhm, although the OP is a troll, he did link to the correct repository. The SeaMonkey specific code is in the /suite and /xpfe directories underneath that starting dir, same as Firefox has it under /browser and thunderbird under /mail (and then both under /toolkit) - pretty much everything else there is core code used by all projects. Firefox was not "recoded from scratch" - it got a slightly simplified and cleaned up UI-library (toolkit) and lots of general overhaul of the UI - but it's 90% same code.

      As for corporate players helping with the revival of SeaMonkey... Heh, if only! At present it's mostly half a dozen volunteer developers, and maybe a dozen people doing QA and general small tasks that's keeping it alive. If any corporate player likes what these people are doing though, they'd be more than welcome to hire someone to work on it fulltime. :)

    26. Re:The source is a fucking mess! by osu-neko · · Score: 4, Insightful

      Bull. People who write hard to figure out code do so with pretty much equal ease in any language. People who write easy to read and maintain code again do so pretty much equally well in any language. Reason being, the skills used to write maintainable code have nothing at all whatsoever to do with the programming language. "Elegant syntax" of the language? Gimme a break. Elegant code is elegant code, regardless of the language syntax. Elegance has do to with the underlying idea expressed, not the syntax of the language.

      Oh, and Python has lousy syntax, but that's just a personal opinion on my part, not in any way an objective fact. My personal preferences on syntax don't apply to anyone but me. Nor do yours.

      --
      "Convictions are more dangerous enemies of truth than lies."
    27. Re:The source is a fucking mess! by unix_core · · Score: 1

      If the patches received are crap, then the people who are in charge of receiving the patches and committing them should reject them, or pass them on to a 'de-crappifying' team who can look at the patch and rework it in a non-crappy manner.

      Great, except for the fact that it would probably take away the whole point of people submitting patches if you still need other people to rewrite them.

    28. Re:The source is a fucking mess! by mccoma · · Score: 1

      I was thinking the security patch / fix a bug / make it work route. For the most part, the groups actually changing features have used a different name (e.g. Camino). I have no problem with different feature sets needing a new name, but I am little wary of slow uptake on patches needed to get stuff working on other environments. I kinda wish Mozilla had developed a scheme for naming that would have prevented the need for Ice Weasel.

    29. Re:The source is a fucking mess! by mortonda · · Score: 1

      I looked through the source he linked to and I couldn't find a single C file

      Maybe you should be looking for cpp files? I thought about rendering pages, and decided to go to layout and the base, which has a bunch of rendering files for you.

      http://lxr.mozilla.org/seamonkey/source/layout/bas e/

      The code is right there, doesn't look too bad. I can't tell you what it does just yet, but with any large project, it takes a little while to become acclimated to the code.

      I've never looked at this code before, and I was instantly able to find whatever functions I was looking for, and I think I could even debug it given some time to look things over. It actually looks fairly good.

    30. Re:The source is a fucking mess! by swimmar132 · · Score: 1

      I can write an object / class factory in Ruby in a couple lines of code. Doing the same in C++ would be a couple hundred (or more) lines of template monstrosity. And the concept doesn't make sense in C.

      Sometimes, the language does dictate what you can and can't elegantly do.

    31. Re:The source is a fucking mess! by Coryoth · · Score: 1

      May I suggest to look at Ada and Eiffel - both offer elegant and consistent syntax that results in easy to maintain code, with the benefit that they compile to run as fast as C and C++.

    32. Re:The source is a fucking mess! by Anonymous Coward · · Score: 0

      A couple of years back, I complained about the way certificates are handled (its in bugzilla), and proposed a patch to the way it automatically selected certificates for sites where multiple certificates were relevant. The patch was pretty much ignored with no comment. This does not exactly encourage me to write patches for other things that annoys me in the browser.

    33. Re:The source is a fucking mess! by coaxial · · Score: 1

      The reason I brought it up is because the author of the article implied that he has the skill to fix at least one of the bugs that he's complaining about. While I agree that he's under no obligation to do so if he doesn't want to, I also think it's extremely bad form to sit around complaining that no one else will.

      As if he doesn't have better things to do. The great thing of sophmoric refrain of "Use the source! Fix it yourself" is the shear arrogance of it. It's, "Why don't you drop everything, and do my job for me." Why is it your job? Because you're the maintainer. You're the developer. You chose that role, and now that someone is depending on you, you tell them screw off. Now that's "bad form" buddy.

    34. Re:The source is a fucking mess! by toddbu · · Score: 1

      Not true. If the person creating the patch has identified both the problem and a solution, cleaning up the code is easy. I think that far too many bugs never see the light of day because nobody is willing to verify the bug, let alone identify a solution.

      --
      If you don't want crime to pay, let the government run it.
    35. Re:The source is a fucking mess! by Shawn+is+an+Asshole · · Score: 4, Interesting

      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.

      However, if you really want to see a codebase that's an absolute mess, download the source to OpenOffice. Same as with Mozilla, the developers are making progress on cleaning it up, but it's still a total mess.

      --
      "It ain't a war against drugs.it's a war against personal freedom" --Bill Hicks
    36. Re:The source is a fucking mess! by NickFortune · · Score: 1
      The SeaMonkey specific code is in the /suite and /xpfe directories underneath that starting dir, same as Firefox has it under /browser and thunderbird under /mail (and then both under /toolkit) - pretty much everything else there is core code used by all projects.

      Then why not link to the correct repository? Then there's no doubt. As it is we have to wonder about motivation.

      Firefox was not "recoded from scratch" - it got a slightly simplified and cleaned up UI-library (toolkit) and lots of general overhaul of the UI - but it's 90% same code.

      mmmm.... the UI was recoded from scratch - it was redefined in terms of XUL which meant the entire interface was rendered by Gecko. Gecko wasn't rewritten from scratch of course. Apologies for any imprecision. Of course, if the OP had linked to Firefox/Gecko I'd have taken more care.

      As for corporate players helping with the revival of SeaMonkey.
      Don't think I said "helping". I just remember a lot of complaints at the time along the lines of "my company has a lot of apps that depend on the Mozilla suite and we need security updates at the very least". It's a little disappointing to learn that none of them have followed that up with any sponsorship.
      --
      Don't let THEM immanentize the Eschaton!
    37. Re:The source is a fucking mess! by daviddennis · · Score: 1

      As others have done, I went instantly to the section labelled "Browser", figuring it would contain, well, the browser, and ran into a whole collection of JavaScript files used for skinning and the like.

      I have subsequently been straightened out by people who replied to my message earlier. It would appear that plenty of people who have seen the structure found it as baffling as I did, so I don't feel too bad.

      D

    38. Re:The source is a fucking mess! by Droid+Rot · · Score: 0

      I wonder what Microsoft's coding for IE7 looks like?

      I guess we'll never know!

    39. Re:The source is a fucking mess! by William_Lee · · Score: 1
      Then why don't you point out one of these Firefox memory leaks?

      Because frankly, I'm not very adept at serious programming, and don't know where in the code they're occuring. All I know is that when I have FF open with a lot of tabs, and leave it running, it consumes more and more ram as the day(s) go by, even without extensions. I don't see this behavior in Opera, or on my machine on IE 7.

      FF 2.0 seems to be an improvement over 1.5 in this area, but it is still a serious issue.

      I'm not the only one who has experienced this behavior, and I'm sure many others have pointed out the memory leaks.

      I still use FF, and am a big supporter of open source software. That doesn't mean that I shouldn't feel able to point out a serious issue that needs to be addressed in later updates, and that is well known, and documented.

    40. Re:The source is a fucking mess! by Marcus+Green · · Score: 1

      Is it any better than the source to IE?. Oh I forgot, we can't look at that so we cannot compare.

    41. Re:The source is a fucking mess! by ralphdaugherty · · Score: 1

      ...but for 2 years I have had to use the task manager to control this browser and it keeps me from recommending it to other people.

            and version 2.0 continues to do this?

        rd

    42. Re:The source is a fucking mess! by Anonymous Coward · · Score: 0

      I write object oriented code all the time in C. Object oriented C is my primary language. I find languages that force you into a single object model to be be awkward and stifling.

      The great thing about C object code over C++ object code is that the private interface is actually private and your .h file has only public items in it. Having only the public interface public means that you can much more easily change the internal workings of the code module and add and remove private members of the class without having to recompile hundreds of other code modules just because you changed a single private variable name and now everything that includes that .h file needs recompiled.

      This provides inheritance by wrapping an old class in a new class, Encapsulation by providing opaque interfaces to the data, Data Abstraction by providing a clean object interface to the data, and Polymophism is handled by creating a message dispatch to the appropriate objects function call in the base class, clean .h files with complete info on every function, and much faster modify, compile, link times than C++ when the private areas of an object are modified.

      Of course C has a flat namespace and no "this" concept, so you can't call functions off the name of the variable, and have this set for you.

      double myarea = circle.area();

      is written

      double myarea = circle_area(circle);

      or if you have implemented some code to handle figuring out which object you are passing in and then calling the appropriate function then you can perform message dispatch to handle polymophism like this:

      double myarea = area(circle);

      and then the area function will dispatch the message to the object area function.

      So it's actually pretty much the same.

      I would love to see just a couple of extensions added to C to support hierarchical name spaces, and mapping of a "this" variable for a function call, but just because that would be cool and useful for many other things than classes. Just a little syntactic sugar and C would be perfect for object oriented design.

      I had one boss that loved to have complete access to all data everywhere in a program and he constantly complained about the modules that I wrote only provided opaque data pointers, and the only time those pointers were valid data structures were inside my own code modules, everywhere else they were completely and totally opaque.

      One time he came to me and asked me why he couldn't see the data inside of one of my buffer classes over in a completely different module. I told him if he wanted to see what was in the buffer, put a break point in the buffer module, because that was the only time that the data was valid, was when it was being handled by the code that handled that data. I told him that if he could access the data anywhere else, then he would access the data directly everywhere else and that is a Bad Thing (TM).

      He was used to writing a code module and then using the raw data structure everywhere in our massive code base, making modifying that code module a horrifying adventure in bug fixing and tracking down just lovely side effects in 100's of code modules. Not to mention having to completely recompile the entire program just because I added a single new element to a data structure in one .h file. *shudders*

      90% of my job there was refactoring the code so that the code modules had interfaces and hid the data structures. My method of doing this was simple. Refactor the module, rewrite the .h file so that it only contained function calls for the new class. Attempt to compile the project and begin fixing every place I just broke by hiding the data structure. As I went along I would have to pull code that dealt with data handling of the object from random far flung places in the code base to only in that one code module. Typically this resulted in much higher code quality, all the code dealing with a data structure in one place, and a reduction in bugs and line count by the time I was done.

    43. Re:The source is a fucking mess! by Brandybuck · · Score: 1

      Doing the same in C++ would be a couple hundred (or more) lines of template monstrosity.

      Huh? I can write an oject factory in three lines:

      MyClass *MyClass::factory() {
              return new MyClass();
      }

      --
      Don't blame me, I didn't vote for either of them!
    44. Re:The source is a fucking mess! by hao2lian · · Score: 1

      > Why, does Mozilla have a policy of allowing anyone to commit patches without approval?
      > If crap patches get automatically committed and added to the code base, and no-one at Mozilla thinks this is a bad idea...

      Nothing like this happens. All patches are reviewed and super-reviewed. And then only people with CVS access can check in that patch. You can verify this by looking at all the r= and sr= marks on Bonsai.

      --
      Pelé!
    45. Re:The source is a fucking mess! by hao2lian · · Score: 1

      > Look for yourself: http://lxr.mozilla.org/seamonkey/source/.

      You just linked to the source code of an entire web browser and called it "a mess." If broad generalization warning lights don't flash now, we really should change the batteries. What code file do you think is a mess? As someone who's seen a lot of code review, patches get thoroughly reviewed and nitpicked (for indentation, spacing, line breaks, variable naming, you name it). To suggest the codebase went down the toilet between the 1.5 and 2.0 release is a preposterous argument.

      > 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...

      Which programmers? Do you have names? Or is it just "most" of them? I've seen plenty of small bugs that were minor changes in an XML or JS file somewhere that weren't difficult to understand at all. And, yes, implementing a new feature in a mature web browser project is hard. This shouldn't be news to anybody.

      --
      Pelé!
    46. Re:The source is a fucking mess! by Sigma+7 · · Score: 1
      Huh? I can write an oject factory in three lines:

      MyClass *MyClass::factory() {
                      return new MyClass();
      }


      Technically, that is a basic class factory.

      However, you need a constructor - otherwise the fields within the new MyClass() would most likely be undefined (or perceived to be undefined, since the new operator is an offshoot of the malloc function). This adds a few more lines to the code.

      It's not as much of a problem if you stick with C++ classes, but primitives generally need to be initialized - including pointers that is required if you have a circular class dependancy. (e.g. class world contains vector, and class thing wants to know which class world it's contained in.)

    47. Re:The source is a fucking mess! by thealsir · · Score: 4, Interesting

      I'm running firefox 2.0 with a rather minimal set of extensions. Let me tell you, does it leak. I have 1GB of RAM, and, left open long enough (say, three or four days) the system starts slowing down dramatically, and firefox starts not responding that well, UI starts not painting right, etc. I wonder what the heck is going on.

      Then I go into task manager to find firefox consuming 900MB of RAM with tons put in the page file.

      NO OTHER application I have ever used does it to this extreme, and while I'm sure IE has some not so good memory leaks, in my years of using IE that has NEVER happened to me.

      --
      Do not downmod posts "overrated" simply because you disagree with them.
    48. Re:The source is a fucking mess! by Sigma+7 · · Score: 1
      Because frankly, I'm not very adept at serious programming, and don't know where in the code they're occuring. All I know is that when I have FF open with a lot of tabs, and leave it running, it consumes more and more ram as the day(s) go by, even without extensions. I don't see this behavior in Opera, or on my machine on IE 7.


      Write a memory leak detector - even if you are an amateur programmer, you need to have one in your portfolio or otherwise know how to deploy one.

      This is the exact same method I used to suppliment the MSVC 6.0 memory leak detector - since it wasn't properly giving the line and filename of the affected source file in question, I patched the malloc() function and new operator to correct the filename and line number for allocated memory.

      From there, you can instantly detect the line number and filename for the memory leak - and submit a bug report stating that this line is causing a leak. It won't detect memory inefficiencies, such as holding onto a cached page much longer than it should, but it will find the issue you claim is present. Of course, most Mozilla developers know how to find these memory leaks as well.
    49. Re:The source is a fucking mess! by jamiecook · · Score: 1

      MOD PARENT UP!!

    50. Re:The source is a fucking mess! by Anonymous Coward · · Score: 2, Insightful

      "Is it any better than the source to IE?"

      Even if it is better than IE, is it really enough to simply not be as bad as your competitor? Not writing professional code just because the other guy doesn't bother is silly. Proper code is easier to maintain and makes a better platform for future development. Further, it's easier to add new developers and include third party patches.

    51. Re:The source is a fucking mess! by fluffy99 · · Score: 1

      Besides, the likelyhood of the Mozilla developers accepting code fixes from an unknown person is pretty close to zero as it should be. Would you really blindly trust someone submitting revised code to fix a bug, or would you rather someone identify the problem and let you fix it yourself. This is one of the fundamental perceived flaws of open-source software - the lack of accountability.

    52. Re:The source is a fucking mess! by HeroreV · · Score: 1

      That isn't skinning. The stuff that is actually SeaMonkey consists of JavaScript, XUL, and CSS. Firefox is the same way. All the heavy lifting is done by a bunch of XPCOM components that are accessed through JavaScript bindings.

    53. Re:The source is a fucking mess! by bunratty · · Score: 1
      That doesn't mean that I shouldn't feel able to point out a serious issue that needs to be addressed in later updates, and that is well known, and documented.
      However, it isn't "well known, and documented" because no one can point out a single one of these "horrendous memory leaks". I have to conclude those people still talking about them just don't have a clue what they're referring to.
      --
      What a fool believes, he sees, no wise man has the power to reason away.
    54. Re:The source is a fucking mess! by HeroreV · · Score: 1

      You've got your history screwed up really badly. The Mozilla Organization inherited what would have been Netscape 5. That is what they decided to scrap. They then began a browser that became Netscape 6 and the Mozilla suite (codenamed SeaMonkey). Both Netscape 6 and the suite defined their interfaces with XUL. The Mozilla suite was not based on the code inherited from Netscape.

      Phoenix/Firebird/Firefox was started because many people felt the Mozilla suite was suffering from major feature creep. It had nothing to do with the code inherited from Netscape. Firefox was not coded from scratch; it is basically the suite with the non-browser stuff stripped away. Firefox and the suite share a lot of code.

    55. Re:The source is a fucking mess! by chromozone · · Score: 1

      Yes it does. I go to a couple of forums that get hit with a lot of people in the evening hours. The worst forum for the hanging effect runs dotNetBB v2.42EC SP3. Its a teen psychology in the UK site that get a million hits every couple days. Needing to use the task manager doesn't happen often. Maybe once a week I click the firfox shortcut and nothing happens. I can click several more times and nothing happens. If I then open the task manager I can see Firefox listed under "proceses". If I shut if off in task manager I will then be able to open Firefox using shortcut. I don't think the task manger issue is related to the forum.

    56. Re:The source is a fucking mess! by Anonymous+Brave+Guy · · Score: 1

      People who write hard to figure out code do so with pretty much equal ease in any language.

      Except Perl. It's much easier in Perl. :-)

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    57. Re:The source is a fucking mess! by gordgekko · · Score: 1

      I have this same problem with Firefox 2.0 on multiple machines. It just decides to hang and I get to wait until it resumes operating. That never happened with FF 1.5.

      --
      You want to know who isn't running Firefox 2.x? They spell it "definately" and "rediculous".
    58. Re:The source is a fucking mess! by William_Lee · · Score: 1
      However, it isn't "well known, and documented" because no one can point out a single one of these "horrendous memory leaks". I have to conclude those people still talking about them just don't have a clue what they're referring to.

      Yeah, we're all imagining that with multiple tabs open, leaving FF running for days results in growing amount of RAM usage, eventually bogging down the entire system, even with 2 gigs of RAM under XP.

      Maybe your type of attitude is the reason FF still has the problem...I guess anyone who experiences it doesn't have a clue because you don't want it to exist.

      All I know is it happens, and the only offending application on my system at the time is FF. Maybe you should get a clue...

    59. Re:The source is a fucking mess! by BenoitRen · · Score: 1
      It's not entirely fair to compare SeaMonkey with Firefox.

      He doesn't compare. The link he gave gives you the source code of the trunk of the project. All projects can be found there.

      The seamonkey directory is named like that because it was the code name of the Mozilla suite, which was the flagship product of Mozilla in the beginning.

      One of the drivers factors behind the foundation of Firefox (then Phoenix) was that the Mozilla inherited from Netscape was borked beyond redemption, and recoding from scratch was the only way forward.

      The rewriting from scratch has nothing to do with Firefox. The source code Netscape released was indeed a big mess, and Mozilla then rewrote it from scratch. This rewrite is what was used for all their Mozilla projects. Firefox is not the rewrite.

      Firefox is a project that was born around the year 2000 from a couple teenagers who didn't like the review process and the approach the suite took, so they forked the interface code and started on Phoenix, which was designed to only be a browser with the end user in mind.

      SeaMonkey, whose repository you linked to. is a continuation of the old Mozilla codebase. It was brought back from the dead after the mozilla project decided to junk it.

      It's a continuation of the suite interface code, but not the old Netscape source code that was released.

    60. Re:The source is a fucking mess! by Anonymous Coward · · Score: 0

      You stupid fucker. He did link to the correct repository! The Firefox and Seamonkey code is stored in the same goddamn repository!

      Firefox builds upon the Gecko rendering engine, just as Seamonkey does. So to only link to just the browser/ directory would be a mistake. If you're looking there, you're only considering a small portion of what makes up the product we call "Firefox".

      Honestly, you've just made a disgrace of yourself. I hope any future employer of yours sees that post of yours, just so they know how technologically inept you truly are.

    61. Re:The source is a fucking mess! by rossifer · · Score: 1
      The simple fact of the matter is that IE 6 & 7, and Opera 9 do not suffer from memory leaks anywhere near as badly as Firefox.
      Then why don't you point out one of these Firefox memory leaks?
      The memory leaks in Firefox are fairly easy to reproduce, so I'll assume you're not asking him to do that and are instead asking him to find in code or actually fix the leaks.

      The reason he doesn't point to the problematic line(s) of code: memory leaks are among the hardest kinds of problems to isolate, let alone debug, even for original authors of recent code with the proper tools. They're usually a symptom of the right hand not knowing what the left hand is doing (which one way of saying there was inadequate communication during design). Which tells me something important about Firefox.

      Regards,
      Ross
    62. Re:The source is a fucking mess! by mmclean · · Score: 1

      % cd
      % grep -ir main .

    63. Re:The source is a fucking mess! by maxume · · Score: 1

      From http://lxr.mozilla.org/ :

      "SeaMonkey (updated hourly)
              This module is SeaMonkeyAll, the trunk of the Mozilla browser project."

      So really, it is the firefox codebase. Seamonkey lives here:

      http://lxr.mozilla.org/seamonkey/source/suite/

      while firefox lives in the similar, but different:

      http://lxr.mozilla.org/seamonkey/source/browser/

      Ooops.

      --
      Nerd rage is the funniest rage.
    64. Re:The source is a fucking mess! by Anonymous Coward · · Score: 0

      And what are the non-techies supposed to do? I thought that Firefox was supposed to be "the new thing," and get the attention of the general public. How is it supposed to do that, if people download it and find that it slows their computer to a crawl? You don't have to be a techie to know that you're computer is going slow, but there's a hell of a lot of people who don't know how to go about detecting memory leaks... and more still who don't even know how to report bugs (or even know what the word 'bug' means).

      Bottom line: Firefox is a hog. I don't use any extensions, and it's using up (easy) about 128MB RAM with 5-10 tabs open. That's a problem.

    65. Re:The source is a fucking mess! by NateTech · · Score: 1

      Actually the Linux distros *ALREADY* do this. They all call themselves "Linux". Then your non-tech friends call up and say, "I can't get my Linux box to do X."

      It's already a nightmare.

      --
      +++OK ATH
    66. Re:The source is a fucking mess! by Blink+Tag · · Score: 2, Insightful

      You may be right, but one data point does not make a trend. Even on Slashdot.

    67. Re:The source is a fucking mess! by Brandybuck · · Score: 1

      Irrelevant. The grandparent post said "doing the same in C++ would be a couple hundred (or more) lines of template monstrosity." But even with a non-default constructor and explicit initialization of members, you're STILL not going to get "a couple hundred (or more) lines of template monstrosity."

      --
      Don't blame me, I didn't vote for either of them!
    68. Re:The source is a fucking mess! by misleb · · Score: 3, Insightful

      Well, one data point beats a baseless assertion. At least that is what my Slashdot rulebook says.

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    69. Re:The source is a fucking mess! by Anonymous Coward · · Score: 1, Interesting

      I realize there are memory leaks. I too keep FF open for extended periods.
      I use Tab Mix Plus and it can save sessions.
      So if FF starts to hog memory, I save the session, close FF then reopen the session.

      Not perfect, but...

    70. Re:The source is a fucking mess! by Anonymous Coward · · Score: 0

      > I use Tab Mix Plus and it can save sessions.

      If you don't have Tab Mix Plus a dirty work-around is to bookmark the open tabs in a "Trash" folder. Restart browser and open the bookmarked tabs again. Periodically I just delete everything in the Trash folder.
      Frankly, session saving should be a built-in default option for any browser these days (though FF does session recovery in case it crashes).

    71. Re:The source is a fucking mess! by biglig2 · · Score: 1

      Ahem: Last time I checked, Firefox was still open source software. If the code is a mess, by all means, download the source and fix it yourself.

      --
      ~~~~~ BigLig2? You mean there's another one of me?
    72. Re:The source is a fucking mess! by NickFortune · · Score: 2, Interesting
      So really, it is the firefox codebase. Seamonkey lives here:
      http://lxr.mozilla.org/seamonkey/source/suite/
      while firefox lives in the similar, but different:
      http://lxr.mozilla.org/seamonkey/source/browser/
      Riiight, gotcha. So the repository is named seamonkey after the old codename and not because it's only for the Seamonkey project.
      My mistake then. I should know better than to post after I've had a few drinks
      --
      Don't let THEM immanentize the Eschaton!
    73. Re:The source is a fucking mess! by pronik · · Score: 1

      That's not correct. The whole Netscape codebase had been dumped back in 1998. Then a new rendering engine called Gecko has been developed, together with several other pieces of infrastructure - this has become the foundation of Mozilla. Firefox is just an implementation of a browser using XUL - as opposed to Mozilla Suite or Seamonkey, which are implementation of Netscape's app design in XUL. Seamonkey and Firefox share a lot of code, both are based on current Gecko, so the difference is really bundling several applications together or not.

    74. Re:The source is a fucking mess! by AutumnLeaf · · Score: 1

      Elegance has do to with the underlying idea expressed, not the syntax of the language.I think there are two types of elegance.

      There's the elegance of a solution to a problem. That is, the algorithm.
      And then there is the elegance of the implementation of an algorithm.

      Give two programmers an elegent algorithm to implement in a given language, and there's a chance one of them will find a way to express the solution in the syntax of the language in a beautiful way, whereas the other one won't.

      It struck me while reading this thread you and the person you were talking to may not have been talking about the same sort of elegance.

    75. Re:The source is a fucking mess! by NickFortune · · Score: 1

      That's right, get it out of your system. You'll feel better for it afterwards.

      --
      Don't let THEM immanentize the Eschaton!
    76. Re:The source is a fucking mess! by Anonymous Coward · · Score: 0

      Don't blame your stupidity on being "drunk". We all know your daddy would spank your ass red if you got into his Jack. You're just a fucking moron. It's as simple as that.

    77. Re:The source is a fucking mess! by namekuseijin · · Score: 1

      "Their code is a mess"

      any large codebase is a mess, especially ones written in ancient hierogliphic low-level imperative ideograms like C/C++. Just ask Windows Vista developers why it took so long...

      the only good thing about proprietary software is that you are never able to see the horror yourself, since the code is closed...

      --
      I don't feel like it...
    78. Re:The source is a fucking mess! by mariushm · · Score: 1

      Then how about closing the f@#ing Firefox once every six hours ? Is that so damn hard ? Seriously now, I'm using only Firefox and I close it even without realizing at least once every couple of hours. My uptime is usually 10-20 days. If you don't want to lose the open tabs go to Tools > Options and select: When Firefox starts : Show my windows and tabs from last time

    79. Re:The source is a fucking mess! by Sigma+7 · · Score: 1
      Irrelevant. The grandparent post said "doing the same in C++ would be a couple hundred (or more) lines of template monstrosity."


      Which can and will happen if you need multiple classes.

      Programming languages are supposed to be designed as efficiently as possible (within a reasonable scope). You should not have to worry about having to type more than you have to - for example, it would be nice to explicitly declare fields like so:


      class thing
      {
            int value = 5;
      };


      Rather than having to type value twice to initialize it.

      But even with a non-default constructor and explicit initialization of members, you're STILL not going to get "a couple hundred (or more) lines of template monstrosity."


      That is correct. However, C++ is one of the languages where this is easily possible, which can happen if a class should receive an excessivly large number of variables. Granted, you want to check the design, but it's still harder to maintain than other languages such as Java.

      The only advantage of not auto-initializing the variables is a slight performance boost.
    80. Re:The source is a fucking mess! by Killjoy_NL · · Score: 1

      My god, take a chillpill, no need to get all angry about a piece of software or a weblink.

      --
      This is the sig that says NI (again)
    81. Re:The source is a fucking mess! by NickFortune · · Score: 1
      You're just a fucking moron.

      How fortunate we are that Slashdot has such remarkable intellects as your own to exemplify the opposite extreme.

      --
      Don't let THEM immanentize the Eschaton!
    82. Re:The source is a fucking mess! by maxume · · Score: 1

      I was replying for the taking-you-seriously irony more than the factual inaccuracy.

      --
      Nerd rage is the funniest rage.
    83. Re:The source is a fucking mess! by Fnkmaster · · Score: 1

      Funny, this happened frequently with FF 1.0 and 1.5 for me, but seems much less of a problem with FF 2.0, which fixed most of the worst, most repeatable memory leak issues for me. I'm not saying it's flawless, but I've never seen 900MB of RAM usage by Firefox 2.0.

    84. Re:The source is a fucking mess! by DrRotwang · · Score: 1

      "Being a mess never implies low quality" Ladies, gentlment, slash-doters. I point your attention at that absurd statement. And rarely do I uses this phrase, but I use it now: "nuff said".

    85. Re:The source is a fucking mess! by NickFortune · · Score: 1

      Yeah, I got that, but I found the comment helpful anyway.

      --
      Don't let THEM immanentize the Eschaton!
    86. Re:The source is a fucking mess! by Risen888 · · Score: 1

      My god, they're trotting this old whore out.

      Listen, I hear this repeated on Slashdot about twenty times in any conversation about any web browser. And I've never seen it in real life. I've got a copy of FF2.0 running at home right now (I'm at work), it's been running for over a fucking week, and it's consuming maybe 120MB of RAM. Which is about 20MB more than when I open it. It'll be at 120 when I get home, it'll be at 120 next week.

      No, my single data point proves nothing, but neither does yours.

      --
      Hey, I finally got my first freak! Took you long enough!
    87. Re:The source is a fucking mess! by unix_core · · Score: 1

      Or simply clean up their own fucking code =)

    88. Re:The source is a fucking mess! by kobaz · · Score: 1

      I know this story is a bit old but I still had the tab open from a few days ago. My firefox 2.0 has actually been running for 14 days straight and it's currently using 500megs total allocated mem, 290megs physical and I have 55 tabs open. It's not exactly snappy but it's not too bad either. I wonder if IE could perform the same.

      --

      The goal of computer science is to build something that will last at least until we've finished building it.
  15. Re:JESUS FRACKING CHRIST by Anonymous Coward · · Score: 0

    And just what exactly is "frack" a contraction of?

  16. Firefox 2.0 is welcome on my 'puters by TimHunter · · Score: 1

    I've upgraded to 2.0 on all 3 of my PCs, one running Windows, another with Mandriva Linux, and my Powerbook. I usually use Safari on my Powerbook but I'll start Firefox 2.0 just to use its "Report Web Forgery" menu pick to report the web sites that come in the phishing emails I get every day. http://www.mozilla.com/en-US/firefox/phishing-prot ection/

  17. Let me break it down for you by Howzer · · Score: 5, Insightful

    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.

    1. Re:Let me break it down for you by Anonymous Coward · · Score: 0

      Use the strike tag next time. It reads like shit as it is.

    2. Re:Let me break it down for you by Anonymous Coward · · Score: 0

      Strike tag doesn't work on ./ - that's the first thing I tried, but thanks for your helpful and polite criticism anyway.

  18. Firefox not so terrible by ButteBlues · · Score: 1

    Firefox is a good browser. I personally refuse to use it, but I'm not afraid to admit that. I simply wish that Epiphany was compatible with Firefox extensions.

    --
    Yo.
    1. Re:Firefox not so terrible by ScrewMaster · · Score: 1

      Just out of curiosity ... why do you refuse to use it?

      --
      The higher the technology, the sharper that two-edged sword.
  19. The by Konster · · Score: 1, Troll

    The time between a critical flaw and a patch to fix it is too great. IE7 has been patched more than FF2.0, and this is not a good thing.

    There hasn't been a *single* patch to fix flaws in FF2. Not. A. Single. One.

    This isn't a troll, so please don't mode me down. When MS leads the way for browser security, things are very, very wrong for FF.

    I'm an XP user partly by choice, but when I seriously consider running FF2 under XP via a VM in Linux just to get some security, something is wrong.

    1. Re:The by tfreport · · Score: 1

      Are you seriously suggesting that the more patches a program gets, the safer it is? Should Mozilla have you download 2.0.0.1, 2.0.0.2, and 2.0.0.3 this week just so you feel safer without changes? Should they make changes if there are not serious flaws found? I ask because I am not understanding your logic - if you are truly not a troll as you claim.

  20. Re:IE7 by Anonymous Coward · · Score: 0
    IE7 has put the nail in it's coffin.

    IE7 hasn't even forund the graveyard. I don't use Firefox, but I do have to use IE7 and it sucks big time.

  21. Personally, I wish that they would fix the bug by Threni · · Score: 1

    Personally, I wish that they'd fix the bug that makes Firefox2 think that when you shut down Windows, and restart it 2 years later, it'll offer to `restart session`. Shutting down your pc should terminate Firefox, and end the session. I shouldn't have to shut down apps individually to avoid security problems (ie some guy 2 years down the line restarting firefox and being offered to `continue` my `session`...

    1. Re:Personally, I wish that they would fix the bug by weirdguy · · Score: 0, Troll

      Thats not a bug with firefox, it's the way windows shuts down programs when its shutting down that make it think its crashed.

    2. Re:Personally, I wish that they would fix the bug by Psykosys · · Score: 1

      But it's a lack of the very simple shutdown detection feature Firefox would need to solve the problem.

    3. Re:Personally, I wish that they would fix the bug by Anonymous Coward · · Score: 1, Informative

      What? Windows sends the same WM_QUERYSHUTDOWN and WM_SHUTDOWN messages to every application running. None of my other apps (with the exception of SpyBot's TeaTimer, another known bug) have a problem handling that. If Firefox is not handling it properly, that's not Windows fault, it's Firefox's.

      If what you say is true, many applications would have a problem shutting down properly when Windows shuts down, but they don't.

      All that said, I disagree that Firefox has "lost it's way" but that doesn't mean I don't think 2.0 was rushed out prematurely.

    4. Re:Personally, I wish that they would fix the bug by asills · · Score: 1

      Applications get a very distinct message indicating a shutdown of Windows. If the application doesn't handle said message and not turn off, Windows is forced to kill the program.

      If Firefox can't turn off in the required amount of time (Windows gives apps around 20 seconds or so to comply before killing them) or simply doesn't listen for the message, it would indeed be a bug.

      --
      -- What did Spock find in Kirk's toilet? The captain's log.
    5. Re:Personally, I wish that they would fix the bug by Threni · · Score: 1

      No, it's a bug in Firefox because I don't have problems with any other programs, and I never had, on Windows 2000, 98 or 95.

      How hard is it to get a `system shutting down - please quit` message from Windows and respond to it?

    6. Re:Personally, I wish that they would fix the bug by prandal · · Score: 1

      And some guy in two year's time would be using your profile and login? Get real!

      In about:config set browser.sessionstore.resume_from_crash to false.

      Simple.

      Solution found with a quick web search. You might like to try using a search engine before you mouth off next time.

    7. Re:Personally, I wish that they would fix the bug by jacksonj04 · · Score: 1

      It's still a bug though. Firefox thinks it's recovering from a crash when, in fact, the system was shut down correctly. Firefox *will* have received a notification from Windows to this effect and should damn well be able to close elegantly.

      --
      How many people can read hex if only you and dead people can read hex?
    8. Re:Personally, I wish that they would fix the bug by ralphdaugherty · · Score: 1

      Personally, I wish that they'd fix the bug that makes Firefox2 think that when you shut down Windows, and restart it 2 years later, it'll offer to `restart session`.

            That's not a bug, that's an advertised new feature.

        rd

    9. Re:Personally, I wish that they would fix the bug by mobilebuddha · · Score: 1

      but in this case, it's not a "crash".

      if it does what i think it does, then once this config setting is changed, if FF crashes, then it wouldn't restore the sessions that i was in. right? that's also not what i(and most users, i imagine) want.

      what we want is the following:
      1) during a shutdown/restart, FF should be aware and properly SHUTDOWN.
      2) after a crash, FF should retain its current functionality and offer the option to resume the sessions that it had.

      since FF is open source, i don't feel right about bitching. but if it was a commercial software, then i'd be wondering where the QA was on this one. you could've witnessed this if you restarted your computer ONCE.

      well, hope they fix it in a patch.

    10. Re:Personally, I wish that they would fix the bug by Threni · · Score: 1

      It's a bug if default behaviour is to be unsafe, when you'd never want a session to survive a deliberate reboot. If Firefox handled system shutdowns properly, and the session only survived rebooting as the result of deliberate alteration of the configuration on the part of the user then perhaps you'd have a point.

    11. Re:Personally, I wish that they would fix the bug by Threni · · Score: 1

      > Not closing apps before shutting down is bad practice

      Nice use of the verb "is" to suggest that you're right objectively and there's no other position on the matter. Somehow I've managed to use system shutdown as my working practice at home and at work (I'm a software developer) and escaped losing any 500 MB files. We're talking about Firefox so I'm not sure how I'd create/edit this 500 MB file in the first place. Most recent apps auto-save to prevent from power outages etc - perhaps my anal saving/sourcesafe/backup tics are helping me out a little here.

      This sort of thing is usually configurable, anyway.

    12. Re:Personally, I wish that they would fix the bug by Sigma+7 · · Score: 1
      Applications get a very distinct message indicating a shutdown of Windows. If the application doesn't handle said message and not turn off, Windows is forced to kill the program.


      Quick test:
      - Open up notepad.
      - Type something.
      - Try to shutdown windows.

      Notepad, at least in Windows XP, will ask if you want to save changes. If you wait for these 20 seconds, Windows will think Notepad is hung and wants to shut down the application.

      This is actually a more common problem that even appears in Microsoft Office. If you have unsaved data, applications want to be sure whether or not the user wants to keep it if the system is going down.
  22. What security flaws? by MarkByers · · Score: 3, Informative

    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...
  23. Where did all the Mozilla/Firefox enthusiasim go? by linebackn · · Score: 5, Insightful

    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!

  24. Re:IE7 by hahafaha · · Score: 1

    Hmm, so here's a question: what about IE7 is so great?

    I myself use both GNU/Linux and FF2, but I will try to be as unbiased as possible. What don't you like about FF2 and what do you like about IE?

  25. neosmart.net is a troll by Anonymous Coward · · Score: 0

    Take a look at the tags each story citing NeoSmart has gotten:

    lame, fud, and now this.

    I don't know why anyone listens to what they have to say when they have such a clear track record of trolling.

  26. Re:IE7 by Anonymous Coward · · Score: 0

    Thanks, your check is in the mail. BillG.

  27. Re:IE7 by Joseph+W.+Stalin · · Score: 1

    I agree that Internet Explorer 7 is definitely competition for Firefox. However, I think the IE team shot themselves in the foot when they moved the menu bar. I went back to Firefox because I liked the user interface better.

    --
    In Soviet Russia, sigs read YOU!
  28. Re:Solution by hahafaha · · Score: 2, Informative

    And how, pray ask, is Konqueror better? Not only does it require KDE, which I don't want to use, it does not have an extension system, is not compatible with other operating systems and in some cases, websites.

  29. Re:JESUS FRACKING CHRIST by Anonymous Coward · · Score: 0

    There's no apostrophe in frack, so why do you think it's a contraction?

  30. Re:IE7 by Computer+Guru · · Score: 0

    Try pressing the "alt" key.

  31. Re:IE7 by jakedakat · · Score: 1

    I have installed IE7 on a few customers machines and then had to uninstall shortly after. I have had problems loading many pages with IE7. The pages it had problems loading comcast.net, cnn.com, slashdot.org. Not quite sure why, it would just hang indefinitely. There have been quite a few customers at my work who had IE7 installed in the latest round of updates, then when they uninstalled it IE6 was broke. Gotta love it.

  32. Good software can't lose its way by dkarma · · Score: 1

    Let's look at the facts.

    1. Stops popups automatically
    2. constant updates and improvements every x months (because it is open source)
    3. better security than IE
    4. the option to easily clear cookies, history, temp files, etc on close (finding all the crap IE buries in your HDD is next to impossible for the average user)
    IMHO The firefox browser is a damn good browser.

    To tell you the truth I use FF for #1 ALONE. After listening to all the chatter on slashdot about holes in IE7...

    If your honda has a bad muffler, do you trade it in for a yugo?

    1. Re:Good software can't lose its way by Anonymous Coward · · Score: 0

      1. Stops popups automaticallyusing Fx 2.0/XP Pro SP2 - that's not the case, not all popups at least. Try http://wow.allakhazam.com/ for examples (and that's not the only site)

    2. Re:Good software can't lose its way by Danga · · Score: 3, Informative

      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.
    3. Re:Good software can't lose its way by Fizzl · · Score: 1

      If your honda has a bad muffler, do you trade it in for a yugo?
      What kind of analogy is this? Did you blow a tire on your Skoda? Wanna trade it in for Lada with broken drivers seat?

    4. Re:Good software can't lose its way by nanananini · · Score: 1

      I hate to say it, but IE7 does both #1 and #4 (Tools->Delete Browsing History). To do #4 on close just go to Tools -> Internet Options -> Advanced.

    5. Re:Good software can't lose its way by iabervon · · Score: 1

      I think the complaint is that Firefox 1.5 is better than Firefox 2.0. If I try out a new Honda, and it's less pleasant to drive than my old Honda, I stick with my current car, and I worry about what I'll do if it breaks down.

      All of your items are good reasons to use Firefox 1.5. Firefox 2.0 doesn't add anything I find compelling, and it adds non-removable junk to the navigation toolbar. It's a legitimate worry that I'll eventually have to go to a worse browser than Firefox 1.5 to have the latest security updates, because the Firefox team will only support 2.0 and their trademark policies prohibit other people from fixing things.

    6. Re:Good software can't lose its way by Anonymous Coward · · Score: 0

      Plus, both Opera and Firefox's default themes are ugly as sin. But opera lets you download a new theme and immediatly try it out, while Firefox makes you download, reboot start Firefox and then look at the theme, repeat for each.

    7. Re:Good software can't lose its way by Anonymous Coward · · Score: 0

      I have used Opera on and off for quite a few years. I don't like it. The feel is just not there for me. I use Firefox as my primary browser since it was at 0.8. I also use Konqueror or Dillo, it all depends on what system I am on and what I am needing to do. Actually I also use Lynx on my little 150mhz laptop. I will not use IE.

      I try to get everyone I know to stop using IE. I always recommend Firefox or Opera. I give them links to both or I even download them and allow them to figure things out. I have never seen one of them keep Opera. They feel that Firefox is better for them just by the way it looks and feels, then they fall in love with various extensions. Opera is very nice, but it has a feel that doesn't seem to pull me in and it appears others are also not pulled in.

      After downloading Fx2 I fiddled with settings to get it to look like my old 1.5 installation. I did not like the new look of the UI. However, others I know who downloaded it love the new UI. They only wanted the close button back on the right side of the tab bar. They like the gradient on the tabs, they liked the feel and they liked some of the other enhancements. These are people who call me to come over and install anything they purchase. They do not want to watch me install it or even listen to how to install simple software. They prefer to pay me to install it for them. They chose Firefox over Opera and IE. They chose Fx2.0 over Fx1.5 as it felt correct to them.

      Seeing people who are not tech-savvy choosing Fx2.0 over Fx1.5 in regards to the UI and the feel of the browser is a refresher to me to remember that Fx is going after those that use IE and they know that people who have a problem with the UI changes to Fx will either figure out how to fix those problems or will complain on an online forum about it and someone will post a fix for them.

      Opera is good and I recommend it, but for my daily web surfing, Firefox it is.

    8. Re:Good software can't lose its way by Ash-Fox · · Score: 1
      Have you ever tried out Opera?

      Let's look at the facts for Opera:
      *Snip*

      It fails my check 1. Browser synchronization.

      Until it obtains such a feature, I have no need to try it.

      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.
      To be honest, I wasn't very impressed with how it didn't support my bank's site (even when changing the browser agent) -- but for some reason they support Konqueror even.
      --
      Change is certain; progress is not obligatory.
    9. Re:Good software can't lose its way by Danga · · Score: 1

      It fails my check 1. Browser synchronization.

      Until it obtains such a feature, I have no need to try it.


      Actually something similar is already in the works and I agree that browser synchronization is a HUGE bonus for firefox. The following is a quote from an interview with Wium Lie who is CTO at Opera:

      "You can start, for example, reading a CNET article on your laptop in the morning and then, as you run out and catch a bus or subway, you can continue reading that article on your phone; the data can follow you. We're not quite there yet, but that's another point that's going to be a focus in our development--to try to synchronize data between the mobile world and the stationary world." http://news.com.com/For+Opera%2C+smaller+really+is +better/2008-1032_3-6124184.html

      So, Opera will soon have something similar.

      To be honest, I wasn't very impressed with how it didn't support my bank's site (even when changing the browser agent) -- but for some reason they support Konqueror even.

      How did it fail? This sounds more like a problem with how the website was coded and not a problem with Opera itself. I think it is a case of your banks website not supporting Opera, not Opera not supporting your banks website.

      --
      Hey, there is only one Return and it's not of the King, it's of the Jedi.
    10. Re:Good software can't lose its way by arevos · · Score: 1

      No automatic ad blocking :(

    11. Re:Good software can't lose its way by Danga · · Score: 1

      Opera does have pop up blocking. For the in page ads just get a good hosts file setup and that should take care of the rest of the ads. Problem solved.

      --
      Hey, there is only one Return and it's not of the King, it's of the Jedi.
    12. Re:Good software can't lose its way by arevos · · Score: 1
      Opera does have pop up blocking. For the in page ads just get a good hosts file setup and that should take care of the rest of the ads. Problem solved.

      No automatic ad blocking.

      Filterset.G has populated my filter list with over 3000 rules, which have so far blocked over 10'000 banner ads. Maintaining that list manually does not appeal to me. Secondly, a hosts file is rather limited compared to Regexs filtering on URL strings, nor does it update itself automatically to respond to new threats. Furthermore, with AdBlock, I don't even get broken image symbols; often I don't know whether a page has ads unless its layout gives the game away.

      With Firefox, it takes 2 minutes tops to remove 98% to 99% of all banner advertisements, forever. It's frighteningly effective. When Opera has the same capability, I'll be interested to know about it. Until then, it's just too useful a feature to do without.

    13. Re:Good software can't lose its way by Danga · · Score: 1

      That sounds great but I really don't mind ads as long as they aren't pop ups. With the popup blocker in Opera enabled and the hosts file from http://www.mvps.org/winhelp2002/hosts.htm I almost never see ads at all and it is pretty much "automatic". Also, using *'s in the hosts file really does a nice job and almost makes using regexes unneeded.

      I recently reset my hosts file because I figure the websites I like need to make money somehow and while I don't buy anything I do click on the ads at the sites I frequent quite often. Without revenue from ads many sites would not be able to exist so as long as they are not intrusive I really could care less to see them on the page.

      If just seeing ads bothers you so much then I can see why you would want to use filterset.g. For me as long as the ads don't cover a page or popup I don't mind them. I am glad that there are choices out there for us all, to each there own.

      --
      Hey, there is only one Return and it's not of the King, it's of the Jedi.
  33. Re:JESUS FRACKING CHRIST by Morky · · Score: 0, Offtopic

    Oh my gods. You don't know where the frack frack comes from?

  34. Fear. Uncertainty. Doubt.. This ones for u M$ PR by gd23ka · · Score: 1

    How about this one?

    Microsoft's Upcoming Operating System Woes.

    As Microsoft is planning to role out its latest installment in the Windows saga, tech experts warn
    that Vista is far from enterprise ready. "Up to now we have received no word whatsoever from
    Microsoft whether Vista will indeed integrate seamlessly with existing Windows 2000 servers" says Vox
    Technologica's Expert Frank Gibson. "As far as we know the numerous gotchas we have uncovered
    in the lastest beta release of the operating system have not been fixed". Since many of Microsoft's
    customers are still using Microsoft Windows 2000 servers, tech experts are not expecting a massive wave of
    upgrades to Microsoft Windows 2003. Tech experts agree, only very few corporate users will readily
    adopt Windows Vista in 2007 pointing out that Windows XP was shown the same kind of cold shoulder.

  35. One thing I hate about Firefox 2.0 by bismark.a · · Score: 1

    Is that by default the search box kept pinging Google's server for suggestions when you typed something in the search box. (I haven't seen where it pings for suggestions when the default search engine is not Google's). I can't understand why Firefox developers would leave it turned on by default.

    Any way browser.search.suggest.enabled is where this can be turned off. Just search for Filter: "suggest" in about:config tab.

    Now my (conspiracy) theory is that the suggestion redirect to Google is paid for by Google. Like it is (publicly known) for the searches in the Search box.

  36. Any search can offer suggest by Anonymous Coward · · Score: 0

    It simply has to be defined in the plugin and obviously supported by the search engine. It's not some google-only feature.

  37. anyone else remember when phoenix would fit by Anonymous Coward · · Score: 0

    ... on a floppy?

    Yeah, I'd say it's lost its way.

    1. Re:anyone else remember when phoenix would fit by HeroreV · · Score: 1

      On a what?

      In Korea, only old dying people use floppy disks.

    2. Re:anyone else remember when phoenix would fit by Anonymous Coward · · Score: 0
  38. It's got no apostrophe when its is a pronoun. by Radak · · Score: 2, Insightful

    NeoSmart Technologies has a recap on Firefox 2.0 and it's [sic] shortcomings. Aside from the technical aspects, the article raises some good questions about the Firefox "community," it's [sic] future, and what it's [sic] goals are at the end of the day.

    Attention Slashdot editors: Edit is a verb. Possessive pronouns in English (save one's) do not have apostrophes.

    1. Re:It's got no apostrophe when its is a pronoun. by Anonymous Coward · · Score: 0

      Why did you tack something random ("Edit is a verb") to your post? Please also show Slashdot editors that they need to be direct and to the point.

    2. Re:It's got no apostrophe when its is a pronoun. by Radak · · Score: 1

      Why did you tack something random ("Edit is a verb") to your post?

      That's not random. Slashdot editors are supposed to be editors, not just posters. Fixing submitters' egregious grammar is part of their job description, and yet they never seem to bother.

    3. Re:It's got no apostrophe when its is a pronoun. by Anonymous Coward · · Score: 0

      As opposed to "poster" which comes from the noun "post", I see.

    4. Re:It's got no apostrophe when its is a pronoun. by Anonymous Coward · · Score: 0

      As opposed to "poster" which comes from the noun "post", I see.That would be the verb "post".

    5. Re:It's got no apostrophe when its is a pronoun. by Sax+Maniac · · Score: 1

      I think you meant apostrophe's. The letter s is scary, and we need a warning when it end's a word. But sometime's I use it at the end anyway, just to be saf'e!

      --
      I can explanate how to administrate your network. You must configurate and segmentate it, so it can computate.
  39. Maybe they already accomplished what they needed t by Anonymous Coward · · Score: 2, Insightful

    Firefox's popularity finally shamed Microsoft into updating IE. They did what they needed to do -- encourage (or force) IE to catch up and maybe even try to innovate. The fact is, no matter how popular FF will ever or could ever get, it will probably never be more popular than IE, as long as IE remains the default browser. But by forcing MS to update IE, they've probably helped more people than those who actually use FF.

    It's still worth working on, sure, but it's not nearly as crucial as before. IE7 is not nearly as much an embarrassment as IE6 is.

  40. Re:Where did all the Mozilla/Firefox enthusiasim g by Anonymous Coward · · Score: 0, Insightful

    Bored, indeed!

    To me, this is exactly why open source software has yet to make the same inroads into large corporations as proprietary software (at least in the in United States).

    It's amazing how people have much more enthusiasm and creativity when an actual paycheck is involved. Otherwise, it's just a hobby. Microsoft, Sun, IBM, etc will always have an upper hand because they have paid resources to create and innovate (MS at least - Sun seems to be shooting themselves in the foot!).

  41. Gnome users; give epiphany a chance by Tribbin · · Score: 1

    I love firefox for it's plugins, but in gnome, epiphany might be a good choice. I found it more stable, easier on the mem and for the rest not all that different from firefox.

    Don't forget to enable the ad-blocker and page-info under Tools->Extensions.

    One thing I am missing though is the CTRL+K for google-search.

    While you are at it; try abiword whenever you don't really need OOo.

    --
    If you mod this up, your slashdot background will turn into a beautiful sunset!
    1. Re:Gnome users; give epiphany a chance by misleb · · Score: 1
      I love firefox for it's plugins, but in gnome, epiphany might be a good choice. I found it more stable, easier on the mem and for the rest not all that different from firefox.


      What is FF without plugins?

      Don't forget to enable the ad-blocker and page-info under Tools->Extensions.


      If it ain't Adblock Plus, it ain't nothin' :-)

      -matthew
      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
  42. Re:IE7 by Anonymous Coward · · Score: 0

    Right click over the menu region and select "Menu Bar". Now you can go back to IE.

  43. noticed out library is not using it by Anonymous Coward · · Score: 4, Interesting

    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.

    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&conten 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

    1. Re:noticed out library is not using it by laffer1 · · Score: 1

      We must hold off with the firefox 2 upgrade at work due to old ssl support with the webserver. There is a workaround but people above me don't want to do it.

    2. Re:noticed out library is not using it by WuphonsReach · · Score: 1

      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 tried that... and got tired of a crash in one applet taking out the entire suite. Which left me trying to pickup the pieces and remember what all I was working on when the suite crashed.

      (I used the suite up until about 2 months ago and finally switched back to standalone versions of Thunderbird and Firefox.)

      --
      Wolde you bothe eate your cake, and have your cake?
  44. Re:JESUS FRACKING CHRIST by westlake · · Score: 0, Offtopic
    IT'S is a contraction for IT IS motherfrackers! How fracking hard is that to understand!?

    Very hard.

    It is, after all, arguably the most common grammatical error in the English language.

    The meaning is always clear in context and there is little real incentive to correct it. Nor will you get any thanks for pointing it out.

  45. why does it have to be so damn slow under linux? by biscon · · Score: 2, Interesting

    Before you instantly flamebait me for critizing a high profile OSS project please let me briefly explain my background.

    I am an almost 100% Linux user simply because its the OS which works best for me. I keep a spare windows partition only for playing
    games. Also I try to suggest OSS solutions in my dayjob and have so far succeeded in getting my company dependent on Apache/MySQL, Imagemagick, Ghostscript, PHP etc (unfortunately all on windows servers, which I loathe).

    Anyway allow me to get to the point:
    Can anyone tell me why Firefox both starts and run so much slower on linux than windows. It almost feels like its made for windows and the linux version is running on some emulation layer. Now I know thats not the case, I know about their XUL platform and all of that.
    The very slow loading could have something to do with the dynamical linker being somewhat slower on linux?, or is the instantiation of lots and lots of objects? slow memory allocation. But I seem to recall linux being much faster at that although I can't point you at any graphs or papers.

    Why is it slower than the windows version when you have lots of open tabs?. I've seem to recall hearing that this is due to the flashplugin for linux being slow and since almost every page have flash everywhere yadda yadda.. Haven't tried to compare the two using pages with no flash objects so that sounds quite reasonable.

    Why is it slower doing DHTML? again I don't really know if that is the case but try opening http://dojotoolkit.org/ "See it in action"->General widgets->Fisheye (sorry but I can't be bothered to try and dig out a direct link into that steaming pile of javascript (no offense dojo devs)) and compare the rendering speed in firefox/win32 vs. firefox/i386?

    This isn't meant as a whining post. Im genuinely interested in why there is such a huge different between the windows and linux firefox experience, I've been wondering about that simple fact for several years now.

    and no I can't provide sources and all that crap but being developer myself and having used the software for a long time, I sure can tell when an application is noticeable faster on the same machine.

    if any firefox dev is reading this: don't get me wrong im grateful for what I got, firefox is a great browser. I just think its sad that the greatest OSS browser runs worst on the greatest OSS OS (GNU/Linux).

  46. Firefox 200, Konqueror 50 by Colin+Smith · · Score: 1

    MB of RAM that is. Plus with Konqueror, a larger proportion is shared libraries.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. Hmmm. Yes...

    --
    Deleted
  47. Firefox's future problems by itz2000 · · Score: 2, Insightful
    currently there are like 15% people who are using firefox, which is in-fact great, but I think this rating will stop soon since there are not enough people who would actually try to install a program, in this case, not a default program : firefox, to make their life easier!

    The regular user when he installs firefox, versions 1.5 or 2, don't really see why Firefox is better then Explorer.

    He doesn't see the extensions, add-ons, etc
    And to be honest vanilla Explorer > vanilla Firefox, though "hacked" firefox (jesus, I'm using too many linux terms) is much better then Explorer.

    So the other 85% need guide to show them how and why firefox > explorer.

    About firefox source, I think that it's too much a mess like someone already commented on from a few minutes of looking on it.

    What we shall do now, is continuing helping people to see why Open Source is good! I've traveled through schools and showed them linux, Firefox, etc. I'm talk backing on ynet.co.il the local news site, and offering help to move to linux (till now helped 56 people to move to linux!). I hope you're doing as much as you can to help the open source community.!
    GOODLUCK :]

    1. Re:Firefox's future problems by Iloinen+Lohikrme · · Score: 1

      I think that we could easily up the 15% to 25% or 30% just by telling our moms, dads, brothers, sisters and friends that we won't support computers whos user uses Internet Explorer. I myself have got everybody from my family to use Firefox by installing and deleting Internet Explorer icons and warning them about the perils of using Internet Explorer. The only thing todo now is to convert them to Linux. Next time when my familys home computer is updated I will give my ultimatum "I do not support any other systems than Linux", this is great because then I will not be bothered with help desk issues and if they indeed fold, then I can lock the machine so deep that they can't screw it. Ha!

      On a different note, I like Firefox 2.0, thought it's not so visible upgrade to 1.5, but it still rocks. Actually I really don't care what browser people are using as long as it supports standards and don't open huge security holes to the system.

  48. Re:why does it have to be so damn slow under linux by biscon · · Score: 1

    I'd like to add: this is my experience after running firefox on 4 different distributions and having compiled it myself once, since it wasn't called firefox and the version numbers started with 0.

  49. Re:IE7 by Anonymous Coward · · Score: 0

    No it doesn't, it just adds the menu bar back. It does not put the buttons back in order, and the menu bar is forced to be under the buttons. I think that the user interface is to drastic of a change without the option to go back to the default view.

  50. Re:Where did all the Mozilla/Firefox enthusiasim g by Tet · · Score: 2
    I think the main problem here is that Firefox has pretty much reached perfection.

    Ha ha ha ha ha ha ha! You really ought to consider a career as a stand up comic. I haven't heard anything that funny in years. I can't even begin to express how far from perfection Firefox is. Perhaps it'd be closer to perfection if it handled cookies properly, handled unknown content types in a sane manner, and most importantly, had a rendering engine that didn't suck (or at least, a development team that was interested in fixing rendering bugs, rather than adding on yet more new and pointless features and eye candy instead).

    --
    "The invisible and the non-existent look very much alike." -- Delos B. McKown
  51. Dealing with MS by Anonymous Coward · · Score: 1, Interesting

    Dealing with MS and the mindset that goes with it is what is the big fat mess, and it always has been. The linux devs need to make a *serious* fork and just go their own way,completely, even to the point of renaming the new open source browser something else and work ONLY for open source operating systems. Let the Microsoft volunteer partners (like novell and suse now and the bulk of the mozilla people) deal with making crap work with WINDOWS. FF is 99% a WINDOWS product. We need a LINUX browser.

    1. Re:Dealing with MS by Ash-Fox · · Score: 1
      We need a LINUX browser.
      Konqueror?
      --
      Change is certain; progress is not obligatory.
    2. Re:Dealing with MS by Anonymous Coward · · Score: 0

      KDE runs on Windows.

      These days with source code and sufficient human resources, one could port code from one platform to another quite easily. On the Windows side we have cygwin, and on the Linux/*nix side we have Wine.

  52. Changing existing behavior for no good reason. by SCHecklerX · · Score: 2, Interesting

    Messing with behaviors from older versions is a lame thing to do. For example: Replacing the menu hot keys (this totally broke my sage extension hotkey. GRRRRR), and changing the behavior of backspace on the linux platform. Had to dig through about:config to find and fix the latter. No easy way to do the former without messing with your personal css files. Not cool.

    1. Re:Changing existing behavior for no good reason. by ICA · · Score: 1

      Agree 100%. The loss of Alt-S for Sage is probably my only remaining gripe with 2.0 after I turned off the new tab handling.

      These are not providing critical improvements, so the breaking of existing functionality is definitely not worth making the change.

    2. Re:Changing existing behavior for no good reason. by Michael+Wardle · · Score: 1

      What happened to backspace? Is this behavior new in Firefox 2?

    3. Re:Changing existing behavior for no good reason. by SCHecklerX · · Score: 1

      http://kb.mozillazine.org/Browser.backspace_action

      Regardless of whether or not you have a profile already, going from 1.5->2.0 decides to change the default behavior in linux. Frustrating. Existing behavior should never be changed, unless the 'new way' is the only way going forward (obviously not the case for the cases I cited).

    4. Re:Changing existing behavior for no good reason. by Michael+Wardle · · Score: 1

      What did you use it for before the change? To scroll up, to do something else, or did you accidentally press it?

    5. Re:Changing existing behavior for no good reason. by Phroggy · · Score: 1

      Bizarre.

      I disagree that existing behavior should never be changed, if the new behavior is better. However, I can't imagine why anyone would ever want to use the backspace key to scroll.

      Thanks for pointing this out, so now I know how to disable it altogether (I sometimes hit it accidentally, thinking a form field has focus, and I've always hated it).

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  53. mirror by winkydink · · Score: 1
    --

    "I'd rather be a lightning rod than a seismometer." -Ken Kesey

  54. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  55. Mozilla Composer by phrostie · · Score: 1

    are they still developing the Mozilla Composer?

    i like to use it every now and then

    1. Re:Mozilla Composer by Anonymous Coward · · Score: 0

      It's now NVu:
      http://nvu.com/

    2. Re:Mozilla Composer by BenoitRen · · Score: 1

      SeaMonkey still has Composer, though hasn't really been developed anymore since years. It's mostly kept in working shape.

      However, the original author of Composer has made a stand-alone application called nVU (http://www.nvu.com/).

  56. Re:IE7 by Blakey+Rat · · Score: 1

    They just made it hidden by default. Like Safari does with the status bar.

    (I had a friend who used Safari for like a year and a half, and one day he complained to me that he wished it had a status bar. It never occurred to him, apparently, to check the View menu for an option to turn on the status bar, the same way you would with any other toolbar. So maybe you do have a point about IE7... either way, get used to it, because Windows Live Messenger and some other Vista apps are the same way.)

  57. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  58. If Developer Support Means Anything by coldcanofbeer · · Score: 3, Insightful

    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.

    1. Re:If Developer Support Means Anything by adolf · · Score: 1

      Thriving, eh?

      Another way of interpreting the data you present might be to say the following:

      According to Bill's Big List of Firefox 2.0 Extensions, users of more than 700 extensions had to wait up to 40 days for their favorite extensions to become usable on Firefox 2.0.

      Impressive developer support, indeed.

  59. Re:Solution by feld · · Score: 2, Interesting

    *KHTML is > Gecko. It is lighter, faster, and more standards compliant.

    *Konqueror does NOT require all of KDE; just mainly KDElibs and QT

    *It DOES have an extension system.

    Any questions?

  60. Re:JESUS FRACKING CHRIST by benicillin · · Score: 1

    hahaha... you believe in a supernatural being

    --
    "i stand on the edge of destruction" -shai hulud
  61. Re:Where did all the Mozilla/Firefox enthusiasim g by Kjella · · Score: 2, Interesting

    The article is slashdotted, but I think the main problem here is that Firefox has pretty much reached perfection.

    I doubt very many find Firefox perfect. But I do think that most people have got what they wanted - an alternative browser which is usable on mainstream pages and that runs on Linux and Mac. By mainstream sites I mean market share, Opera was standards compilant for years and never got the market share to make sites standard compliant. For many people that's probably "good enough" that they'd rather spend time using Firefox (or doing something else) than develop it. With the inertia it has, hopefully that'll be enough that the "IE-web" never comes back. The Mac market getting an upswing also promises well for that, and Linux... on the desktop any day now, right? And should Firefox flaunder and fail, I'm sure by then KDE4 and Konqueror would be there to carry the banner. Personally I'll be happy on Opera as long as IE's market share stays low.

    --
    Live today, because you never know what tomorrow brings
  62. Firefox needs attention... by Bashar+Abdullah · · Score: 1

    I am a big fan of open source, and have turned quite a few to Firefox from IE. But with IE7 coming, they have made a big progress, even if they are still trying to catch up with what Firefox has to offer. On the other hand, we can see new problems arising with Firefox 2, and some inhereted from Firefox 1.5 like the excessive memory usage. I would say IE have won this round and Firefox need to act strong to bring things back.

    1. Re:Firefox needs attention... by Anonymous Coward · · Score: 0

      Absolutely not. I installed ie7 too and before installing ie7 i have been using ie6. With the instal of ie7 i start hating ie and turned to ff.

    2. Re:Firefox needs attention... by Bashar+Abdullah · · Score: 1

      You are absolutely right. Most people who changed from IE7 to FF 2 hated the Options menu mainly. But I am giving my own experience so far, even though I am using Firefox and cant see my self going back to IE. I love it :)

  63. Life is too short! by Anonymous Coward · · Score: 0, Redundant

    Life is too short to spend very much of your time fixing things. One of the reasons I use KDE today is the butt ugly monkey paw icon the juvenile coders at Gnome(childishness is a state of mind, not of age) placed all over everything. You simply cannot expect professional results from such people who are so disconnected with the real world. I could have changed the image to something else--but who in their right mind is going to spend the time eleminating such an eyesore from a UI when the very presence of such a butt ugly image is itself a denunciation of the capabilities of the coders. Gnome has apparently grown up considerably, but I will stick with KDE when I use Linux. Yet KDE in its rush to be compatable with Microsoft broke to unuseability the calendar tool I used for years, and it is remains unuseable after a year. Firefox just went through a transition with the typical lack of grace I have increasingly noted as characteristic of all free/open software products over the past few years--they seem unable to manage transitions as gracefully as the commercial outfits when the project reaches a certain size. Oh for the days of Red Hat 4.2 and the clean crisp AfterStep GUI where there weren't a lot of bells and whistles, but dammit everything worked: there is a lot to be said for simple, even austere, working environments, without the endless list of skins designed by juveniles and the crufty changes made to software to accomodate them. Maybe I am a dinosaur (I learned Fortran IV back in '64), and I haven't done much coding for years (I am a physicist), but I bought a MacBook Pro 17" (now that it is 64 bit) as my step away from the crap in free/oss software projects the past few years; when Leopard comes out with its VM in the Spring I will probably install Red Hat Enterprise or SUSE, and probably with a custom kernel, just to keep my hand in Linux, but it will be decidedly my secondary platform. (I still have a Linux desktop at the office.) I have Firefox, Mozilla and SeaMonkey (another dubious name which suggests juveniles again), and am writing this from Camino; I like Mozilla mostly for its web composer feature, for minimal mostly tombstone type web pages for classes I teach these days. Like the old .0 Red Hat releases, I will wait a bit before trying out Firefox 2.0. I actually feel more use for the all-in-one like Mozilla or Sea Monkey, but Firefox+Thunderbird works well in Linux, and probably will on my Mac.

    Far more important for the future of free/open software is the development of models for creating and maintaining large projects, like Firefox--forget the pouty adults and their GPL3, which is and can only be a source of divisiveness. You need the ability to create and maintain large projects, and frankly that will probably take more discipline than most free/open software is capable of maintaining these days!

    My two bits.

    1. Re:Life is too short! by Anonymous Coward · · Score: 0, Insightful

      You, sir, are an idiot.

    2. Re:Life is too short! by crucini · · Score: 1

      Interesting points. I too enjoyed the older RH releases and used AfterStep. But running a modern distro does not mean you have to run Gnome or KDE. I currently use fluxbox, which is about as minimal and fast as you can reasonably get.

      I don't see how free software can manage transition as well as commercial software. Thinking through the transition issues is a boring process. In a commercial software shop, the developers are interested in the new version. Others, like support and marketing, may be aware of the needs of existing customers. In free software, the developers run the show.

      The "juvenile" names of programs also reflect the fact that developers run the show with no intervening marketing department. Inside commercial software shops, products and subsystems are given names much like free software. But these names are usually kept hidden, or only leak out to fans.

    3. Re:Life is too short! by Zontar+The+Mindless · · Score: 1
      Oh for the days of Red Hat 4.2 and the clean crisp AfterStep GUI...

      Welcome to the days of SuSE 10.1 and WindowMaker, then.


      Or not - up to you.

      --
      Il n'y a pas de Planet B.
    4. Re:Life is too short! by HomelessInLaJolla · · Score: 2, Insightful

      Fluxbox is enormous compared to the sheer genius and simplicity of UWM/UDE.

      If people want eye candy inside of a wm which is still sane and doesn't attempt to take over your system why aren't more people looking at Enlightenment?

      --
      the NPG electrode was replaced with carbon blac
    5. Re:Life is too short! by binarybum · · Score: 2, Interesting

      I spend almost all of my time fixing things, and I think life is richer for it. It's an incredible learning experience and those that fix and repair are far better suited to create as well.
          As for all of your accusations about this or that being "juvenile" - OS has been trying to penetrate to a larger audience for some time now - what seems juvenile to you is considered "user friendly" to others, and there's nothing wrong with that especially when you have the power to modify or disable these features. Additionally, a lot of people go into OS because they are enthusiastic, creative individuals striving to produce more than just a paycheck. Don't confuse creativity for immaturity.

      --
      ôó
    6. Re:Life is too short! by Skye16 · · Score: 1
      If people want eye candy inside of a wm which is still sane and doesn't attempt to take over your system why aren't more people looking at Enlightenment?
      fear of cooties.

      :(
    7. Re:Life is too short! by Anonymous Coward · · Score: 0

      Ugh - WindowLab is smaller, faster and smarter.

    8. Re:Life is too short! by HomelessInLaJolla · · Score: 1

      Hm. Since my laptop was stolen and I'm homeless I don't have a system on which to play around with this. I empathize with the author's respect for the Amiga--I was an Amiga advocate for many years until I was forced to the IBM-PC/compatible market out of financial considerations. I could no longer afford to keep up with the Amiga hardware market. I had an A500 with a Kickback module (to switch between 2.04 and 1.3 ROMs), Supra28 accelerator and a sidecar IDE HD controller. When the Kickback module and the Supra28 accelerator burned out it would have cost me nearly $2k to reinvest in an A1200 or $3k+ for an A4000. At the time CBM was also in the handbasket going south and I couldn't justify the expense, even if I had the funding available, on a technology which, while superior, was being provided by a company run by executives who were milking it dry until it hit the dirt.

      The screenshots make it look comparable. I know that UDE/UWM is full-featured and customizable in terms of window borders, border decorations, default colors, and many different parameters and behaviors. When I finally come across a reasonable opportunity which allows me to elevate myself out of this position I'll have a look at it.

      What's the compiled binary size?

      --
      the NPG electrode was replaced with carbon blac
  64. Firefox needs a "standard extension" concept by iabervon · · Score: 1

    I think the real problem is that Firefox doesn't make enough use of the extension mechanism. It's clearly sufficiently powerful to do all sorts of interesting things with, but the default install of Firefox doesn't have any extensions at all. You can change a lot of the appearance of Firefox with themes, but it doesn't come with any themes, either (the "default theme" thing is actually not handled as a theme, but is just the built-in defaults for things, which is why you can't install 1.5's default theme on 2.0).

    What they should do is split most of the functionality into extensions and all of the appearance into themes, and ship those extensions and themes with the browser. Then you'd be able to choose exactly which features you want from each version. And, since extensions can be updated independantly of the rest of the browser, it would be no problem if there was a bug in deciding that a word had been typed completely for the inline spellchecker; they'd release a new version of the spellchecker whenever they fixed it.

    1. Re:Firefox needs a "standard extension" concept by HeroreV · · Score: 1

      Actually the default install comes with the DOM Inspector and Talkback extensions. During installation you can control whether they are installed or not.

  65. Big projects need good methodologies by mangu · · Score: 2, Insightful
    C and C++ lends itself to all manner of abuse and abstractions only the original developer can usually figure out.


    That's true for any moderately useful language. If the language locks you in with limitations, the end result is that the code grows up too much, and either the files become too large or there are so many source code files that you cannot find your way in the project.


    With the languages people have been creating in the last 20 years or so, the limitations appear outside of their specialization. For instance, Perl is an excellent language for what it does best, which is processing text through regular expressions, and a mess for many other uses. PHP is wonderful for doing its own specialty, accessing databases from websites. Also, I particularly like the way PHP handles arrays, making them functionally equal to dictionaries. And Python is excellent for small scientific/engineering apps. I think the only "modern" language I absolutely hate is Ruby, because of its ugly syntax. It seems like the Ruby designers did their best effort to create syntax rules that are even more irregular than FORTRAN's...


    But when a project grows big, one needs more than syntax, one needs to look at an upper level of organization. The project needs to be well structured in the API, it needs a well-layered set of libraries, it needs a clearly mapped directory structure, etc.


    When I manage a large project, I usually start by designing an overall structure for the API that will handle the most computation intensive tasks. These are coded in a library, normally written in C/C++. I make an effort to consolidate and freeze the core API as early as possible, new functions may be added later, but I make an effort to have the most basic functions unchanged. Around this core library one can use different languages, I often do prototypes in either Python or Perl and rewrite them in C/C++ if necessary. The language itself is relatively unimportant for me, I think good coding practices are more important. Use short functions (<150 lines), mnemonic names, well indented code, plenty of comments (but avoid unnecessary ones, like int counter /* counter */, for instance).


    With these practices, one can write code that stays readable as the system grows, regardless of the language. The big problem is with projects that started small and grew up over the years. With these, it's often easier to start over than to try to keep adding functions to the old code, but of course, with a project the size of Firefox, it would take a manager with adamantium balls to decide to rewrite it from scratch.

  66. Re:Solution by Anonymous Coward · · Score: 0

    Given that you don't use KDE I'm not surprised by your ignorance of Konq. But that doesn't mean you should start fabulating just because you don't agree with someone.
    For compability there is a possibility that KDE 4 will be usable on a larger number of platforms, sure it's in the future, sue me :P

    But the rest of your fabulations are bollocks. I've never encountered any websites which would work in FF but not in Konq (besides those which doesn't work with other browsers at all) And for extensions, it does have an extension system - perhaps not widely used (hm, could that be because KDE isn't as widely used?) but it's there.

    Now why its better, in my opinion: Out of box experience. In my *opinion* Konq's current incarnation is better than FF 2 since it has most of the features which were new in FF 2 (the reason for that is quite obvious) but it doesn't have the annoyances of FF, like sending me to FedEx all the time, or educators of America or some such instead of giving me a 404 error when misstyping an URL. To get rid of these annoyances I actually have to configure FF with local:config or whatever it is.. not user friendly.

    Then there is the small matter of it also being able (never mind it's the default one..) to act as a file manager, this is simply something FF just can't do at all. There is also the performance issue, with many tabs open over a long period of time, often involving multi-tasking, FF starts to allocate huge amounts of memory. Now that isn't a problem for most people with a new system, but my system isn't old and it annoyed the heck out of me to have to wait about 5 seconds before FF was redrawn after switching from another (MS windows) application (it's page caching I'm talking about, just in case my rambling is unclear) so, I have to admit, yes, I've only used FF on XP/2003 so it might be diffrent on other operating systems, but it doesn't change the fact that it put me off.

    Needless to say I've had none of these problems with Kong (and yes I use the same applications on the same system, except the OS itself and media player, which means that winamp got turned into amarok - you judge which is most least resource demanding).

    I've used pretty much all versions of FF and I still prefer Konq. The early versions FF were my favorite for a long time and I still consider it a good browser, but it is just a browser and that being said - it's starting to get bogged down with "features" which I simply do not wish for. As for now Konq got the essential functionality of FF and better desktop integration.

    That is my take on "why it's better".

    You on the otherhand deride Konq. based on the fact that you like your gnome/whatever desktop environment better. which I find a bad criteria for choosing "the better browser". Perhaps you should have asked "Better for me in what way? I don't use KDE" and the answer to that is you have to find it out for your self, I'm sure there are people here willing to swear by their favorite browser fit for their favorite work environment.

  67. Re:IE7 by NineNine · · Score: 1

    To me, neither browser is "Great". FF is nice because of all of the extensions. I use one for the game I play (See my sig), and I used a very handy one the other day for reporting a *lot* of form post fields. It didn't work quite right, but it was still helpful.

    IE is nice because for me, I don't ever see the terrible memory leaks that FF has. If I leave FF open for more than an hour or so, it starts to get really big and nasty. Also, FF seems to browse much slower than IE, and hangs a lot of regular pages. In fact, the other day, I caught myself automatically hitting "reload" on a page when browsing with FF because it happens so often, and I thought, "why do I have to reload pages so often when browsing with FF"?

  68. Re:Where did all the Mozilla/Firefox enthusiasim g by bensch128 · · Score: 1

    Sigh, I guess that is why a business driving opensource is usually a more likely candidate for success then a group of amarture programmers.
    Their modivation for continuing to perfect the product is money, not peer-recongition or geek-worship.

    I'm not saying FF2.0 is bad, it's just that they need better managers who can prioritize properly managing their great programmers.
    Otherwise, their programmers will get lost adding new features instead of fixing bugs.
    That'll probably result in a better product overall, as well.

    Cheers
    Ben

  69. Re: yes the code will be fixed by arifirefox · · Score: 3, Informative

    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/
  70. Re:Solution by Anonymous Coward · · Score: 2, Interesting

    "Any questions?"

    Yes: Is sombody working on a firefox that uses khtml for rendering, or alternatively: A khtml-based browser that supports firefox extensions?

  71. Re:Solution by hahafaha · · Score: 1

    Wow, good reply, and thank you. I stand corrected. I won't switch to Konqueror because it does not work nicely with GNOME, but I really respect what you said. I will try to be more considerate next time.

  72. Not popups anymore by everphilski · · Score: 2, Interesting

    There are **plenty** of sites that can get around FF's popup blocker. And IE 7's popup blocker is getting good. I'd say they are about equal now.

    1. Re:Not popups anymore by jesser · · Score: 1

      I haven't noticed this. Can you file a bug with a URL (or even better, a simple testcase) if there isn't already a bug on it?

      --
      The shareholder is always right.
  73. Re:Where did all the Mozilla/Firefox enthusiasim g by anaesthetica · · Score: 1
    Now there seems to be a bigger push for built-in gee-whiz features.

    Actually, I'd say just the opposite: there's a push against the bloat that the community can seem to do nothing about. Lean-mean browser? Not so much anymore. More whiz-bang features keep getting added, while bugs and performance fall by the wayside.

    I think there was a lot of excitement over the 1.0 push and the race to take 10% of the market. After those big milestones it's not easy to get people excited once again until another big milestone comes along. You can't just schedule when we're going to take 20% of the market. And no version number is as important for an open-source project as the 1.0 mark--that kind of fire won't come back.

    I think the formula for future success I'm arriving at is:

    1. better code,
    2. better marketing,
    3. better grassroots developer/community outreach,
    4. leave the features to extension writers.
    5. ?????
    6. profit!
  74. I don't know about that. by LWATCDR · · Score: 1

    Right before Microsoft Released IE7 I was finishing up a new webpage. I checked it in FF and IE6 and it rendered fine on both. Then I start getting complaints. You guessed it IE7 didn't render it correctly.
    Good freaking grief.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    1. Re:I don't know about that. by jez9999 · · Score: 1

      Perhaps if it renders correectly in IE6, you might want to try putting IE7 into quirks mode. Specify the DOCTYPE as the HTML 4.01 transitional, and put an HTML comment right at the beginning of the document, before the doctype.

    2. Re:I don't know about that. by LWATCDR · · Score: 1

      Thanks but I already fixed the CSS. I had hoped that since I tested in FF, IE6, and Opera that it would work for seven but I am afraid that IE7 has it's new and improved bugs.
      So now testing is FF, Opera, IE7 and IE6... Oh joy.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  75. Opera is nice. by LWATCDR · · Score: 1

    I use it and I love the zoom function.
    Opera is better out of the box but I think Firefox is better once you get it set up with the right extensions.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    1. Re:Opera is nice. by Danga · · Score: 2, Interesting

      Yes, the zoom function definitely comes in handy at times.

      I honestly cannot say if firefox is better once it is setup with the right extensions, Opera just has everything I need already built in. I also know that the cold startup time for Opera is WAY less. According to:
      http://www.howtocreate.co.uk/browserSpeed.html#win speed

      Opera 9 takes only 2.74 seconds to startup compared to FF 2.0's time of 11.64 seconds. That alone will keep me from seriously testing out FF, when I start up a browser I want it working NOW and having to wait over 4 times longer is not acceptable.

      FF definitely has a lot more extensions to use and they may be better but Opera does have widgets now so it no longer is held back in regard to not having support for any third party extensions. Until I see a significant reason to switch over to FF I am sticking with Opera since I am used to it and prefer how it is setup and I think most diehard FF users are of the same mindset regarding FF. I used to be a Moz user until about 5 years ago when I discovered the tabbed browsing that Opera had and that is what got me to switch over at that point in time. To each their own.

      --
      Hey, there is only one Return and it's not of the King, it's of the Jedi.
    2. Re:Opera is nice. by petabyte · · Score: 1

      I have to say, I would switch over to Opera too, IF there was a way of using regexp based filtering like the adblock extension. I don't see ads with Firefox and adblock. I don't really want to use Firefox as I think its a disaster area of a browser next to Opera or Konq but since I'm a gnome user who has an addition to blocked ads, I'm stuck with this thing until something changes.

      It kills me because all I need is that one thing and firefox is gone.

    3. Re:Opera is nice. by nutshell42 · · Score: 1
      Konqueror->Settings->Configure Konqueror->AdBlock Filters. You *can* use regexps by putting them between "/"s (Just press Shift+F1 for a tooltip on how to do it)

      I have to say, I would switch over to Opera too, IF there was a way of using regexp based filtering like the adblock extension.

      Do you really need regexps? If a simple * wildcard is enough you can use Opera too (I don't think it supports regexps but I've never actually tried it). Right-click on any page->Block content...

      --
      Don't think of it as a flame---it's more like an argument that does 3d6 fire damage
    4. Re:Opera is nice. by nutshell42 · · Score: 1
      2 things I forgot/should clarify:

      You can right-click on images in Konqueror. The menu has two entries "Block Image" and "Block Images from (domain that image's from)". So you don't have to do it in the settings. The "Block Image" option also gives you an edit dialog where you can adjust the filter rule.

      In Opera you have to right-click *not* on the image but somewhere on the background. It will then highlight the images on the page and you can click on those you want to block.

      --
      Don't think of it as a flame---it's more like an argument that does 3d6 fire damage
    5. Re:Opera is nice. by petabyte · · Score: 1

      Well, I want to run filterset.g which consists of dozens of regexps. It works out of the box blocking everything I want blocked and not really anything I don't. I can click one button to disable it if I want.

      Opera's never done that. I can block ads, but not as well or it takes more work to get going. The main reason I don't use konqueror is that I use gnome or XFCE and try rather hard not to have qt or kdelibs installed on my system. Opera I can get by with the static qt version.

      I just don't understand why it is so hard to add regexp support to opera's filtering.

    6. Re:Opera is nice. by nutshell42 · · Score: 1
      I don't try to block all banner ads (in fact sometimes I even click on one =), just those in Flash, flashing, moving, annoying and sometimes even with sound. So I don't really need regexps for Opera but I see your point.

      I miss flashblock and its pdf equivalent, though. I prefer it if plugins are only loaded on demand. Oh and Firesomething.

      Why don't you want to use both Qt and GTK? Unless you're really short on RAM it shouldn't be too much of a problem. In the GNOME/KDE 1.x times my DE was KDE but I used GTK apps almost exclusively. I'm Pro-Choice so to speak =)

      --
      Don't think of it as a flame---it's more like an argument that does 3d6 fire damage
  76. Re:why does it have to be so damn slow under linux by NereusRen · · Score: 1

    I've seen the same thing you have, and I'm also interested if there's a reason for it.

    I run Firefox on Linux at home. I've tried both self-compiled and Mozilla precompiled binaries, with various versions from 1.0.x to 2.0. In all cases, complex sites like GMail are significantly slower on my home machine than on comparable or slightly slower Windows machines I use (e.g. at work or my parents' house). I haven't done a direct comparison by running Windows on the same computer as Linux, but I have more RAM and CPU speed than those computers, with less RAM being taken up by other running apps.

    Even sites without such fancy interfaces, such as phpBB-type forums, take a little bit longer to render the pages. It's annoying because they stick at 100% CPU while doing it, so I can't interact with the Firefox interface for that instant. Sounds trivial, but when I'm trying to open 5 forum threads at once and then switch to the tabs afterwards to read them, it slowly me down significantly compared to doing the same thing with Windows Firefox.

    Anyone have any insight on why the parent and I might be having these problems?

  77. Re:No, it's not "losing its way" - Ditto! by Anonymous Coward · · Score: 0

    Well said. The review is a bunch of needless tripe from some blogger trying to generate traffic to his/her website.

    Frankly, I didn't think there was much substance to the review... I guess they really needed to nitpick to find something to criticize. The bulk of the firefox community will upgrade from 1.5 to 2.0, so even the page 2 nitpicking really becomes a non-issue.

  78. Too popular for its own good? by MisterCookie · · Score: 1

    IMO, part of the problem is that the project now has legions of supporters just dumping money and publicity on the project, regardless of quality. Back when this project was just getting started, I bet they put much more effort into their code.

  79. Thank you by abigsmurf · · Score: 2, Insightful
    For demonstrating one of Firefox's clear problems.

    "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."

    The fact is, 99.9% of users simply aren't capable of finding and fixing these bug. When Firefox has to compete with Opera and IE which generally don't have such basic bugs (copy & paste bug is still occuring for me in an updated version) and when people moan about problems, they tend to (eventually) get fixed. A sluggish response is always better than "fix it yourself" responses that result in long term bugs that plague firefox.

  80. Volunteers are not slaves. by sowth · · Score: 3, Insightful

    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.

    1. Re:Volunteers are not slaves. by toddbu · · Score: 4, Interesting

      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.
    2. Re:Volunteers are not slaves. by filterchild · · Score: 4, Insightful

      I have noticed that the free software world tends to mirror the commercial software world in this one aspect: the larger the team, the more arrogant they become. I have, on several occasions, sent feature requests to software projects run by one or two people. They tended to be very cheerful and happy (flattered, almost!) that I had used their software to the point of finding a bug and submitting it. One developer actually patched the source tree and had an updated build posted within two hours. The few times that I've dealt with larger projects, they were not as helpful or happy to hear from me. Maybe it's just the issue of being jaded, being tired of so many bug reports? I'm not sure, but I can definitely say that some projects (be they open or commercial) could really use a bit of soul searching and re-commitment to their missions.

    3. Re:Volunteers are not slaves. by coaxial · · Score: 3, Interesting

      That's right they volunteered. The volunteered to dot a job. Now apparently some didn't realize that when you volunteer, you have to actually support the project instead of just call yourself a "developer" and shuffle deck chairs around. When the user base wants something fixed, then it should be fixed. That's called "being responsible" and "taking pride in your work." Volunteering is not a one way street, and some would have you believe. It's work and it doesn't mean that only have to do the the easy things that you like to do. That's why people don't volunteer. This is doubly so, when the group, like mozilla, has placed high barriers to entry. Specifically, the code is a poorly documented bizzare mishmash of multiple languages spread out among directories that don't have obvious names. Also, the review process effectively eliminates all external development, as the the codebase moves faster than the review process, and the sheer arrogance of the developers that "I own this." I'm sorry, you can't say you "own" it in one breath, and in the very next breath say "fix it yourself."

      The argument that if something is provided at no cost, it's somehow above reproach is an absurd intellectual cop out. The cost of something is completely irrelevant to its merits. Let's take your soup kitchen analogy. Suppose you walked into a soup kitchen and was served a soup consisting broken glass in a fine urine base. Would you honestly say, "Oh. Well this sucks, but I shouldn't complain. Afterall, it's free." Bullshit. Incompetence is incompetence at any price.

    4. Re:Volunteers are not slaves. by Shads · · Score: 2, Insightful

      You are absolutely right, and god knows I've abused that right. I mean, I called Microsoft and explained to them the bug their "Microsoft Windows 2000 Server" product had and asked that they fix it because whenever a certain transaction happened on the "Microsoft SQL Server" it caused the entire system to hang until it was rebooted. It only took them THREE MONTHS to put a patch out for it. I decided I was going to switch to another vendor because of how slow they went... but there really wasn't one except for Linux and MacOS. The latter's hardware vs performance at the time was obscenely expensive and our software was easier to port to a new OS on x86 than to change to powerpc.

      Yes, I definitely agree, it sure is nice to not be able to fix a problem yourself when the vendor goes so damn slowly that we'd have been out of business before they fixed the problem... why there are so many selections of better vendors in commercial software that ... oh wait there's not. Never mind my sarcasm.

      There are occasionally major bugs in open source software too. Generally, if we notify the developer (Redhat->SUSE->Gentoo->Debian & PostgreSQL->MySQL was our progression of developer groups) and they don't fix it fairly rapidly, one of our programmers goes in and patches it himself and we knock a patch to the developer who is responsible for the application/operating system in question... longest turnaround on a single bug so far? 11 hours. How often we've had to knock a patch out ourselves? 1 time... in 5 years. Most of the time by the time we discover a problem exists there is a newer version of the software out already fixing the problem (we run a few versions behind the most recent version usually.)

      I wish most commercial companies supported us as well as the developers of most open source projects.

      --
      Shadus
    5. Re:Volunteers are not slaves. by toddbu · · Score: 2, Interesting
      I know that you're being sarcastic here, but I'll reply anyway...

      "It only took them THREE MONTHS to put a patch out for it." - So how does this stack up with OSS? Let's see - FF leaks memory for many, many months and the community keeps getting told it's not a problem. I've stopped using FF for the most part because I don't want to have to restart my browser on a regular basis. I lose too much work that way.

      I'd also be interested to know how any commercial software vendor ranks against vendors of other products. How long does it take for Detroit to issue a recall on a car? I don't know the number myself, but I'd be shocked if it's less than three months. A problem has to go on for a very long time before a recall is issued, even if it's for safety.

      "How often we've had to knock a patch out ourselves? 1 time... in 5 years" - I don't get it, you complain that vendors aren't fast enough but then you say that only once in five years have you needed a patch quicker than the vendor can provide it?

      I don't know about you, but many IT departments neither have the time nor care enough to want to fix other people's code. They are willing to work around the limitations of the software that they have, or live without a feature until the vendor makes it available. You may think that this is bone-headed, but it's reality. And F/OSS is doing little to address this issue. I applaud Ubuntu for putting out 6.06 LTS. It's a clear recognition that what matters most to the people making the decisions is stability, not features.

      --
      If you don't want crime to pay, let the government run it.
    6. Re:Volunteers are not slaves. by Anonymous Coward · · Score: 0

      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.

      No, but I would expect them to have bowls.

      Bum: Where are the bowls?
      Volunteer A: Fuck you. We volunteered. We made the soup. If you want a bowl, you should have brought one from home.
      Bum: But I'm a bum. I don't own a bowl. How can you serve soup without bowls? And what's kind of soup is this? It looks like it's just lukewarm water.
      Volunteer A: Fuck you. We volunteered. Here's the soup recipe. If you want it, make it yourself, or are you too good for that?
      Bum: But you're already in the kitchen, and you said you'd make soup. Why didn't you make soup?
      Volunteer A: We're too busy playing with the garbage disposal.
      Volunteer B: Dude! Let's feed it the mop!
      Volunteer A: Awesome!

    7. Re:Volunteers are not slaves. by fluffy99 · · Score: 1

      Imagine if the soup kitchen down the street really did hand feed you and wipe you. Which one would you prefer? So you're saying that Firefox is of lower quality because it's free? That's heresy on Slashdot where most people blindly chant "open-source is better".

    8. Re:Volunteers are not slaves. by fluffy99 · · Score: 1

      So you have the ability to get minimally tested patches rolled out into the main stream pretty quickly. Sorry, I see that as a flaw because you may very well be introducing more bugs for the next person to have to patch.

    9. Re:Volunteers are not slaves. by coaxial · · Score: 1

      So it took Microsoft three months to issue a patch? Well given the fact that most commercial developers schedule releases on a quarterly basis, that would be "next release." The very fastest a group can release something that isn't an immediate critical problem, i.e. a disaster of biblical proportions. You know, Old Testament, real wrath-of-God type stuff. Fire and brimstone coming down from the skies. Rivers and seas boiling. Forty years of darkness. Earthquakes, volcanoes... The dead rising from the grave. Human sacrifice, dogs and cats living together - mass hysteria. (apologies to "Ghostbusters")

      The fact that you're getting you're critical systems patched in less than a day for non-critical problems, implies that you're basing your system off the live CVS branches. Why are on Earth are you doing that? It's so unstable. Someone checks in a wonky patch, and you're screwed. What project are you working on? I'd like to avoid it.

    10. Re:Volunteers are not slaves. by Shads · · Score: 2, Insightful

      "I don't get it, you complain that vendors aren't fast enough but then you say that only once in five years have you needed a patch quicker than the vendor can provide it?"

      I went on to explain that point. Since we changed to open source (about 5 years ago) there has been one time the vendor (various linux providers/database providers) didn't already have a patch out by the time we found the issue or didn't respond faster than we could.

      "It's a clear recognition that what matters most to the people making the decisions is stability, not features."

      Funny, availability is our primary concern, that's one of the reasons why we use Linux instead of Windows.

      "So how does this stack up with OSS? Let's see - FF leaks memory for many, many months and the community keeps getting told it's not a problem. I've stopped using FF for the most part because I don't want to have to restart my browser on a regular basis. I lose too much work that way."

      My firefox2 has been running for ~5 days now... firing firefox up on my other computer says there is a difference of ~7m from startup to ~5 days of memory use between them and it's presently ~12m under it's peak use. If that isn't the most pressing issue with firefox I don't know what is, good god make all of the devs drop what they're doing and jump on those massive memory leaks right the hell away, the world is ending, the sky is falling... and let me tell you, you lose so much in firefox after closing it since it can remember state... *rolls eyes*. Good thing most sites work well with having them open all day, you know cookies typically last forever... they don't expire... oh wait. Never mind. Gotta re-login anyways at many sites about once a day.

      Never mind that two different versions of windows have had memory leaks at the login screen that would make the server run so slow after sitting at the login screen for a week that you had to hard boot it. That is a serious memory leak... of course it "only" took microsoft a month or two to fix that. You're comparing two different kinds of problems, one is SERIOUS (FATAL, KILLS THE SYSTEM) compared to one that "inconveniences" *you* and that i've never even noticed. What are you running on a pentium 1 with 32mb of ram, if you are the memory leak you're probably experiencing is the windows 95 operating system, you generally needed to reboot it once a day to maintain any semblance of performance.

      --
      Shadus
    11. Re:Volunteers are not slaves. by Shads · · Score: 1

      Actually take the TIME to read what I wrote and then get back with me if you have something intelligent to say, if you can't figure out the part I'm referring to, I suggest you take some classes on basic English comprehension.

      --
      Shadus
    12. Re:Volunteers are not slaves. by Shads · · Score: 1

      I suggest you actually take the TIME to read what I wrote and then get back with me if you have something intelligent to say... otherwise I suggest you take some classes on basic English comprehension.

      --
      Shadus
    13. Re:Volunteers are not slaves. by Phisbut · · Score: 1
      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. [...] 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 use OSS and don't get what you want, then you can find an alternative. It's no different.

      I work for a proprietary-closed-source-software company. It happened a couple of times that a customer experienced a very rare bug because of some weird configuration they had, or that they wanted the software to behave slightly differently in a special situation. In both cases, we told the customer we could implement the specially requested feature just for them, but we would charge them to do it. Some accepted, some refused (we charge a lot... gotta pay the programmers). The extra feature made for that one client, we then make available for all of out users.

      Had it been an OSS, the user could have hired a programmer to add the required feature themselves, probably costing them about the same amount. Same result, different path.

      If the OSS maintainer decides not to add your feature or fix your bug, you can either do it yourself or hire someone to do it for you. If the proprietary software company decides to ignore your request, you're shit out of luck. Which actually makes me wonder why companies are not more nervous about using proprietary software for mission critical projects.

      --
      After 3 days without programming, life becomes meaningless
      - The Tao of Programming
    14. Re:Volunteers are not slaves. by coaxial · · Score: 0

      So, now an ad hominium attack. Truly, the last refuge of a man whose argument has been beaten.

      Bravo.

    15. Re:Volunteers are not slaves. by toddbu · · Score: 1
      "it's presently ~12m under it's peak use" - A lot of this depends on how you use FF. I also believe that this is a bigger problem on Linux than it is on Windows. (Not sure of your platform.) I had FF leaking several hundred megs, to the point where the system was paging so hard that it was hard to kill it. No other OSS that I was running (LAMP, Asterisk) had any serious memory issues.

      I find it interesting that you've adopted *exactly* the same attitude as the guys working on FF. Even though I found this problem documented in many places on the web (including /.), nothing was being done about the problem because those who were working on the code refused to recognize it as a serious issue. So back to my original point - if I've spent money on the software then I have every right to complain. But since I didn't pay anything for FF and I didn't want to spent the time to maintain a private build, I switched to (what for me is) a more reliable browser.

      --
      If you don't want crime to pay, let the government run it.
    16. Re:Volunteers are not slaves. by Pichu0102 · · Score: 1

      I doubt it's not so much as the size of the team, as the size of the userbase. Like you said, it's probably due to many people submitting so many bug reports, that they just get frustrated, but it's also probably due to things like arrogant users who act like everyone should listen to them first no matter what, and just the size of the userbase in general. I mean, I can imagine it must be frustrating trying to get something done when a large group of people is depending on you and your team to make it work, it must be very stressful.

    17. Re:Volunteers are not slaves. by bill_mcgonigle · · Score: 1

      Not to mention it doesn't take more than a few "why isn't this fixed already", "this bug has been open for years are you too dumb to fix it", or "I need this fixed NOW!" comments on bug to really perturb a developer.

      One problem I don't know how to fix is that the developers really should be insulated from this somewhat. There aren't really managers in the project who would traditionally fill this roll. Bugzilla really ought to have comment categories which could be cooperatively tagged to handle the spam so devs don't need to get annoyed by them.

      I do feel for the volunteers who have done good patches and the project managers have let them bitrot. That's almost inexcusable. Again, more non-programming management would probably be useful here.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    18. Re:Volunteers are not slaves. by bigpat · · Score: 1

      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.

      Hmm... Not so sure about that. When you buy a version of software, don't you buy it with bugs? Especially if the bugs are documented before you buy it, seems you have no legal recourse to demand that they fix any specific bug. Really the comfort seems to come from your ability to bitch to someone on the phone about a bug rather than any effective means of getting it fixed on your time schedule.

      With open source software if a bug is mission critical, then you can hire someone to fix it if you can't fix it yourself. You aren't reliant on the arbitrary priorities of another business. With closed source, especially when you are a smaller customer of a larger software company, then all you can do is demand that the company fix the bug. But you you can only push then as far as your contract goes, which usually won't be very far at all. Sometimes demands work, sometimes they don't. Additionally, I consider open source to be a real insurance against a company dropping support for a product, which happens more often than not.

    19. Re:Volunteers are not slaves. by coaxial · · Score: 0
      Excuse me for following up twice to the same comment, but I couldn't let this go without being mentioned.

      You've responded to two different posts -- in the same thread mind you -- the exact same way. This one says

      Actually take the TIME to read what I wrote and then get back with me if you have something intelligent to say, if you can't figure out the part I'm referring to, I suggest you take some classes on basic English comprehension.


      And then in this one you said:

      I suggest you actually take the TIME to read what I wrote and then get back with me if you have something intelligent to say... otherwise I suggest you take some classes on basic English comprehension.


      That's sad. That's really sad. It's a stock response. I guess I should be greatful that it wasn't just cut and pasted in, but still... Damn. That's pathetic. I mean, that's the kind of tactic I'd expect from a elementary school student. You know, something along the lines of "Nuh-uh!" and "I'm rubber and you're glue! What you you say bounces of me and sticks to you!" I mean, I haven't heard a ready made stock response to a criticism since the 5th grade. Seriously! And I know you're not 10. You have way to low of an ID for that. You're like what 30+? Geez.

      Now the fact that you're using a stock response, that not only doesn't rebut the criticism, but rather make some vague swipe at the critic's intellegence and english composition skills, is incredibly ironic. I mean, apparently only have one trick, and you apply it whether it makes sense or not. Since the responses don't make any sense in this contet, it draws into question whether you actually read and understood the criticism. I mean, if you did, you'd have a better response than, "You're stupid."

      Okay fine, you get flustered, and can't come up with a quick rebut, but your passion got inflamed and so you shot off something without really thinking it out. Okay, fine. You didn't have to respond right away. You could have waited until you came up with something good, you know totake advantage of stairwell wit, but whatever. The passion was too much. It happens to us all. No harm done. (And sadly in this case, less harm than usual.) But you didn't even take the time to come up with something original. Now there's just no excuse for that. Have some decency man! If you need help coming up with something original, I suggest you take some classes in creative writing.

      Now that my good man, is how you flame someone.
    20. Re:Volunteers are not slaves. by fluffy99 · · Score: 1

      I did read what you said. Contrary to popular belief, rapidly rolling out patches or fixes is not always in the best interest of corporate level software. Without proper regression testing, you introduce a non-trivial risk that you will break something else. People scream bloody murder when MS rolls out a hasty patch that later causes a problem. Why is this any different?

    21. Re:Volunteers are not slaves. by cthulhu11 · · Score: 1

      The myth here is that with commercial software you can demand all you want, but the vendor knows that, by and large, A) They already have your money and B) You're more likely to stick it out with their crap than abandon your inve$tment and admit to your employer that you made a bad choice There are some few exceptions - I've seen maybe two in the last 20 years. I've also seen freeware/OSS/whateveryoucallitthisweek leave users high and dry on occasion, but for the most part my experience has been that I stand a much better chance of something being fixed (faster, or at all) if it's freeware. I also have a much, much better chance of not having at least one of the platforms I use it on desupported because the vendor lost interest in compiling it there. I've worked for several software companies and one system company who provided a *ix OS. I've never seen anything to indicate that code quality for popular freeware packages is any lower in quality than the commercial stuff. I've seen -- intimately -- commercial code that was so incredibly awful that I was ashamed to be associated with it and couldn't believe that anyone (including a certain verrrrry well-known company you know who bought into it in a big way) would buy it.

    22. Re:Volunteers are not slaves. by Listen+Up · · Score: 1

      No, that's not entirely true. It depends on what you are talking about. As a little background, I am a Java software developer at an enterprise consulting firm on the East coast. I develop Java applications on OS X using Eclipse and NetBeans targeting Windows/Linux/OS X/Solaris/AIX/etc.

      My experience with open source software in the enterprise has really shown two things:

      1) Open source software development is extremely well received and highly sought after. With Java development, for example, almost all of the development software is %100 open source with the exceptions of some of the work with BEA WebLogic and IBM WebSphere. The open source Java development libraries are absolutely world class.

      2) Linux and open source software is general is extremely popular, and generally highly sought after, especially server software like Apache, Tomcat, JBoss, etc. All of the major commercial enterprise software that is supported natively on Linux is extremely popular as well including DB2, Oracle, BEA, WebSphere, etc. This is for a number of reasons including cost, scalability, reliability, security, etc. But none of the Linux installations I have seen in the enterprise have been the freely downloadable installations of Linux. All of the Linux I have seen in the enterprise is RedHat Enterprise Linux or Novell Suse. This is because those versions of Linux come with Enterprise Support with someone available by phone 24/7 to take support calls/requests/fixes/etc.

      So betting very serious business on Open Source, whether you are an IT manager or software developer, makes a lot of sense for a very large number of reasons. But lack of enterprise support is not one of them.

    23. Re:Volunteers are not slaves. by DavidTC · · Score: 1

      Almost all 'leaks' in Firefox are extensions.

      And people who insist on using the leaky ones, or who have leaks without them (Which does happen.), need to get the damn 'Restart Firefox' extension, turn on sessions, choose that every four hours or so, and STFU.

      Seriously. It's not a Firefox problem, because, if it was, it would happen to me. I, like the parent, keep Firefox open almost all the time, with dozens of tabs and four or five windows, and have never had Firefox go above 100 megs. (It usually hovers around 60, but I have a lot of extensions.)

      --
      If corporations are people, aren't stockholders guilty of slavery?
    24. Re:Volunteers are not slaves. by mha · · Score: 0

      I guess you mean "ad hominem"?
      http://en.wikipedia.org/wiki/Ad_hominem

    25. Re:Volunteers are not slaves. by sowth · · Score: 1

      That's sad. That's really sad. It's a stock response.

      Yes, it is really sad that some people write total crap posts that don't deserve anything more than a stock response.

      BTW, many open source projects have two branches. A stable and developer. If you are using the stable branch, you will only get bug fixes and minor feature improvements, not highly experimental untested development code.

    26. Re:Volunteers are not slaves. by Anonymous Coward · · Score: 0

      Excuse me? You can demand that commercial vendors actually fix their products? What have you been smoking? Go tell MS that you demand they fix some of the thousands of bugs in Office or XP because you "paid for the software". I'm sure they'll get on that right away for you. I know! They probably don't know about the bugs because no one has reported them yet! Pllleeaase!

    27. Re:Volunteers are not slaves. by coaxial · · Score: 1

      Any code checked into a branch needs to be tested. Arguably the code in the stable branch needs to be test more (especially with regards to regressing), since people are actively depending on it. It is highly doubtful that the all the required testing could be completely so quickly.

    28. Re:Volunteers are not slaves. by petermgreen · · Score: 1

      At least with proprietary software you have the right to demand that things get fixed
      ROFL

      if you buy ordinary grade licenses for off the shelf propietry software you get no such thing.

      if you need that level of support gaurantee you are going to have to buy it seperately regardless of if the software is opensource or not.

      and if you don't get what you want then you can find an alternative.
      you can do that with OSS too.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    29. Re:Volunteers are not slaves. by rjstegbauer · · Score: 1


      Excellent post!

      I was going to post that exact sentiment, but then realized that I was two days late.

      Good Job,
      Randy.

    30. Re:Volunteers are not slaves. by Anonymous Coward · · Score: 0
      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?

      OK I have one for you. Let's say that a situation arises as you describe, where a company has chosen OSS over some closed source app that costs big bucks to licence. Then, to their horror (*gasp*) there is a bug in the software. Oh noes! Well, with OSS they have a choice. Firstly, they can ask the original developer to fix it. If the developer isn't interested, then they can move on to option two: spend some of the money they didn't spend on licences paying a developer to fix it for them. Wow. Problem solved, money saved.

      Now if they went closed source, and found a bug, what options do they have? They can whine at the supplier, but they are basically at their mercy. I've had to deal with software suppliers in the commercial world, and they can be very unresponsive when it comes to fixing bugs. Even when it is their single largest customer complaining!

      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

      And what if moving to that alternative means abandoning a multi-million dollar investment in software and man-hours? Is it realistic to spend another few tens of millions buying, installing, migrating and testing software with near-identical functionality as the one you already have, just because your current one has a bug?

      Running to a new software supplier when your current one is slow to fix bugs may be realistic for small companies with limited investment in licences, training and support. However, a large company that has software which is in constant use by thousands of its employees is very unlikely to abandon such an investment on a whim. To get them to switch, there would have to be a major, major bug causing a measureable impact to their bottom line, and the software suppliers know this all too well. They know they have their customers over a barrel, which is why they can get away with being unresponsive.

      With closed source programs as a critical part of your business, you have less options when you run into problems than if you were running OSS.

    31. Re:Volunteers are not slaves. by Shads · · Score: 1

      I use it on linux but not the way I use it on windows. So you may well be right about the linux side of firefox, but I don't use it in a way there that would cause anything like you're experiencing... but my windows usage should, and it doesn't... so I'd guess at least one branch of firefox isn't leaking like that and perhaps that is where the reluctance to "fix it" is coming from... its not a universal issue.

      --
      Shadus
    32. Re:Volunteers are not slaves. by Shads · · Score: 1

      > Most of the time by the time we discover a problem exists there is a newer version of the software out already fixing the problem (we run a few versions behind the most recent version usually.)

      Really can't read can you. Remedial english for you.

      --
      Shadus
    33. Re:Volunteers are not slaves. by Shads · · Score: 1

      *yawn* I would have cut and pasted but slashdot won't let you do that. Since neither person could be bothered to actually READ what I wrote... why should I bother with them? I have already replied and pasted the relevant portion to one of the people above and it applies to the other also. Why take the time to write a logical well thought out response when people can't even bother to read your original post before making shit up and pulling it out of their ass as to what was said. Genius.

      I'm hardly flustered, it's just not worth the time. End of story. If that is a flame, I'm sorry for your personal state of being... I'd call that pathetic for a flame at best... go hang out on usenet for 10-15 years and then get back with me when you actually have an idea how to write a flame.

      --
      Shadus
    34. Re:Volunteers are not slaves. by coaxial · · Score: 1

      I had no idea that /. prevented you from using your mouse to copy and paste.
      I had no idea that /. prevented you from using your mouse to copy and paste.
      I had no idea that /. prevented you from using your mouse to copy and paste.
      I had no idea that /. prevented you from using your mouse to copy and paste.
      I had no idea that /. prevented you from using your mouse to copy and paste.

      And it is oh so hurtful when you start with "*yawn*". Way to go Napoleon. You've certainly proved that you've got nothing to prove.

  81. On "Hidden 3rd-Party Cookie Options" by BenoitRen · · Score: 1
    Firefox has always been about controlling your information: what goes in and what goes out has traditionally been left up to the user. But with Firefox 2.0, the Mozilla Foundation obviously decided that users couldn't be trusted to safely decide for themselves whether or not they want to enable the installation of 3rd party tracking, advertising, and adware cookies on their PC. Now users have to navigate to a hidden options page few know of to change that.

    Those options were removed because they never worked reliably in the first place. So the developers though it best to remove them instead of instilling a false sense of security.

    And since I'm replying about the article already...

    however it seems that the Mozilla Foundation has forgotten what gave it its initial boost: people looking to get out of Microsoft's Corporate world

    The article's author probably forgot that Firefox and Thunderbird are now in Mozilla Corporation's hands. Mozilla Foundation is the home of all the other projects.

  82. I'm asking for a troll mod here, but... by ixnaay · · Score: 1

    I was a relatively early adopter of Firefox, I liked it because of the multiform support, tabbed browsing, etc. I have a triple boot system, with Vista RC2, XP, and Mandriva - and Firefox 2.0 has been crashing/hanging within minutes of any browsing session, with no discrimination for the platform I am on. Needless to say, previous versions didn't have the issue. I have a psychical aversion to downgrading (I'm American, we aren't trained for that kind of thing), but I guess I will have to go back to 1.5 soon. I have also found myself using IE or opera when I am doing something that I really don't want to lose.

    I'm a EE, and I know enough coding to break stuff, and piss off the CS dept., but I have no desire whatsoever to debug a browser. With that in mind, I've seen, as have the rest of you here at /., a major push to get everyone possible using FOSS. So here's my point - The community can't have it both ways with FOSS:
    1: Either this type of software should only be used by those who have the ability and/or desire to fix what is or could become broken
    or
    2: the community, having pushed the use of FOSS into the less-technical world, should take responsibility for what they have created and promoted.

    The reality right now is that the 'community' seems to want both - they want the market share - and they are very quick to run away when a product doesn't work as advertised - and don't try to say that Firefox in particular isn't advertised. Try searching for 'Firefox 2.0' crashes...Basically every response will lead you here.

    Since Firefox really is the poster child of the FOSS movement, they need to be very careful not to make Microsoft's case for them.

    1. Re: I'm asking for a troll mod here, but... by JacksBrokenCode · · Score: 1
      1: Either this type of software should only be used by those who have the ability and/or desire to fix what is or could become broken
      or
      2: the community, having pushed the use of FOSS into the less-technical world, should take responsibility for what they have created and promoted.

      Absolutely!

      It's amazing how many people in this discussion are quick to jump on the "why is he complaining about the first-run page?" argument while ignoring the cut/copy/paste bug argument. In this same discussion Firefox advocates have been quick to say that features have been added for some people, but any ignored features can be had with plug-ins and any bugs found should be fixed by the person who finds them. I've even seen a poster go so far as to suggest that people who want bugs fixed should might consider paying money for their browser.

      This immaturity is why I have trouble supporting many community based projects. Shiny new features get the focus over bugs, and then the users that were wooed so emphatically to the software are told to stop complaining since they don't pay-for/contribute-to the project.

    2. Re:I'm asking for a troll mod here, but... by bitbucketeer · · Score: 1

      Firefox hanging/crashing soon after startup? Have you tried running it in "safe mode" just to ensure that the fault is Firefox's and not some poorly written extension's?

  83. Gimme some of that crack. by alexborges · · Score: 1

    I mean, damn. How in hell do you figure that?

    I had the best possible user experience with firefox since the 2.0 release than ever before with a mozilla product.

    I farking love the browser.

    Keep your greasy paws off my fox.

    --
    NO SIG
  84. Coral Cache by LordSnooty · · Score: 1
    Fatal error: Out of memory (allocated 3670016) (tried to allocate 98304 bytes) in C:\Inetpub\wwwroot\blog\wp-includes\category.php on line 104

    Well, that's different. If I wasn't so lazy I'd try and make a joke about Firefox memory leaks at this point.

  85. Re:why does it have to be so damn slow under linux by Droid+Rot · · Score: 1, Informative

    Are you running Firefox on a new version of one of the more popular distros? I have noticed some newer distros are running services which you may not need (dare I say bloat). Also KDE 3.5 is more graphic intensive than previous. Whilst I've noticed Firefox takes longer to load up under Linux, I have not observed Firefox *run* slower on my Linux boxes than my Windows box, and my Linux systems are older (and slower) hardware.

  86. Faster than IE, slower than Opera by Skeith · · Score: 1

    Firefox may be one of the most popular open source projects, but that does not mean it can implement features as fast as other browsers. Its developers are still comprised mainly of volunteers. When Firefox 3 comes out (Q2/3 2007) it will be a huge step forward from firefox 2, but how many steps forward will Opera have taken by then? If the nightlys are any indication, then Firefox 3 will be on par with Opera 9 in terms of speed and memory usage.

    Lets just assume IE doesn't exist, but another browser I didn't mention is Konquerer. From what I've heard it will be avaible on OS X and Windows when KDE 4 is released.

    Competition is good

  87. Fireefox? There are better alternatives.. by DandyRandy · · Score: 1

    OK, guys, to tell the truth: in former times, for me it was FF, Konquerer and Opera, when I fired-up my boxes under the Linux. It was FF and Opera, when I fired-up any of my boxes under Windo$e. Now the situation has changed, and FF is completely REMOVED from my boxes! under the Wondow$, IE7 definitely beats the sh_t out of FF, which (FF) is relatively slow, clumpsy, and I had problems with memory usage already at FF 1.5. My recommendation for Window$: definitely IE7.0 (by the way, there is very nice free tool available to import all of your FF bookmarks into the IE7.0), for Linux - Opera and Konq. No FF!

  88. Re:JESUS FRACKING CHRIST by istartedi · · Score: 1

    Sometime around 2016, modern English usage was revised so that "its" was used in both cases, and the reader deduced the meaning from context. By that time, most scholars were in agreement that this was accepted usage. At least, that's what John Titor told me.

    --
    For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
  89. Anti change by infofc · · Score: 1

    When you have only have a small market share, it is generally not a good idea to avoid changes that will attract new users in order to try to not inconvenience existing users. The change to tab UI is a response to the experience of having a lot of tabs open.

  90. Why I reverted to FF1.5 almost immediately... by The+Last+Gunslinger · · Score: 2

    I couldn't have cared less about the default theme or first-use page...seriously, people, grab a clue regarding priorities.

    However, after a couple days' usage, I found two issues in FF2.0 that led me to uninstall it and go back to FF1.5:

    1 - Broken "back" browser function:
    Basically, when I hit the "back" button, I expect to be taken not only to the page I was previously viewing, but to the same location of that page. With FF2, every time I use the "back" button, I get taken to the top of the previous page. Extremely annoying.

    2 - Reduced image filtering function:
    This one was (and still is) my favorite feature of Mozilla/Firefox 1.x. I like the ability to select the content checkbox that displays images ONLY from the originating website, with the exception of my personal whitelist. That checkbox vanished in 2.0, and this alone was enough to make me uninstall it.


    While these may sound like trivial issues to some, they're a major component of my everyday end-user experience with a browser...and FF 2.0 offered nothing in the way of improvements that would even come close to offsetting this setback to my experience.

    1. Re:Why I reverted to FF1.5 almost immediately... by Tatsh · · Score: 1

      After a day of multiple memory leak issues (and still no updats even to this day!), I reverted to Firefox 1.5 as well. Plus my favorite theme is no longer being updated and it only works on Firefox 1.5. A few other plugins I use also stopped working (mostly ones that don't get listed at the main site). I got sick of it and I don't see what's wrong 1.5, unless you're a total moron.

      Lately though I have been wondering what are the goals of the Firefox team. If Firefox becomes the most popular browser, then the attacks go straigt to Firefox then, no longer IE. Then I might feel like definitely switching to something like Opera or Maxthon (I hear both are really good). I'm already starting to get this feeling. Firefox is as good as Google anyway, if you ask me [/sarcasm].

  91. Enough Opera! by Anonymous Coward · · Score: 0

    Opera can never reach the features and functionality that firefox+extensions is capable of! Opera is the most annoying browser ever:
    The widgets are a joke and frequently crash/hang requiring a restart or in some cases complete removal
    The autoscroll snaps to the center of the screen regardless of where I middle clicked
    It's ugly and bloated and the mail feature is slow and buggy compared to anything else I've tried (thunderbird, outlook, eudora)
    I doesn't have a Tab Mix Plus level of customizability
    There's no real alternative to the godlike extension NoScript
    Integration of download managers is poor and seriously inferior to Flashgot
    Shall I go on?
    Seamonkey is likely to claim the all in one internet suite crown in the future. They already have tab previews in the latest beta and advanced download manager functionality is on the way too. If it weren't for the killer firefox extensions I'd be using seamonkey right now (They might be compatible in the future based on information on their wiki)
    Opera belongs in mobile phones. End of story.

    1. Re:Enough Opera! by Ash-Fox · · Score: 1

      You forgot to mention there is a lack of browser synchronization too currently.

      --
      Change is certain; progress is not obligatory.
  92. What Short Memories We Have! by coaxial · · Score: 3, Informative

    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?

    1. Re:What Short Memories We Have! by BenoitRen · · Score: 1

      It was not a blunder. The rewrite was desperately needed. The source code that Netscape released was a complete mess, one that they couldn't go forward with.

    2. Re:What Short Memories We Have! by Nurgled · · Score: 1

      On the other hand, we can observe in IE6 and IE7 what happens if you progressively try to shoe-horn the latest tech into a rendering engine designed for HTML 3.2 tag soup. I think the new, CSS-based layout engine was a necessity, not a blunder.

      Of course, I don't think they should throw it all away and start again now. What they've got works well even if it is quite messy and buggy; at this point, it's time to refactor and fix the bugs, not throw it all away and start again.

    3. Re:What Short Memories We Have! by VENONA · · Score: 1

      "mozilla released the new layout engine, Gecko" sort of implies that Gecko was their work, while it actually came from KDE's Konqueror. Credit where credit is due. I recommend Konqueror as the more secure browser. There are a few sites which it doesn't deal with very well, and I keep Firefox around for those. But 99% of the time, Konqueror is my browser.

      --
      What you do with a computer does not constitute the whole of computing.
    4. Re:What Short Memories We Have! by Laur · · Score: 1

      No Konqueror uses KHTML, and is not related to Firefox, Mozilla, or Gecko in any way. Maybe you're thinking of Safari, Apple's browser which is based off KHTML.

      --
      When you lose something irreplaceable, you don't mourn for the thing you lost, you mourn for yourself. - Harpo Marx
    5. Re:What Short Memories We Have! by coaxial · · Score: 1

      No. Konqueror uses KHTML, which is used in Safari, not Firefox. Gecko is a mozilla project, and always has been.

    6. Re:What Short Memories We Have! by VENONA · · Score: 1

      You're right, and I was thinking of Safari, as that old debate on devs contributing back went through my mind as I was typing. That *definitely* was Apple, not Moz. But I also _thought_ I recalled seeing a setting to change the rendering agent--KHTML or Gecko. Can't find it now, though. It may have been on a different version of KDE and/or Konqueror.

      --
      What you do with a computer does not constitute the whole of computing.
    7. Re:What Short Memories We Have! by VENONA · · Score: 1

      You are correct. My bad.

      --
      What you do with a computer does not constitute the whole of computing.
  93. Swiftfox by Terminus32 · · Score: 0
    --
    http://nathanlindsell.blogspot.com/
  94. How about Kernel? by antdude · · Score: 1

    How does Kernel handle this situation when it got big like Firefox? Is the Kernel's sources messy, hard to maintain, etc.? Is it going losing its way too?

    --
    Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
  95. Re:It's (sic) got no apostrophe when its is a.... by enodo · · Score: 1

    Funny, but "it's" = "it is", not "it has".

  96. Re:It's (sic) got no apostrophe when its is a.... by Radak · · Score: 1

    Funny, but "it's" = "it is", not "it has".Consult your dictionary again. Both expansions are correct.

  97. If you want to get owned, use IE. by argent · · Score: 1

    OK, Firefox has some security design flaws. Installing extensions at the request of the remote site and asking the user if you want to install it, that's a mistake. There's been one vulnerability in this already.

    However, this is a TINY hole compared to what Microsoft exposes in IE with ActiveX. And you can simply not install extensions, or remove all the whitelisted sites, and you've closed it. You can't turn off ActiveX because the HTML conrol is itself an ActiveX component!

    It's like the difference between not washing your hands after using a public lavatory, and running barefoot over broken glass through a "Hot" ward in a Michael Crichton disaster epic snogging the Ebola patients.

  98. Haven't we forgotten something? by yoz · · Score: 1

    It's typical that this thread devolves into a fight about which language gives you cleaner and more understandable syntax, or whether it's just down to "elegant code" as if that's the main problem here. Want to make your code maintainable and understandable? Here's the big secret you've been overlooking:

    Comments.

    The sad fact is, the vast majority of open source code may as well not be open, given the impenetrability of it all - mostly written by losers who have convinced themselves that they write "self-documenting code" (*cough* bullshit). There is no such thing as self-documenting code; even if you use Literal Programming techniques (which not nearly enough people do, and which help a great deal) you still need to put actual line comments in.

    The last time I dove into Mozilla code was to try and fix a long-standing complaint I had with (what was then) Mail & News. I was dealing with a JS file, not even their horrific C++ (which has been described as "not so much C++ as a whole new language that a C++ compiler happens to be able to deal with". After grappling for an hour with a huge and totally uncommented file, I gave up and never went back. It's a shame, as I'd love to be able to contribute.

    1. Re:Haven't we forgotten something? by Anonymous+Brave+Guy · · Score: 1

      There is no such thing as self-documenting code; even if you use Literal Programming techniques (which not nearly enough people do, and which help a great deal) you still need to put actual line comments in.

      But you don't need very many of them. If your code uses a clean design and descriptive names in the implementation, then what your code is doing (from a low level perspective) should be pretty obvious to anyone who already understands the high level design and the overall goals. The latter things are what comments (and design docs, etc.) are for.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    2. Re:Haven't we forgotten something? by ErroneousBee · · Score: 1

      Your approach might not be that useful. Your descriptive names are probably only decriptive to you, or are so long that the code becomes unreadable. You also have a weird belief that design documents bear any resembelance to the code.

      I find about 1 comment line for every 10-20 lines of code is about right, and make sure the comments are a level of abstraction higher than the code, E.g. Dont comment that you are opening a file, comment why you are opening that file (E.g. /* Open the inbound configuration file for parsing */)

      Ive seen people go to both extremes, to the point of commenting that return statements will be returning, folks using 60 character variable names, folks who never write a single comment, and one particularly annoying individual who would tell me in the comments exactly what was in the next line of code, on every line of code, no matter how trivial, in boxed comments.

      --
      **TODO** Steal someone elses sig.
    3. Re:Haven't we forgotten something? by Anonymous+Brave+Guy · · Score: 1

      Your descriptive names are probably only decriptive to you, or are so long that the code becomes unreadable. You also have a weird belief that design documents bear any resembelance to the code.

      I think you prejudge too much.

      For one thing, it is common for members of my team to ask for a quick second opinion on naming conventions if there's any doubt about what the most descriptive terminology would be or what others might understand. This takes all of ten seconds at the coffee machine, so it's hardly some huge burden. Things like code review (formal, informal, pair programming, however you do it) also help with this. So in fact, I'm pretty sure that the naming used by myself and my colleagues is generally descriptive.

      I have no idea where you get that idea about long names. Descriptive does not imply long. On the contrary, IME many of the best variable/function/type names are remarkable more for their conciseness than their verbosity.

      Finally, if your design docs don't reflect reality, then you have either the wrong information in them or the wrong procedures for maintaining them. Our design docs are integrated with the source code using tools like Doxygen, and reflect the high-level design for each area of our code. Someone new to an area could read the design doc and then use that as a starting point for browsing the code to explore the detailed design, which is described by the comments and conventions within the code itself. I agree 100% that huge, "print out all your class diagrams as they were three years ago" documents are an almost complete waste of time, but they are hardly the only way to do it.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    4. Re:Haven't we forgotten something? by ErroneousBee · · Score: 1
      I think you prejudge too much.

      Perhaps I did, I assumed your design docs were of the "word docs that nobody actually reads" type and your descriptive names were "MQ065_Quicker_info_from_source_data_definition()"

      Getting into the code written at this place is a lifetimes work. No useful docs, no literate programming tools, comments are either absent or useless, the only machine parsable comments are those I create myself. No-one uses any wiki tools to note how anything is done. And most of them retire in the next 5 years. Welcome to my (increasingly well paid!) world.

      --
      **TODO** Steal someone elses sig.
  99. Scenario by Anonymous Coward · · Score: 0

    It's like playing a game of Jenga (remember that game?). You start off with a solid, relatively small structure. As the game progresses the base gets weakened in some regards due to aged code and the newer stuff built on top. Eventually a renovation is needed to remedy the state of the tower.

    And that's kind of where Firefox is in some regards. In some regards it's very well kept. The main areas I think need fixing (I'm not a dev, just my guess from using the browser):

    1. Javascript implementation should be able to increase efficiency by at least 10-20%. Obviously some of the sluggishness of the JS engine is due to poor scripts in the wild, but some is due to an engine that needs some tweaking.

    2. Rendering could be a little faster and has a little ways to go to meet perfect standardization. It's damn good though.

    3. Memory use is still a little twitchy. This is the hard one because it's one of those things where the best way is the hardest way: you strip the code down to the essentials and optimize the hell out of it, then add one module/component at a time and build up from there. This would be a major undertaking, but ultimately this is how the west is won. If someone could make this easier it would make most software a hell of a lot better.

    And that's what I have to say.

  100. Re:Maybe they already accomplished what they neede by trifish · · Score: 1

    Firefox's popularity finally shamed Microsoft into updating IE.

    I keep reading that, but there's not proof for that whatsoever. On the contrary: It can be easily proven that Microsoft released a major upgrade of IE with each major upgrade of Windows.

    Windows Vista + IE7.

  101. Re: Important Releases by TaoPhoenix · · Score: 1

    I briefly glanced at the V1.0x series of Open Office, tried to convince myself for an hour "I should be using this, it's Open Source!", ... and turned away.

    Life trudged along, and I happened to spy the late Betas and now public release of V2.0x and I like it. A couple quirks take getting used to, one of which may inspire me to submit a bug report if I can find the time to prove it's (spelled correctly!) not a duplicate.

    I've never been an early adopter. I like to scout the workings, then bury myself working on my projects. By the time I emerge three months later, someone has often fixed the worst of the heart-attack inducing bugs.

    --
    My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
  102. Re:Solution by Trogre · · Score: 1

    Hey, it seems to work just fine on Mac OSX :)

    --
    "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
  103. Honestly, I don't get it at all. by aussersterne · · Score: 1

    I'm using Firefox 2.0 (well, Swiftfox 2.0) since right after release and I've had:

    1) Not a single crash
    2) Not a single OOM condition
    3) Great performance
    4) Not obvious compatibility problems or renderfux

    In short, the transition was seamless, the browser is faster than it used to be, all of my plugins and themes came across great... I wonder if maybe some in the tech community aren't making out the "horribleness of Firefox 2.0" to be a much bigger issue than it is. Frankly, I like it a lot, and it hasn't pushed me back to Konqueror yet (which all Firefox releases before 1.5 eventually did).

    --
    STOP . AMERICA . NOW
  104. Re:JESUS FRACKING CHRIST by HeroreV · · Score: 1

    People are wasting alot of time on this. Your going to loose the battle anyway, so why bother? Their's just no point.

  105. Re:why does it have to be so damn slow under linux by wolf08 · · Score: 1

    Weird.... I'm sitting at home here at my gentoo system. I have compiled FF 2.0 from source, and the dojo fisheye is EXTREMELY slow. On a VM windows xp running under this same gentoo box, the fisheye demo is almost as smooth as my kiba-dock (fast).

  106. Re:Solution by HeroreV · · Score: 1

    "fabulating"? "fabulations"? You're certainly enjoying your day-to-day calendar, aren't you?

  107. That's a big "DUH" by Anonymous Coward · · Score: 0

    I think Firefox lost it's way when it got it's name. Give me back Firebird... that was a great browser.

    Mark me as a troll, I don't care. That's how I feel.

  108. Re: Important Releases by Ash-Fox · · Score: 1
    I briefly glanced at the V1.0x series of Open Office, tried to convince myself for an hour "I should be using this, it's Open Source!", ... and turned away.
    OpenOffice.org 2.0.4 is out. I feel it is much better than v1.
    --
    Change is certain; progress is not obligatory.
  109. Leak Monitor by towsonu2003 · · Score: 1
    Leaking? Try the "Leak Monitor"[1] extension... And I wonder if it's really working.

    [1] https://addons.mozilla.org/firefox/2490/

    1. Re:Leak Monitor by Blink+Tag · · Score: 1

      The extension is designed to catch one very specific type of leak (chrome/extension leaks). There are many ways to leak memory, and this extension won't catch most of 'em.

      (I have the same problem as the parent, btw).

  110. I have two main complaints about Firefox 2.0 by Master+of+Transhuman · · Score: 1

    Well, 3, really, since I agree with the author that the look is worse - but that doesn't particularly bother me, as I'm not interested in "eye candy". If I can read the screen text and figure out the buttons, I'm satisfied.

    My two main complaints are:

    1) Firefox's "Save Link As" is utterly broken (on Linux under KDE anyway - I think it works on the Windows version). Try to download anything from many different Web sites and you get spurious errors back from the Web site - including the notion, from Rapidshare, that you're "already downloading a file" or you've just submitted the wrong CAPCHA- or it just downloads a few bytes or no bytes. Utterly broken. I've had to install DownThemAll and use it to be able to download anything. ("Save Image As", however, still works fine, so I can still get my babe pictures from Superiorpics.com.)

    2) Now that I'm still able to "Save Image As", as noted above, I run into: memory leaks - save dozens of images and wait for Firefox to slow to a crawl or start manipulating the save dialog weirdly (fixed under KDE by forcing the windows to a specific size and shape). C'mon, guys, MEMORY LEAKS? This is the 21st Century! We still have people not checking for properly allocated memory? The guys at Mozilla just graduate from Programming 101 - Introduction to Programming with BASIC?

    And this has been true since Firefox 1.0. The author of the article under discussion mentions a cut and paste bug which I'm not sure I've seen myself, but he notes this bug is FOUR YEARS OLD. Add the memory leaks to that.

    The screwups in 2.0 forced me to install Opera 9 as an alternative browser (and occasionally use Kongueror as well). I haven't used Opera since I think 5.7. Now that's free with no ads, I figured I might as well try it. It's STILL the fastest browser in the business, noticeably faster than Firefox or IE7. And while it has bugs (ALL software has bugs), they aren't show stoppers for me like Firefox 2.0's are.

    What really bugs me is that problem number one above CLEARLY shows that Firefox 2.0 simply was NOT TESTED adequately. Since I've just had major problems a few weeks ago with Mandriva 2007 and SUSE 10.1, forcing me to switch to Kubuntu 6.06 (and IT had a problem with its installer), it is now VERY clear to me that Linux and OSS in general is in danger of being held back by incompetent design and very inadequate testing.

    The distros and OSS projects are expending their limited manpower and resources into doing things like putting more eye candy into Linux (with Compiz and the like - the problems with the official Nvidia drivers in MANY distros are becoming legendary, since everybody wants "3D shaky windows", for some bizarre reason - I had to uninstall them on my machine after I lost my desktop and other instabilities) rather than putting them into ensuring a rock-solid experience for the end user - which is supposed to be Linux's strong point against Windows.

    This is especially true in the installers. End users switching from Windows to Linux need to be shown UP FRONT in the installation process that Linux is better. Screwups like Kubuntu's inability to leave the mount point modification screen are simply unacceptable.

    Screwups like SUSE 10.1's update "patch" that screws the entire software update process are also unacceptable. Software update is a considerable weakness in Linux right now (with the possible exception of Synaptic) and the entire process of setting repositories and downloading updates needs to be totally automated and rock solid if we expect Windows users to be able to use Linux.

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  111. Delete this! Fuckheads. by Anonymous Coward · · Score: 0
    I can't be bothered to type out my criticism of themes, extensions and javascript for the THIRD TIME.

    So just go ahead and delete this post you narrow minded shitheads.

    From the FAQ:

    Will you delete my comment?

    No. We believe that discussions in Slashdot are like discussions in real life- you can't change what you say, you only can attempt to clarify by saying more. In other words, you can't delete a comment that you've posted, you only can post a reply to yourself and attempt to clarify what you've said.

    In short, you should think twice before you click that 'Submit' button because once you click it, we aren't going to let you Undo it.
    http://slashdot.org/faq/com-mod.shtml#cm150

    Why did my comment get deleted?

    The only time we ever delete comments is if the comment contains malformed HTML that is somehow causing Slashdot to fail to display properly. Comments are not deleted on the basis of content. At this point, however, it shouldn't be a big worry. The comment engine is reasonably bulletproof, and it's pretty tough to post a comment that breaks Netscape.

    If you posted a comment and you don't see it now, it may have been moderated down below your threshold (see below). If you set your threshold to -1, you should be able to see it again.
    http://slashdot.org/faq/com-mod.shtml#cm200

    PURE unadulterated BULLSHIT!

    My last two posts on this subject were both deleted, neither contained malformed HTML (they only used the blockquote tag as in this post).

    My posts were deleted because slashdot editors did not like what I was saying.

    So if you do not want your post to be deleted then do not criticise the concept of software themes, extensions or javascript, slashdot editors are highly offended by such criticism for some reason.
  112. Re:JESUS FRACKING CHRIST by The+Hobo · · Score: 1

    It's still not a license to write things the wrong way, nor an excuse for poor language skills. French is my first language and I know the difference between the two and employ the words correctly. If you forced yourself to get it right a long time ago, by now it would come naturally and you wouldn't have to think about it. As I say to all the anglophone apologists: if you're not good in your only tongue, then you're not good in ANY language.

    --
    There is another kind of evil which we must fear most, and that is the indifference of good men. -- Boondock Saints
  113. Mozilla better than firefox ever was or will be by Anonymous Coward · · Score: 0

    My title says it all. I use Mozilla and will continue to do so. I will never willingly use firefox for long...not enough ability to control malware, toolbars, cookies, javascript, java, etc. that has long been the forte of Mozilla. Mozilla under SuSE linux 9.0 really rocks, as anything that the browser happens to download can be utterly obliterated by SuSE 9.0's shredder under its kernel 2.4. Kernel 2.4 is far better than kernel 2.6 simply because of the presence of the shredder function, far and away the most important function of the operating system. All other functions pale to insignifigance. Defenders of weak security browsers like firefox and non secure browsers like 2.6 deserve all the malware they get and cannot get rid of, for it is they that sold out the linux consuming public for money from the monopolies like micro$$$.
    Everything that they say should be considered in the light of their lightweight character.

  114. False. by FunkyMarcus · · Score: 2, Informative

    First, that bug didn't make Firefox "almost" unusable by any stretch. The old code (which was a lot older than two years, by the way) spun a busy loop when you held the mouse button down. The worst-case scenario was that you'd rob some other process of a small amount of processor time during the infrequent periods when you'd hold the mouse button down for no other reason than to complain that this bug hadn't yet been fixed. Big deal.

    Second, the bug is in fact fixed in Firefox 2. I should know: I fixed it. You're welcome.

    1. Re:False. by beej69 · · Score: 1

      thanks, Mark!

    2. Re:False. by Monkelectric · · Score: 1

      It was a major pain in the ass and it *WAS* a big deal :) thanks for fixing it.

      --

      Religion is a gateway psychosis. -- Dave Foley

  115. The examples do not represent FF 2.0 by amalakar · · Score: 1

    The small set of examples do not represent what firefox 2.0 has to offer. Morever these examples are more about visual aspects, where it is not always possible to please everyone. I like the new default theme very much, and users always have the option of installing themes. What about dictionary feature and all, which comes very handy in the Web 2.0 era where users generate lots of content. What I don't understand is, what disliking some visual aspect or features have to do with the *policy changes in Firefox 2.0*.

  116. Quantity does not imply Quality. by Anonymous Coward · · Score: 0

    As the old saying goes, quantity does not imply quality.

    Yes, there are a lot of extensions. Some are useful, but the vast majority are pure shit. They're not only "shit" in the sense that they don't perform the functionality they should, but "shit" in that many of them leak memory like there's no tomorrow. Even just one poorly written plugin can take down your Firefox instance by excessive RAM consumption alone.

  117. You have obviously never used Konqueror. by Anonymous Coward · · Score: 0

    1) Konqueror has far better CSS support than Firefox
    While Firefox 2.0 is still unable to pass the Acid2 test, Konqueror has been able to successfully pass it for a number of versions. I know you'll say that the Acid2 test doesn't mean much, but it actually does. It means that Konqueror has long had additional CSS support that even the most recent production release of Firefox does not offer.

    2) Konqueror is fast.
    Firefox has too many layers when it comes to rendering basic GUI widgets. The whole JavaScript, XUL, Gecko, GTK+, GDK (or Cairo), Xlib stack commonly used is slow. Konqueror, on the other hand, eliminates the excess layers. Being directly coded in C++, it only must pass through Qt when rendering. With such rendering code being compiled to machine code, and then passing through far fewer layers than with Firefox, improves the speed greatly.

    3) Konqueror consumes little memory.
    While it's not unusual for a Firefox process to balloon up to consuming hundreds of MB of RAM after a typical browsing session, Konqueror rarely goes above 40 MB. While even that is significant compared to Opera, it's often an order of magnitude less than Firefox's RAM consumption. On machines with only 512 MB of RAM, a Firefox process requiring 700 MB of memory can lead to some pretty awful thrashing.

    4) Konqueror supports virtually every website.
    I personally have never found a site that does not work perfectly with Konqueror. And any time I've seen somebody claim that there is a problem, they almost never produce a link to said site. If they do, that site has always rendered just fine using Konqueror.

    5) Konqueror is portable.
    Konqueror runs flawlessly on Linux, FreeBSD, OpenBSD, NetBSD, Dragonfly BSD, Solaris, HP-UX, AIX, Mac OS X, and even Windows (using Cygwin). The upcoming release of Konqueror included with KDE 4 will be natively ported to Windows, so Cygwin will no longer be needed.

    6) Konqueror extensions are written in C++.
    Konqueror extensions are written in C++. While this may not appeal to the Web designer who thinks he can be a programmer and write plugins, it turns out to be a good thing. You don't want any old schmuck developing plugins for a Web browser, especially when that browser is used to view potentially-hostile Web sites. You want extensions that are written by somebody who knows what they're doing, and the barrier of C++ is often enough to vastly improve the quality of the plugins that are written.

    7) Konqueror extensions are stable and do not consume excessive RAM.
    The extensions that do exist for Konqueror are of a very high quality. Unlike Firefox plugins, they don't crash your browser session. Likewise, they don't leak memory like there's no tomorrow.

    I know you'll have a difficult time accepting many of these points. But the fact of the matter is that Konqueror has proven itself to be a superior browser to Firefox. In virtually every aspect it is either better performing, of a higher quality, or a combination of the two.

  118. Re:why does it have to be so damn slow under linux by beej69 · · Score: 1
  119. It's not "It's" by bidmead · · Score: 0, Offtopic

    Please, guys, this is starting to drive me nutty. The problem's endemic on the Web, but this particular post has it in Spades.

    "It's" when it's a contraction of "it is".

    "Its" when it's a possessive.

    Was that so tough?

    Thank you.

    --
    Chris

  120. Advice to Mozilla: by crhylove · · Score: 1

    I don't really know what 3.0 is going to be all about. I really don't know why everybody is SO up in arms about the lack of quality in FF .3-2.0. I've been using it the entire time (yes, I know it was called Phoenix back then), and frankly it is and has been since that day: The best Browser available for the Windows Operating System.

    Having said all that, though, I do feel the gripes that some users are having, and I agree with them to a certain extent, so I'm going to give Mozilla a piece of free advice, call it even for all the free code you've given me over the years!

    Just clean the hell out of it. Go through the code line by line, clean it up, fix every bug, and don't add a single thing but speed.

    FF 2.0 is awesome. It's got spell check, and all the things that made FF great up to today, to boot. Now just fix the god damned memory leaks, fix the other security problems, make the code better documented and easier to read, and maybe make a couple of extensions like Adblock and Filterset.G automatic, since we're all using it anyway. Or don't bother, I'll install them myself later.

    But seriously: I don't want ANY new features. Hardly ANYBODY DOES. Be the best browser there is on speed and security, and worry about new features after some other browser.

    Thanks for all your hard work, and keep it up. Here's to the future clean/fast FF browser!

    rhY

    --
    I hold very few opinions. I hold information based on observation and fact. If you wish to disagree, please use facts.
  121. Wow - Firefox, a new sleek and efficient browser?? by goldcd · · Score: 1

    Where would I get this from?
    www.mozilla.com y'say?
    *experiences feeling of deja-vu*

  122. Opera is developed by Soviet Union crackers by Anonymous Coward · · Score: 0

    and so not good idea from security point

  123. Confirms what I've seen... by petrus4 · · Score: 1

    I don't know much in the way of specific details, but what little I've seen from Firefox's Bugzilla have suggested to me a deeply insular, elitist, foul tempered group of people with a tendency to be rather abusive of newcomers.

    Mind you, I didn't (and don't) support the Iceweasel fork, and I don't at all think that the Debian Project are in any way a better alternative. I've spent the last few days evaluating Ubuntu Dapper Drake. I have, however, never liked Debian as a distribution, its' "philosophy", or what I've seen of its' development group, so I'm not going to be keeping Ubuntu...when I get my other machine back up I'm going back to Linux From Scratch.

    I will be honest when I say that I'm close to the limits of my tolerance with regards to the Linux userbase more or less in general...the LFS people are the only group I've been able to stand being around for any great length of time. They are genuinely humble, tolerant, and altruistic...they help people who arrive on their IRC server with no questions asked...and they run a very solid project.

    I have a feeling that the LFS project's behaviour and atmosphere are what FOSS people in general have been *aiming* for...but that somehow it got lost when said people started developing an extremely over-inflated view of their own importance...the continually stoked, unreasoning terror of DRM also is not helping matters. As Linus Torvalds has said, nobody does good work from a basis of fear or hatred.

    As I've written previously, I primarily blame the FSF and the Debian people for the current predominant foul attitude among Linux's userbase...I am going to go back to WoW for a while, and simply wait. I cannot help but suspect (or at least hope) that eventually the fear, insularity, and vitriol that the FSF generates will eventually starve it of new converts.

    I am going to observe both the advice of the Tao Te Ching and a proverb that I have seen from Vampire: The Masquerade.

    "The best way to overcome an enemy is to outlast them."

    You are an old man, Richard Stallman, and I suspect that of the two of us, I have more years of life left. Despite the number of people ready to replace you when you go, rare is the cult that survives its' founder...the organisation in question is inevitably radically altered, if it does not fall completely.

    I will wait. When you and yours have gone, I will come back.

    1. Re:Confirms what I've seen... by NumerusSpy · · Score: 0

      I know what you mean about certain flavours of linux attracting undesirables. Like you I have found the LFS people a great and helpful crew. The Manriva channel on freenode also contains many great and helpful people (and of course the odd twit).

      --
      There they are a conga line of suck holes. On the conservative side of Australian politics. - Mark Latham
  124. Re:why does it have to be so damn slow under linux by biscon · · Score: 1

    now that is just sad..

  125. TEST POST by Anonymous Coward · · Score: 0

    Testing, testing, 1,2,3...

    Can you see this post?