Slashdot Mirror


IceWeasel — Why Closed Source Wins

engtech writes, "There's been some hype about the Debian fork of FireFox called IceWeasel. Politics aside, this is a bad idea because it fragments the user base, divides the focus, and opens the path for Microsoft and Internet Explorer 7 to regain marketshare."

21 of 551 comments (clear)

  1. Seamonkey by El_Muerte_TDS · · Score: 5, Insightful

    Just like how Firefox fragmented the Mozilla userbase?

    1. Re:Seamonkey by rolfwind · · Score: 5, Insightful

      But Firefox is installable on a ton of platforms.

      Ice Weasel sounds like it will be only installable on Debian, perhaps Debian-descended platforms like Ubuntu. Of course, since it's open source, anyone can port it to other platforms, I suppose. But why bother, all Ice Weasel is, is Firefox devoid of any nonfree trademarked art. And any updates to Firefox will be bought to Iceweasel.

      But there are already other variations of Firefox, like Swiftfox. Firefox will be the main flavor for a long time.

      The only way a fracture in the community will happen is if the releases are not compatible with each other, but the projects don't sound like they will develop on their own, but always staying with the main branch of Firefox. They can't really afford not to.

    2. Re:Seamonkey by Anonymous Coward · · Score: 5, Insightful
      How are sites slashdotted when nobody reads TFAs?

      It's not that nobody reads them. It's just that the intersection of (dotters who read the articles) and {dotters who post} is the empty set.

    3. Re:Seamonkey by djimi · · Score: 3, Insightful

      Interesting analogy, but I think it's a bit off. Text editors "create" text -- which all of them will see. There really isn't variation in the grand scheme of things. The differences are the keystrokes & interface that people like one way or another. On the other hand, a web browser is a content viewer, and the web is forever changing what we can and will see & hear. Text really isn't changing is it? Web "Compatibility" & standards of experience across platforms is the debate.

      --
      Vox et praetera nihil
    4. Re:Seamonkey by Schraegstrichpunkt · · Score: 3, Insightful
      Port? Debian is Linux.

      This isn't the 1990s. The "Linux distros" are now quite different from each other, and often binary-incompatible in some ways. Granted, it's very easy to port software between them (if you have source code, which you usually do), but they are most definitely different OSes now.

      There are (or will soon be) more similarities between e.g. Debian GNU/Linux and Debian GNU/kFreeBSD than between Debian GNU/Linux and Mandriva Linux or Fedora Core.

  2. Err by republican+gourd · · Score: 5, Insightful

    Exactly *how*, is Microsoft going to capitalize on a fracture of Firefox... within *Debian*? This doesn't touch the userbase that is competing with IE etc whatsoever.

    1. Re:Err by westlake · · Score: 3, Insightful
      Exactly *how*, is Microsoft going to capitalize on a fracture of Firefox... within *Debian*?

      "Iceweasel" is a name chosen out of pure spite.

      What kind of message do you think this sends to the small business and enterprise markets about the maturity of the FOSS community?

  3. My Thoughts on the Issue by AKAImBatman · · Score: 4, Insightful
    My first reaction to this entire situation is that, it's more complicated than it looks. On one hand, Mozilla doesn't want binaries being redistributed that they didn't build themselves. On the other hand, Debian wants to be able to handle source patches of their entire source tree. The result is that you get two competing ideals, both seemingly valid, creating this bit of a mess.

    After stepping back for a moment, however, I realized that the problem isn't as complex as it seems. In fact, I think it highlights something I've been saying for a while: Package systems under Linux are a broken concept.

    When I was working on the Linux Desktop Distribution of the Future article, I received quite a bit of criticism for calling the package management systems a major source of breakage. In the follow-up, I was forced to point out that complete system packaging creates a massive, monolithic code base:

    There is no way to fully test a package repository. Since every package modifies the base system, the only way to prove that a package will work is to test it against every possible package configuration available! In case you're wondering, the math for that is P * P, where P is the number of packages available. A mere 100 packages could potentially result in 10,000 available configurations! That's a lot of potential for breakage! Now consider that most distros today have thousands of packages under their care, and the number is not declining.

    Minor Correction: Reader Bradley Momberger has correctly pointed out that my math was a little screwy on this one. The correct forumla for the number of combinations is 2^P, which is actually quite a bit worse. 100 packages yields 1.26e30 possible combinations!


    What we're seeing here is a legal extension of that same problem. By integrating the software into the codebase, Debian is attempting to take legal responsibility for the software. Yet the software provider (Mozilla) is already handling that responsibiity, and does not wish to give it up. On any other operating system, the binaries would get bundled (or not at all, if they're too untrustworthy) as a self-contained application, and the software provider would be allowed to continue handling updates. End of story.

    In this case, Debian wants this software to be managed like all the other software they manage. Which means that taking responsibility becomes easier for them, rather than allowing the software producer to handle their own software. While this theoretically allows for a more cohesive system, that cohesiveness only goes as far as the packages checked into Debian's repository. Mozilla should be outside of that repository, but any software that's not in the repository is not well supported by the packaging system. Ergo, the process breaks down.

    That's just my thoughts, anyway. I'm sure many will disagree. Loudly. And rudely. Oh well. :P
  4. Ummm by bky1701 · · Score: 4, Insightful

    How does this make Debian users use IE?

  5. marketshare? by teslar · · Score: 5, Insightful
    and opens the path for Microsoft and Internet Explorer 7 to regain marketshare
    Pray, do tell me again, what exactly is the current marketshare of IE7 on debian?
  6. Re:it's bad either way by XanC · · Score: 5, Insightful

    Debian's goals are to quickly patch security problems, and to backport fixes to versions declared stable for the benefit of their users.

    Both these goals a) good, useful, helpful, and worthwhile, and b) in conflict with the wishes of the Mozilla Corporation.

    Perhaps Mozilla could give a little here, instead of Debian. Hmm?

  7. Re:Missing the point... Yourself by Anonymous Coward · · Score: 5, Insightful

    The Mozilla Foundation doesn't have a problem with Debian modifying FireFox. What they have a problem with is Debian modifying FireFox fairly significantly, yet continuing to call the product "FireFox". FireFox(tm) is a specific codebase, maintained by the Mozilla Foundation. I think they have every right to ask Debian to rename their fork, so that end users are not confused, thinking that bugs in Iceweasel are general FireFox bugs (in some cases, they may be, in other cases, not).

    I don't see anything wrong with asking someone who forks your codebase to use a different name to avoid confusion. What's the problem with that?

    Plus, there is this thing about Trademark law. If you don't actively police it, you can lose the right to the mark.

  8. opens the path for Microsoft... by joebooty · · Score: 3, Insightful

    "...and opens the path for Microsoft and Internet Explorer 7 to regain marketshare."

    This is a worthless mindset. The goal should be to release a good product that end users appreciate. Competition will make both products better.

  9. Re:it's bad either way by Al+Dimond · · Score: 4, Insightful

    As I understand it Debian does contribute patches back to Mozilla. But Debian wants to backport security fixes to versions of Firefox that Moz. Foundation no longer supports. I'm pretty sure this is true.

    As I understand it Mozilla used to let them call these versions "Debian Firefox" but now they don't anymore. I'm not entirely sure this is quite right. Also there's a DFSG issue that I don't remember the details of.

    Mozilla Foundation doesn't have to "deal with" Iceweasel at all, except to respond to all of this publicity. This looks "big-picture bad" to some people but to Debian keeping the stable branch secure is more important than Firefox advocacy. In other words, the "small-picture" disagreements that made this happen are actually the big picture.

    For most users there's not much of a reason to use package management for a program like Firefox. It's frequently-updated and for most people frequently-used, and it has an auto-update system if you use the official binaries. People will usually want the updated version. For people that have a good reason to stick with a really old version, or who don't use the browser enough to keep it updated independently of other software Iceweasel gives them their security backports. And I can understand why MoFo wouldn't want their trademark applied to software that's maintained by Debian.

  10. Re:Debian vs. Mozilla.COM by Bruce+Perens · · Score: 3, Insightful
    Right, Mozilla.com not Firefox.com .

    Of course nobody likes the name. You're not supposed to. It's Firefox turned on its head. It's supposed to be annoying to the Firefox developers, to spur them to do something about this.

    Bruce

  11. Polarising the argument by delire · · Score: 5, Insightful

    If it is to be renamed then why not do it with some reference to the reason. A name like FreeFox or similar would at least maintain symbolic connection to the parent while underscoring that it is a wholly non-proprietary distribution of that parent. 'IceWeasel' sounds directly antagonistic of FireFox itself. If FireFox is hot, then it's alternative must be cold. It itself reads as a childishly extremist 'reaction' to what should otherwise be understood as a wise and considered move, for real and sane reasons.

    The sheer lack of foresight amazes me. For years afterward we'll be hearing damaging myths that "FireFox doesn't install on Linux". Newbies coming into IRC to ask how to install FireFox will be pointed to what's later knows as the longest running $TOPIC in history. 'IceWeasel' just adds needless noise for all those millions considering switching to a Linux OS. FireFox is arguably the most important FOSS application for the desktop, if only because of it's notoriety. The name itself is larger than the software it represents. fscking with this reveals new depths of disregard for the adoption of Desktop Linux more generally.

  12. Re:it's bad either way by phoenix.bam! · · Score: 3, Insightful

    Debian aims to offer support for version of software that are in it's stable distro. Firefox 1.0.7 I believe is still supported by debian stable, yet mozilla has long stopped supporting it. Debian needs to be able to maintain a patch set to keep unsupported version of firefox stable and Mozilla is unwilling to budge on trademark enforcement (and well they shouldn't.)

  13. Re:This doesn't hurt Firefox by Anonymous Coward · · Score: 3, Insightful

    They could simply have moved it to non-free

    No they couldn't. The objective of the Debian Project is to create the universal free operating system. The existance of the non-free branch is a minor evil, and there have been discussions not too long ago to remove it.

    What do I care, I use Ubuntu. Debian is becoming the new XFree86.

    You sir are an ignorant. Read the words of Mark Shuttleworth when he says that I'm of the opinion that Ubuntu could not exist without Debian . Debian is a much bigger and important project than you think.

    I'm appalled that people detests someone or something for standing up for their rights and their freedom, I don't understand why.

  14. It is interesting how the dialogue has changed by Infonaut · · Score: 3, Insightful

    Just a few years ago we were talking about making sure Open Source software provided users alternatives to proprietary software. Forking has always been an issue, but the gestalt view seemed to be that ultimately even in a forking situation, the better software would "win" in the sense that it would continue to be developed. The focus was not on defeating proprietary software in the marketplace, but in making truly great software.

    Now it's 2006. Linux is a huge force in the IT world. Firefox has stolen marketshare from IE. These nibbles of success have changed the dialogue, and now marketing is as important if not more important than diversity. Choice is good and all, but getting computer users to make "the correct choice" is perhaps now the ultimate goal. Consumers may become confused by so many browser choices! Ah yes, let's not confuse them. Let's market and package Firefox so the choice will be clear.

    I understand the rationale for not forking Firefox. But that's a tactical issue in a small skirmish. The real war is about choice. I'm for it.

    --
    Read the EFF's Fair Use FAQ
  15. Re:Debian vs. Mozilla.COM by asuffield · · Score: 3, Insightful
    Debian wants to change the code-base of Firefox. Fine. allowed.


    I'm sorry, you lose. This is not allowed - unless you remove the firefox artwork and change the name, or submit to specific per-change licensing from Mozilla (which Debian's policies do not permit, for a number of practical and philosophical reasons). That is what Mozilla have said to Debian. If you do not agree with this, feel free to take up the issue with Mozilla, because Debian will presume them to be correct on any matters regarding what is and is not acceptable here.

    Debian wants to get a free ride


    This is not at all true. Debian has been saying to the Mozilla crew for a long time (since several years ago when this first came up): "we'll leave the name alone if you don't give us a reason to change it, but we'll change it if you want". Mozilla previously said "okay, leave it alone for now" but now they came back to Debian and said "you've got to change it now". At no point did Debian attempt to "get a free ride", they just did exactly what the Mozilla developers asked for.

    Im sure you will counter with: security patches after mozilla.org stops supporting $VER_NOW dont qualify. Only partially true: with IBM/RedHat/Novell supporting mozilla 1.4 long after .org dropped it


    This option has never been offered by Mozilla in respect of Debian's support for Firefox 1.0 (which is still having security fixes applied in Debian, and which is known to have users that are either unable or unwilling to upgrade).

    Let us recap with a statement from Mike Connor, speaking officially on behalf of Mozilla (on the subject of whether or not Debian can call the version it ships "Firefox"):

    At the time, we obviously
    weren't taking that part seriously. We are now, and we're saying its
    not ok.

  16. Every package is a fork by bhmit1 · · Score: 4, Insightful
    Ice Weasel sounds like it will be only installable on Debian, perhaps Debian-descended platforms like Ubuntu.
    With the exception of a few Debian native packages, everything in Debian is a fork that is designed to only be installed on a Debian or a derivative distribution. The source of a Debian package is the original source files and a diff (aka fork) of everything needed to make that software bug free, comply with the packaging standards, and work with other packages on the system. The only difference here from every other package is that Firefox doesn't want to allow Debian to distribute with the same name and logos if it's not released by them, and that's their right. The Debian developers will keep the changes to a minimum to reduce their work, so this will still be very similar to firefox, and I expect the developers to continue using updates from firefox and sending patches and bug reports, where appropriate, back to firefox. The whole thing would have been a lot easier if firefox just made some unofficial branding that could be applied to their product so that people know they are still using firefox that's been modified by a 3rd party vs the real firefox.