Slashdot Mirror


UserLinux Continues Debate Over GUI

An anonymous reader writes "Following up the earlier Slashdot item on this, LinuxWorld is carrying both sides of the discussion as to whether UserLinux GUI should be GNOME only, as Bruce Perens last week decided "by fiat," or include KDE."

564 comments

  1. Gnome or KDE by panxerox · · Score: 5, Funny

    how bout a slashdot poll? 1. Gnome 2. Kde 3. Command line 4. Wine version of XP 5. Cowboyneil is my interface

    --
    "It's so convenient to have a system where everyone is a criminal" - A. Hitler
    1. Re:Gnome or KDE by Anonymous Coward · · Score: 0

      what about Enlightenment?! Or anything else?

      It is all under X-11, I can run Gnome apps under KDE fine, just using KDE libraries.

      In one coherant world we'd all be running one GUI, but in one coherant world that would be under Windoze.

    2. Re:Gnome or KDE by Anonymous Coward · · Score: 0

      how about you learn how to format your post before suggesting polls? ;)

      how bout a slashdot poll?

      1. Gnome
      2. Kde
      3. Command line
      4. Wine version of XP
      5. Cowboyneil is my interface

    3. Re:Gnome or KDE by Anonymous Coward · · Score: 0

      Fluxbox, you insensitive clod!
      *shakes fist*

    4. Re:Gnome or KDE by Anonymous Coward · · Score: 1, Funny

      Opps, should be:

      It is all under X-11, I can run Gnome apps under KDE fine, just using GNOME libraries.

    5. Re:Gnome or KDE by Anonymous Coward · · Score: 0

      Yes. Keep saying that, over and over again, until even your fear-based subconcious believes it. Then the men in white coats will come to collect you, while the world passes your MCSE-, baby-duck-syndrome-, too-lazy-to-learn-new-things- ass by.

      Or you could buy a few books and start learning Linux, Java, Apache, PHP, Perl, C, C++, GTK, Qt, and make yourself useful to the new world order.

    6. Re:Gnome or KDE by Anonymous Coward · · Score: 0
      In one coherant world

      You insensitive clod! I used to run Coherent with X-11, and now it's dead!

    7. Re:Gnome or KDE by Anonymous Coward · · Score: 0

      NEW! Revised and updated!

      $Revision: 1.33 $ $Date: 2003/12/19 23:45:12 $

      The State Of KDE

      We have seen a lot of important news regarding the KDE project over recent weeks, so it is worth pausing to consider the ramifications.

      Let us start with the recent acquisition of SUSE by Novell. SUSE was the biggest Linux distributor (though still dwarfed by Red Hat) to use KDE as its default desktop. SUSE has, for many years, neglected to package the GNOME desktop properly or even do basic Q&A... much to the delight of KDE fanatics. Now, however, Novell has purchased the SUSE Linux distribution and Ximian, a company best known for the producing the most polished and professional desktop available for Linux (GNOME-based). The obvious conclusion to be drawn from these actions is that KDE is about to lose its main commercial support.

      Let us take a look at some of the reasons why this is so:

      • GNOME has always been the commercial desktop of choice. It has long been focussed on getting the basics right and building from there... as opposed to the KDE Project, which is entirely aimed at pleasing the slashdot peanut gallery with pointless eye-candy. KDE features are thrown into the mix with little or no regard for usability, or even good taste. The end result is disasterous, as can be seen by anyone unforunate enough to be forced into using it.
      • KDE is extremely expensive to develop for, unless you intend to produce GPL software. TrollTech, the owners of KDE and Qt, license the X11 version of their Qt toolkit under the GPL. This forces anyone wanting to develop applications built on top of Qt and KDE to be either (L)GPL licensed, or pay for a TrollTech Qt commercial license; costing $3000* for every developer working on the application (per annum.) -- 10 developers: $30,000, and that is just to license the toolkit. No extra development tools and such... just the right to use it. You may find this difficult to believe, but developing for KDE is more expensive than developing for Microsoft Windows!

        * The $3000 figure is just for Linux. If you want to develop for the Mac, Linux and Windows the amount reaches a staggering $6000 per developer.
      • TrollTech is also vulnerable to takeover by companies hostile to Free software and good corporate lawyers who can blow holes in the laughable FreeQt agreements.
      • Qt's/KDE lack of accessiblity. Accessiblity is vital feature for a modern desktop. A desktop cannot be sold to the U.S. government unless it supports the features necessary for disabled users to make full use of it. The lack of said feature effectively cuts it off from the biggest software purchaser of all. GNOME has spent the last 18 months and more doing the ground-work and developing/polishing the accessiblity of the GNOME desktop (thanks to the fine work of Sun engineers). KDE has spent the time making *fake* translucent menus to help make impressive screenshots. Over the next few months you can expect increasing numbers of near-orgasmic announcements of weak accessiblity support from the KDE project, as the full extent of their folly and just how far they are behind GNOME finally becomes obvious to them. The end result will be, as with all KDE features, half-assed and broken -- designed only to function as a marketing feature tick-box filler. Note: The KDE project has begun announcing FULL accessiblity support thanks to using GNOME/GTK code, however (and as usual) the KDE developers are being disingenuous. Accessiblity is more than just toolkit support, it requires work to ensure that all aspects of the desktop are accessible, including auditing applications and (especially) custom widgets, themes and fundementally changing the thought processes of developers. THIS IS THE TIME CONSUMING PART... merely copying GNOME code into KDE/Qt and then posting stories to the morons at slashdot announcing full support is not enough. As predicted, KDE is preannouncing half-finished accessiblity features in a desperate effort to keep up wit
    8. Re:Gnome or KDE by Anonymous Coward · · Score: 0

      Very interesting and thought provoking, but you didn't address what I think is a key question for many of us. Do I have to be Kreskin to see that KDE is dying, or not?

      Any response would be greatly appreciated.

    9. Re:Gnome or KDE by pherris · · Score: 2, Insightful
      From the current poll:
      This whole thing is wildly inaccurate. Rounding errors, ballot stuffers, dynamic IPs, firewalls. If you're using these numbers to do anything important, you're insane.

      While this advice is for just /. polls it's sound advice for anything here.

      --
      "And a voice was screaming: 'Holy Jesus! What are these goddamn animals?'" - HST
    10. Re:Gnome or KDE by Hooded+One · · Score: 2, Informative

      Except that KDE is getting the same accessibility support as GNOME, the OO.o KDE integration project is alive and well, WalMart has already been selling KDE systems in the form of Lindows, and many of the articles you link don't even mention GNOME, or don't exist.

    11. Re:Gnome or KDE by geeber · · Score: 1

      "5. Cowboyneil is my interface"

      I feel dirty. I need a shower now. UUUGGGGH

    12. Re:Gnome or KDE by Anonymous Coward · · Score: 0

      As mentioned in the grandparent -- KDE is using GNOME code to install accessiblity support into KDE, but there is a *long* was to go before you can call it accessible (audits, design, custom widgets etc etc). At the moment, and for the forseeable future, KDE is not accessible.

      As for Lindows... give me a fucking break. NO-ONE uses Lindows. Sun JDS systems are now the biggest Linux desktop systems in existence, and they dwarf every single KDE vendor's installations added toegther by four orders of magnitiude, at least!

      The OO integration project for KDE is a few KDE developers throwing out ideas. The OpenOffice core itself is building in GNOME integration.

    13. Re:Gnome or KDE by Anonymous Coward · · Score: 0
      (I'm not the original poster)

      You're a typical KDE troll, just like the type mentioned in the original post.

      KDE is getting the same accessibility support as GNOME

      You didn't read the post did you? That's an announcement. Nothing more, nothing less. Let's see them implement accessibility in all the apps first.

      OO.o KDE integration project

      You're kidding right? Did you even follow the link you posted yourself? Have they even produced more than a few press releases. Again, let's see it when it's available.

      many of the articles you link don't even mention GNOME, or don't exist.

      Only one of the links were broken. And the articles do mention the companies that are shipping the systems and from that we can deduce the desktop being used.

    14. Re:Gnome or KDE by 56ker · · Score: 1

      Your options are wrong it'd be:-

      1. Gnome only
      2. KDE only
      3. Gnome/KDE only
      4. Neither of the above
      5. (insert some wacky /. ludicrous joke option here)

    15. Re:Gnome or KDE by Kesha · · Score: 1

      A poll is an excellent idea to evaluate current desktop environment preference of Linux (*BSD, UNIX) users.

      To make my bias clear I will tell you outright that I choose KDE, for over 2 years now. And my affection for KDE is so large that I actually abandoned RedHat in favour of SuSE around the time the whole Bluecurve issue arose.

      The reason I disliked Bluecurve is that it really did not solve the underlying issue of gtk/GNOME/Qt/KDE interface integration. At best it tried to hide the problem with some cosmetic makeup (theme + icons). And although the makeup was flattering to GNOME, it was not to KDE. Bluecurve is not an enduring solution.

      So, I abandoned RedHat and decided to give my money to the biggest backer of the KDE project - SuSE. And now that Novell is set to purchase SuSE, I am left wondering whether SuSE will continue to promote KDE as before. Novell already owns Ximian, the "improved" GNOME for corporate desktop. Why would Novell want to maintain two competing inhouse projects? It will most likely kill one of them off. The question is - which one?

      So, what other KDE friendly distribution is out there?

      Fedora is of RedHat descent, and RedHat did not prove to be KDE friendly.
      SuSE is in a limbo until more is known about Novells intentions.
      Mandrake is KDE friendly, but frankly I am not sure that they will still be around in the year 2004.

      There are Lindows, Licoris, Xandros, or so I've heard, but I've heard very little else good about them.

      One thing is certain, if UserLinux will not have KDE, it will not have me as its user.

      Paul.

  2. Slashdot Poll? by Crypto+Gnome · · Score: 1, Funny

    If we did a Slashdot POll, the winning choice would inevitably be:

    All I have is a 9600bps serial line YOU INSENSITIVE BASTARD.

    --
    Visit CryptoGnome in his home.
  3. What's the big deal by HairyCanary · · Score: 5, Insightful

    If you don't like the distribution, don't use it. Simple as that. Keeping the OS simple and maintainable as a laudable goal, and I would find it difficult to argue with them just because my personal choice GUI wasn't included (though neither Gnome or KDE are *my* personal choice :-)). The beauty of open source is that anyone can do this -- if you really disagree with their choice on which GUI to include, make your own distribution and include just KDE with it.

  4. If it's truly for USERs by Anonymous Coward · · Score: 1, Insightful

    Then it should include both so USERs can choose.

    1. Re:If it's truly for USERs by AssClown2520 · · Score: 5, Informative
      My understanding is this is to be an enterprise user system, not a home user or personal user. The whole point is enterprise management and distribution management. Think of an enterprise employment of windows. Every large shop that I know of uses a drive mirror installation and seriously limits any configuration choices that a user may have.

      I've said it before. I agree 100% with including only one GUI. The reason for Gnome over KDE is simply a license issue. I personnaly like KDE better and it is what I will continue to use, as I am not the target "user" of userlinux.

    2. Re:If it's truly for USERs by Idimmu+Xul · · Score: 1

      Then it should include both so USERs can choose.

      Noone is being forced to use UserLinux, anyone that wants to use KDE can just use any of the other distros that support it. USERs still can choose.

      --
      The problem with slashdot is that most of its users were bullied and stuffed into lockers as kids!
    3. Re:If it's truly for USERs by Anonymous Coward · · Score: 0

      Someone actually modded this up. KDE fanatics on the rampage again!

      If you want to use KDE, don't use UserLinux. There's your choice, asshole. UserLinux cannot spend the time crafting and polishing *TWO* desktop systems.

      What makes you comment even more clueless is the fact that if you really want KDE, you can use apt-get to grab it out of DEBIAN's repository because UserLinux *IS* debian.

    4. Re:If it's truly for USERs by ankit · · Score: 2, Insightful

      Not if you are *forced* by your companys IT dept. to use the only linux distribution they will support. A vast majority would not even know there are other linux distributions!!

      --
      Don't Panic
    5. Re:If it's truly for USERs by Anonymous Coward · · Score: 1, Insightful

      USERs still can choose.

      No - this is a business distro, so users' PHBs will choose. And they will predictably choose to refuse to let their users install anything that's not on the UserLinux CD. That means their users will not be able to use any Qt applications, since Perens hath decreed that not even the libraries shall be included.

      This is a disaster for UserLinux, and Perens' stubborn refusal to admit his error is not helping.

    6. Re:If it's truly for USERs by sydb · · Score: 1

      No, they don't even need to use another distro, they can use UserLinux, which is a subset of Debian, by installing KDE (or just whatever libs are required to get the specific KDE application to work).

      --
      Yours Sincerely, Michael.
    7. Re:If it's truly for USERs by Karn · · Score: 2, Insightful

      Choice like this for regular users is unnecessary. I think most regular users will use whatever they are given, and once used to it they will choose it over others (Put a Windows user on a Mac and watch them cry, for example.) The future Linux users won't care what deskotp they use, as long as it lets them use their computer. If they do care, they are most likely advanced users (a minority), and they can go install KDE, just like I can go install Fluxbox or Enlightenment under Redhat.

      And since when is making a default choice a removal of choice from a Linux user? When the KDE people didn't like what Redhat did with KDE, stock KDE Redhat RPMS showed up. If people want KDE on this UserLinux, it is available. That's the whole point of Open Source/Free Software.

      --


      Why do I keep typing pythong?
    8. Re:If it's truly for USERs by sydb · · Score: 1

      And in what way is your post relevant to the choice of default desktop in UserLinux?

      --
      Yours Sincerely, Michael.
    9. Re:If it's truly for USERs by ankit · · Score: 1

      Read the parent and you'll know.

      --
      Don't Panic
    10. Re:If it's truly for USERs by DF5JT · · Score: 5, Informative

      " My understanding is this is to be an enterprise user system, not a home user or personal user. The whole point is enterprise management and distribution management. "

      'Zakly.

      What is it that GNOME has to offer in this regard?

      1.

      KDE Kiosk Mode, also known as lock-down mode, makes it possible to restrict the capabilities of the KDE3 environment in powerful and flexible ways including but not limited to the ability to:
      1. Restrict desktop, application, and printing actions.
      2. Restrict internet access on a URL basis at a desktop-wide level.
      3. Restrict desktop resource customizations.

      Such functionality is invaluable for unattended operation of UserLinux in a kiosk setting as well as for wide-scale enterprise deployment of a controlled environment.

      2.

      A new easy-to-use administration tool, yet in the stages of development, will build on top of the KDE Kiosk Mode and expand upon the features in an exciting direction. The tool will enable scalable management of users, their settings and IT privileges. The design goals include:
      1. Full scalability from medium to large organisations.
      2. Usable by both KDE and non-KDE applications.
      3. Seamless integration into existing IT infrastructure.
      4. Roaming support.

      Please expect more detail and an official announcement in 2004 Q1.
      3.

      An Integrated Terminal Server and Client employing a new and highly efficient X compression technology thereby enabling seamless desktop integration of applications based on a remote compute server. This feature will be in addition to KDE's existing remote desktop support (VNC and RDP) and is especially exciting in light of the fact that it enables a satisfying desktop experience on a thin client even with a low-bandwidth connection (e.g. dialup) to the application server. The technology will bring us on par with Citrix, Tarantella, SunRay and Windows Terminal Server offerings.

      4.

      KDE Print: Enterprise-grade technology for intimate management of printers and print jobs, adaptable to innumerable creative tasks.

      5.

      KDE Core Killer Apps: Whilst too numerous to list here, we expect to leverage core KDE applications where appropriate. In addition to the well-known applications several pertain directly to the enterprise including:
      1. The upcoming Kontact, an integrated personal information management suite, which in conjunction with the Kolab Server will provide a powerful standards-based groupware solution.
      2. The upcoming KERP, an Enterprise Resource Planner.
      3. A set of financial trading tools currently in development.

      ISVs in particular will be pleased to note that the KDE/Qt environment sports a rich body of development tools that leverage the elegant and powerful framework provided by KDE/Qt as well as tools enabling development in areas ranging from HTML production to UML modelling, CAD design and document publishing.

      6.

      KDE brings an impressive body of localization and internationalization effort to the table. With over 80 translation teams and KDE 3.2.x to be available in an estimated 50+ languages, KDE is a compelling choice for an enterprise desktop with an international audience.

      Where is GNOME's visionary roadmap for a subsystem as powerful as that?

      Thought so.

    11. Re:If it's truly for USERs by Anonymous Coward · · Score: 0

      Put a Windows user on a Mac and watch them cry, for example.

      The average Windows user, when faced with a Mac, will cry for about thirty seconds. Then, when shown how much simpler a Mac is to use, the Windows user will weep tears of joy.

      Windows still hasn't mastered the dark art of copy-and-paste, for cryin' out loud.

    12. Re:If it's truly for USERs by sjvn · · Score: 1

      Users can choose. At heart, all UserLinux is is a pre-selection of software to make it easier for naive users to get up and running. Don't like it? Put together your own best of Linux distribution.

      This debate is getting more than a little silly.

      Steven

    13. Re:If it's truly for USERs by Idimmu+Xul · · Score: 1

      Not if you are *forced* by your companys IT dept. to use the only linux distribution they will support. A vast majority would not even know there are other linux distributions!!

      If you are *forced* to use something by your companies IT department, then you are forced to use it. This also carries across to whether they force you to use Windows, or GNOME or KDE under another distro.

      If the company feels that UserLinux and GNOME are better for the company than Suse and KDE then so be it.

      --
      The problem with slashdot is that most of its users were bullied and stuffed into lockers as kids!
    14. Re:If it's truly for USERs by sydb · · Score: 2, Insightful

      But if a Company chooses UserLinux, the User is the Company, not the employee! When I go to my day-job I am a member of staff, not a customer of software houses. I do what is expected of me contractually using the tools I am provided with; I don't complain if I don't like the colour of the tool.

      (OK I do complain and I might bring in my own tool, but I don't believe I occupy the moral high ground by doing so, in fact I consider myself a but of a chancer and it's my good fortune to get away with it).

      --
      Yours Sincerely, Michael.
    15. Re:If it's truly for USERs by Idimmu+Xul · · Score: 1

      No - this is a business distro, so users' PHBs will choose. And they will predictably choose to refuse to let their users install anything that's not on the UserLinux CD. That means their users will not be able to use any Qt applications, since Perens hath decreed that not even the libraries shall be included.

      If you are using a workstation that your PHB has chosen for your job, then that's a part of your job that you'll have to deal with, compare it to having to fill in a form in block capitals with black ink, when your favourite pen has blue ink, if UserLinux and GNOME are chosen by the PHB it should still be possible to adequatly use it to get the work done, if for some reason its not possible then there are bigger issues at stake with respect to the PHB and whatever analysis was done.

      --
      The problem with slashdot is that most of its users were bullied and stuffed into lockers as kids!
    16. Re:If it's truly for USERs by redtux1 · · Score: 1

      so should lindows, ark, xandros etc

      stop whinging and get over it

    17. Re:If it's truly for USERs by kayen_telva · · Score: 1

      retarted comment. by this reasoning, ALL software should be included. where do you draw the line? KDE will be an apt-get away, so chill the F@#$ out.

    18. Re:If it's truly for USERs by Elektroschock · · Score: 1, Insightful

      License FUD. The KDE license problem is slashdot-fiction. It is a pure ideological decision from Bruce Perens because Gnome is not ready for the desktop yet while KDe serves as an enterprise desktop in many organisations. When we talk about Desktop-Linux success in Europe we think of Linux/KDE. RedHat, dominant player on the US market, chose Gnome. RedHat is not intrested in the desktop market at all, they focus on the server. Guess why. For me and you gnome is okay, hackers will prefer gnustep, but the "real" desktop user will be suited better with KDE. It is absolute new to me to explicitely exclude a piece of software.

    19. Re:If it's truly for USERs by AssClown2520 · · Score: 2, Insightful
      You certainly have me at a disadvantage when it comes to the functionality and future of KDE. I use KDE daily, but not at an enterprise level so I am not aware or even interested in a lot of the features that you have detailed.

      My point remains that for the target use of userlinux, this system should concentrate on 1 WM. Perens has made it very clear that the choice simply came down to the license issue.

      There are dozens of distributions out there with different motives. The most successful distributions make clear and solid guidelines and stick to these. I like the fact that Perens has very clearly stated these directives and he should stick to them religously.

      Again, I use KDE and love it. But this issue/choice is not about what environment works better or has feature x. It really boils down to licensing.

    20. Re:If it's truly for USERs by AssClown2520 · · Score: 3, Interesting
      License FUD. The KDE license problem is slashdot-fiction.

      I am not trying to be a smart ass, but I would really appreciate it if you would enlighten me on this issue. I may be victim to the slashdot-fiction as IANAL and I have not studied either license in detail.

      My understanding from what I have read is that if you are going to make a commercial product with QT, you need to buy a royalty license. Is that not the case?

    21. Re:If it's truly for USERs by afd8856 · · Score: 2, Informative

      This is absolutely true.

      From my experience, people will prefer KDE over GNOME (I don't know what you're talking about the beauty of GNOME, yes, so it's streamlined - that in my experience, is lack of options - but is ugly, not customizable, it's file manager is anything but usefull to real work, it's applications are not so good and it is slooow...

      And let me explain my experience. A year ago (I used RedHat 8) i installed in my organization (a non-profit one, 10 computer seats) an LTSP server. The users had no previous experience in Linux and not that much experience with Windows anyway (they're just users, they don't go about configuring anything). When asked to make a choice, they choose KDE. Over the relative slow network (a switched 100Mbit network, with realy low hardware for X stations - P2-266 and 64Mb Ram, and a not so great server - Athlon 1,2 Ghz) KDE 3.1 runs a lot faster than GNOME (quite smooth, actualy), feels integrated, Konqueror rules (they use it for file management and web browsing), kmail is just right to them, it has integrated image and PDF viewer, very easy printing with preview, and, once again, I repeat, QT runs faster than GTK, XUL and VCL (I wish kde.openoffice.org would finish the integration very soon, it's just what we need). Also, I don't know why everyone is complaining about Kcontrol, it's a non-issue here. After I showed them how to use it and where to start, they're quite comfortable with changing settings (mostly visuals - icons, backgrounds, window decorations and styles).

      And, because I'm a web developer, I can use Quanta and KDE's transparent network integration to work over fish on the webserver, running, of course, under WindowMaker

      --
      I'll do the stupid thing first and then you shy people follow...
    22. Re:If it's truly for USERs by afd8856 · · Score: 1

      It goes something like this:
      We are open-source idealists. So why should we choose the lesser GPL over the real GPL? We should promote GPL over closed source, don't we? It seems to me that the UserLinux idea is built with the idea that companies would not pay for comercial Qt licences. But, theKompany uses it comercially, Borland had Kylix built on Qt, Opera on Linux is built with Qt, etc. Clearly, those companies chose the better toolkit by paying for it. Of course, it makes more sense to have a free toolkit for your closed source software, but only when it's not something really big, like the above examples.
      Also, it makes some sence that, if you make money with it, you should pay for it.
      What I don't understand is why dump the really good KDE for a not so good (IMHO) Gnome just because of toolkits. Making GTK work better with QT is a lot easier (again, IMHO) than replacing KDE. My answer to the UserLinux proposal is: use KDE as desktop, support Gnome also and improve interoperability (freedesktop is already a common direction for that). By the time UserLinux actualy sees the light of day, I believe interoperability will be better betwen toolkits, anyway.

      --
      I'll do the stupid thing first and then you shy people follow...
    23. Re:If it's truly for USERs by Anonymous Coward · · Score: 0

      Cut-n-paste works fine on Windows -- it's drag-n-drop that sucks.

      I'm posting from a Mac right now, and I can tell you that there's several annoyances which make it difficult for us Windows users. Window Management from the Dock just sucks. (Can't open a new browser window without maximizing an existing one, for example). The lack of keyboard shortcuts is completely annoying. Network browsing sucks. The multi-pane file browser is just annoying and lacks basic features. The keyboard lacks useful keys like Forward Delete. And finally, the single mouse button on this PowerBook.

    24. Re:If it's truly for USERs by inc_x · · Score: 2, Informative
      Let's start with royalties, according to webster a royalty is:
      "a payment to an author or composer for each copy of a work sold or to an inventor for each item sold under a patent"

      Does Qt require royalty payments? No.

      However, if you make a commercial closed source product (and do not wish to use the GPL) you will need to buy a one-time commercial Qt license for the developers that work on your product.

      You can read more about commercial Qt licensing here.

      So next time you hear someone talk about Qt royalties you now know that that person either doesn't know what he is talking about or he is trying to sell you a bridge.

    25. Re:If it's truly for USERs by AssClown2520 · · Score: 1
      Let's start with royalties, according to webster a royalty is: "a payment to an author or composer for each copy of a work sold or to an inventor for each item sold under a patent"

      Good point. My choice of word here was entirely incorrect. Nevertheless, the point still remains that a license needs to be bought in order to develop commercially under QT. OTOH, this is not the case for GTK. This is the only point that gave the nod to Gnome.

      Thanks for the clarification though. There is an important distinction between a royalty and a one-time license fee.

    26. Re:If it's truly for USERs by inc_x · · Score: 2, Insightful
      > This is the only point that gave the nod to Gnome.

      Appearantly, but when you look at the realities of the market place you will notice that commercial software developers gladly pay this license fee in order to use a better toolkit.

      That's were it starts to smell a bit fishy. When given the choice, commercial software developers prefer to use Qt and here comes Bruce who says, I know better, commercial software developers should use GTK because it is better for them. Dunno about you, but I always become highly suspicious when other people start telling me what is supposed to be in my interest.

    27. Re:If it's truly for USERs by autopr0n · · Score: 1

      My understanding from what I have read is that if you are going to make a commercial product with QT, you need to buy a royalty license. Is that not the case?

      You need to buy a per-seat license, not pay royalties. It's about twice as much as the cost of visual studio. But the important thing is the difference between commercial product and in-house software. The GPL allows you to write code inside the company and keep it 'personal'. You don't need to release it.

      In fact, the way the GPL works, there's no way to prevent someone from using GPL'd code internally. It says right there in the first paragraph that you don't need to agree to the GPL to use the software, only to distribute the software.

      The issue only comes up with companies that actually sell software. The vast majority of which do not.

      Anyway, the way most companies are going, the code will probably be done in java, or used through a web browser anyway, making GUI development moot.

      --
      autopr0n is like, down and stuff.
    28. Re:If it's truly for USERs by dilute · · Score: 1

      Except for one thing. Take Debian, for example, which supports both - if you're running either Gnome or KDE as your desktop, apps from the other work, so it really is no big deal. However, if as a result of this, you can't run KDE apps, then that does make a difference, because there are a lot of things in KDE that don't have corresponding apps in Gnowme that are as developed. Not as much as there used to be, but it is still an issue.

    29. Re:If it's truly for USERs by Anonymous Coward · · Score: 0

      Can't open a new browser window without maximizing an existing one, for example

      Yes, you can. That's what the menu bar is for.

      The lack of keyboard shortcuts is completely annoying.

      Keyboard shortcuts were invented on the Mac. Besides, they're completely customizable. Any menu item can be assigned an arbitrary keyboard shortcut.

      Network browsing sucks.

      Wrong.

      The multi-pane file browser is just annoying and lacks basic features.

      Wrong.

      The keyboard lacks useful keys like Forward Delete.

      Wrong.

      And finally, the single mouse button on this PowerBook.

      One's all you need.

  5. Holy War by SkArcher · · Score: 4, Insightful

    I sense another Holy War incoming over this. In all honesty, while having a single interface to deal with would be easier, I don't feel the GNOME ca claim to be it. Nor can KDE, but shortening the field by including only one in this project is a bit anti-competitive, and OSS has allways thrived on the competition between similar projects.

    --

    An infinite number of monkeys will eventually come up with the complete works of /.
    1. Re:Holy War by McAddress · · Score: 1

      Speaking of Holy Wars. It's GNU/Linux!!!

      In all seriousness, the insistence that Linux should be "Free", and therefore be stuck with KDE or GNOME will make it harder to achieve the goals of ease of use. Ease of use is not just for programmers. it needs to be for <cliche> grandma users as well.</cliche> People need to start paying more attention to some of the UI's used by the windows clones like Lindows, on the grounds that even if they suck technically, they are easier to use than GNOME/KDE.

    2. Re:Holy War by Svennig · · Score: 5, Insightful
      In all honesty, while having a single interface to deal with would be easier.. OSS has allways thrived on the competition between similar projects

      This competition also gives OSS its greatest downfall - there just arent any standards. You wanna write for QT? do x. You wanna write for GTK? do y. You wanna write for something else? do z. Someone needs to make an standardised API for all linux guis and stick with it.

      Say what you want about M$ Windows, but it provided a standard. The ability to program on one GUI and reach 80% of people is fantastic.

    3. Re:Holy War by Anonymous Coward · · Score: 0

      People need to start paying more attention to some of the UI's used by the windows clones like Lindows, on the grounds that even if they suck technically, they are easier to use than GNOME/KDE.

      The UI used by the Windows clones, including Lindows, is KDE.

      The UI used by the distributions that have attracted the most interest from goverments worldwide, SuSE and Mandrake, is KDE.

      KDE is the nearest thing Linux has to a standard interface. Among major distributions, Red Hat is unique in selecting Gnome by default (unless you count Sun's "Java desktop", which hasn't taken off yet).

      While I respect Bruce Perens, and I respect his decision, I hope other people will respect my right to believe that he's made a major mistake here. I shall not be recommending UserLinux to anyone.

    4. Re:Holy War by Anonymous Coward · · Score: 1, Informative

      Ouch. Why is a standardised API for all linux guis needed? You -can- run programs written for different graphical toolkits under different systems. You don't need to run gnome for gtk+ or gnome apps; you don't need to run kde for QT or kde apps. Any toolkit for which you have the libraries installed will run under any window manager.
      Windows has a -lot- of GUI toolkits. Sticking to microsoft ones, there's MFC and raw Win32, among others. There's also java's swing, wxWindows, and, yes, QT.

      If you want interoperability - great, it's already there. If you want the one standard API - hey, there's raw X11 (xlib is fun!); it works.

      For some tasks, using one API over another is easier. At other times, a developer prefers one achitecture over another for various reasons. It can be -good- to allow a programmer to do things in different ways.

      Program in QT as much as you want; it won't be identical to GTK, although the underlying system might be the same. Given an installation of QT, it doesn't matter if someone is running xfce4 or openbox; it runs.

      How Windows can reach "80%" of people is that it is installed on most desktops. Unifiied GUI API's are not the reason; it does not have one.

    5. Re:Holy War by CaptnMArk · · Score: 1

      Especially since there is at least one more choice for a linux GUI toolkit: XUL from mozilla.

    6. Re:Holy War by Anonymous Coward · · Score: 0

      Great. So in addition to the GNOME/KDE holy war, now you'd like to throw the old Windows/Linux holy war in the mix? -1, Flamebait mods please!

    7. Re:Holy War by Anonymous Coward · · Score: 0

      Wow. You just don't get it, do you?

      Windows DOES has a single standard programming API. Linux doesn't. As a result, every Linux system has to have eleventy dozen libraries installed just to be functional. And those libraries are all under the control of third parties, meaning they're all updated at random times. And since Linux has NO centralized software update framework, every Linux user has a different version of those libraries on his computer. It's a fucking mess.

    8. Re:Holy War by Svennig · · Score: 1
      Let me expand a little. Much as the post below the parent suggests my original post was flamebait, it was not. Here's my reasoning (although I admit in retrospect it was not well explained and put forward).

      If I took my parents machine and put a fresh install of RedHat 9 on it, it would take them about a week to re-learn everything. This is a conservative estimate.

      So my parents now have a reasonable knowledge of Gnome with Bluecurve. Suppose we live in a world where linux is everywhere and M$ doesnt exist. They go off to work (they are teachers) and have to use KDE at school. This takes them more time to learn and I can't even begin to tell you how confused they would get having to use both. My parents are the average computer users: they barely manage Windows.

      This is NOT geek Linux where you can twiddle the nobs and customise everything. This is USER linux and most users dont care about having choice, entirely the opposite in fact. My parents dont want choice they want something familiar to appear on the screen when they turn the machine on. If you could learn to use one GUI for linux and know that any other linux box would have that GUI, we would be a step closer towards linux on the desktop (which is A Good Thing).

      I take the point about having GTK and QT libraries installed, my argument to that point was somewhat flawed.

      I'm not interested that they chose gnome or KDE above the other - I don't care. I care that this choice has been made so my parents can turn on a UserLinux distro anywhere and get a familiar desktop - a standard set of widgets and feel.

    9. Re:Holy War by Anonymous Coward · · Score: 0

      It's only a mess if you build and install libraries from wherever you found them on the net. Try sticking to the binaries provided by your distro, that way someone should have checked that they don't conflict with other packages and you have someone to complain to if it doesn't work.

    10. Re:Holy War by Anonymous Coward · · Score: 0

      XUL isn't a generally useful toolkit. First of all it only comes packaged with Mozilla. Second, it changes all the time based on Mozilla's whims and therefore breaks.

      The few fools who tried building 3rd party apps on XUL found this out the hard way. New version of Moz comes out, all their apps stop working. Pretty pathetic - and now there is just about 0 non-browser apps running on XUL.

    11. Re:Holy War by Anonymous Coward · · Score: 0

      Try sticking to the binaries provided by your distro

      Two obvious problems: the binaries provided when I installed are woefully out of date. Program X requires version Y of library Z, which depends on library Q which requires library B which...

      Second, that puts an unreasonable burden on those who create and (sometimes) maintain distributions. I thought Linux was supposed to be one of those "anybody can do it" things.

    12. Re:Holy War by Anonymous Coward · · Score: 0

      Who says anything about customizing anything?
      I'm a geek; I freely admit it. Most of my relatives aren't.
      Sit someone down in front of KDE or gnome. Show them to click the K or foot. It's not harder than clicking the "start" button under Windows.
      They can click on icons to start programs. Depending, they might need to single or double click; for absolute newbies, single-click is a lot easier, for those used to Windows, double-click usually is.
      I've used KDE, Gnome, several less popular X11 Window managers, CDE, Windows, BeOS, QNX's photon, etc. For basic usage, they're all pretty similar with the exception of the -box X11 ones, where you right click instead of clicking a button in a corner for a menu.
      Who -cares- about advanced customization? It's nice when you need or want it, but for basic usage, there's really -very- little difference between KDE and Gnome. For default looks, I personally prefer KDE; ymmv.
      UserLinux won't be the only distribution used, so it doesn't really mitigate this "problem".
      Show people how to click, how to double-click, and how to get to a menu of applications, and they're pretty close to all set, especially given a decent set of desktop icons.
      For system administration? That should -not- be an issue at their school, at least. Using one desktop or another really is -not that tough-.
      People managed to go from DOS to Window 3.1 to Windows 95; changing desktops is doable, and really does not take that long.

      There are a lot of people who barely manage Windows, or whatever system they need to use. It's unrealistic to sit them in front of linux and have them instantly become experts; no amount of UI design can do that.
      My point is, for pure -desktop- use, it makes very little difference. As for applications, hopefully they're using the same set, approximately; they have a much higher learning curve than any semi-modern commonly used UI, whether Win32, Gnome, or KDE.
      Please don't tell me that the shading of the widgets differing makes it impossible for them to use one or the other.

    13. Re:Holy War by zhenlin · · Score: 1

      Non-insightful. The core difference between the GUI systems is the toolkit that is used. Different toolkits attract different sorts of developers... I'd say, Qt encourages tight knitting, GTK+ encourages... something, and GNUStep encourages tight integration without tight knitting.

      IF... they standardised the GUI programming, the toolkit differences would disappear. And then the different desktop environments would merge. And everyone is left with no choice.

  6. Why does it matter so much? by Anonymous Coward · · Score: 2, Insightful

    I really don't get it. UserLinux seems targeted towards a very specific goal that KDE cannot meet because of the Qt widget set. That's that, right? What is the big deal? Why does it matter to KDE ppl anyway? Why is it so important a matter that it has required months of discussion to no end except bitching and fantasy conceptions of what KDE will someday be?

    1. Re:Why does it matter so much? by fritmebufstek · · Score: 5, Informative

      It matters to the KDE folk, because we ( a group of some twenty enthusiast KDE and Debian developers ) were intending to work together with UL on making UserLinux a KDE based enterprise distro that would easily beat other available offers. Bruce's decision stopped this plan, but we are continuing the effort standalone now. Furthermore, the licensing argument is bogus, read why below.

    2. Re:Why does it matter so much? by Anonymous Coward · · Score: 0

      Well then, lets put it on the table. This project is not by or for the community. Yet it depends on the contributions of a huge number of developers. It's goal is to encourage proprietary development on top of freely contributed libraries. It by design excludes half of the desktop development efforts, many of them not even close to being matched.

      As I said elsewhere, when your most precious resource is developers, why would you go piss off half of them right off the start?

      Neither Gnome or KDE can offer right now what is required. Isn't it a fantasy conception that Gnome is the answer?

      Derek

    3. Re:Why does it matter so much? by Anonymous Coward · · Score: 0

      Difference being, you don't have to rewrite Gnome from scratch to meet requirements, whereas the bottom layer of the KDE pyramid is the Qt widget set.

    4. Re:Why does it matter so much? by 10Ghz · · Score: 1
      UserLinux seems targeted towards a very specific goal that KDE cannot meet because of the Qt widget set. That's that,


      And what goal is that? Are you saying that UL's target audience is "Companies that write for-profit software but they are so poor that they can't afford to spend $2000 on developer tools"? Very very few companies WRITE software. Most companies USE software, but they don't write software. And even if they do, GPL allows company to write in-house closed-source software, so they could use Qt just fine.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    5. Re:Why does it matter so much? by unapersson · · Score: 1

      > And what goal is that? Are you saying that UL's
      > target audience is "Companies that write
      > for-profit software but they are so poor that they
      > can't afford to spend $2000 on developer tools"?

      I assume it's targeted more at the companies that go: "I've bought this distro off company X, why do I have to pay company Y to develop for it?"

    6. Re:Why does it matter so much? by rking · · Score: 3, Insightful

      It matters to the KDE folk, because we ( a group of some twenty enthusiast KDE and Debian developers ) were intending to work together with UL on making UserLinux a KDE based enterprise distro that would easily beat other available offers.

      So to be clear on this, your intention wasn't some marvelous egalitarian distribution with equal showing for Gnome and KDE that so many people here are going on about, your hope was to base it on KDE instead? You agree with the basic idea of Bruce picking one desktop environment or the other, you just understandably wish that he'd picked your one. Have I got that right?

    7. Re:Why does it matter so much? by inc_x · · Score: 1
      > I really don't get it. UserLinux seems targeted towards a very specific goal that KDE cannot meet because of the Qt widget set. That's that, right?

      Not quite, when UserLinux was announced it talked about community based, cost-sharing, free software and an aim for the enterprise. This attracted many KDE developers because KDE offers a very good set of software to reach such goal. Appearantly that wasn't quite the plan that Bruce had in mind, because he then "ruled" that GNOME was to be used, with some reference to unnamed sponsors. This surprised the interested KDE developers somewhat. They published a paper in which they outlined why a KDE-based approach would be a better solution in the hope to start a discussion on the merits, but Bruce didn't seem very interested in hearing arguments.

      So in short, it's not the fact that Bruce choose GNOME, it's the fact that he was not very honest about his motives when he started with UserLinux that has upset quite a few people.

      If he would have told people from the start that he was hired by some companies to start a GNOME based distribution not many people would have bothered making a case for KDE.

    8. Re:Why does it matter so much? by fritmebufstek · · Score: 1

      Yup, we're mad at Bruce Perens because of the way the choice was made. There was not any sort of democratic decision, and he kept on inventing new arguments, which we kept on rebuffing ( the licensing argument seems to be his final argument, but we have also rebuffed it, as you can read below ).

  7. Re:What's the big deal by DAldredge · · Score: 1

    Because that isn't enought. Side 1 doesn't want Side 2 to get 'ahead'.

    Who side 1 and side 2 are in this discussion is up to you.

  8. Why I'm not optimistic for UserLinux by jbellis · · Score: 5, Interesting

    They're targeting the enterprise market -- defined explicitly by Peren's whitepaper as (paraphrasing) the market that Red Hat gets $$$ in support fees for.

    I just don't see companies who want that level of support settling for "here's our linux distro, and if you want support, uh... here's a list of 3rd party providers." Remember LinuxCare? They're still around, but only because they moved away from providing third-party support solutions.

    1. Re:Why I'm not optimistic for UserLinux by benjamindees · · Score: 1

      Businesses tend to want more than just phone support. Having a local rep in town is what RedHat is missing. Having a network of independent providers is the easiest way for a community-based distro like UserLinux to get that.

      --
      "I assumed blithely that there were no elves out there in the darkness"
  9. GNOME is a failure by Anonymous Coward · · Score: 0, Flamebait

    Once upon a time there was a project named KDE, a friendly bunch they were. They used a toolkit named "Qt" because they didn't have the luxury of using anything else. They could either use Motif which everyone agreed was crap or Qt. There was no GPL toolkit like GTK+ back then (it was around.. just not nearly as advanced or stable).

    Then comes this arrogant troll, named Miguel. He writes to the town's newspaper (Slashdot.org) about the evils of KDE. He claims that KDE is dependent on Qt and that Qt is EVIL. It is EVIL because it is not GPL. It is EVIL because it can take over the desktop just like MICROSOFT. And we know how EVIL MICROSOFT is, right? REALLY EVIL.

    This was the opening statement for the initiation of the GNOME project. Like Linus' famous Linux announcement on Usenet, this was Miguel's famous announcement to the world about GNOME--a flame about KDE.

    This gets them over reinvention hurdle #1 (reinventing an already _GPL_ desktop.. which KDE was ALWAYS GPL, but it didn't seem like it because Miguel spewed PR crap that said KDE was anything but GPL). The drones (like you) flocked to GNOME thinking "wow what a _great_ idea!@# free software at last!@#" or perhaps "KDE is teh suck" (notice the misspelled "the") or perhaps "in soviet russia KDE uses YOU." I can't remember what kind of sheepisms existed back then, but you get the idea.

    During the next few months, GNOME magically catches up to KDE. How this magic is performed is quite simple. On GNOME hacker mailing list I was witness to some extraordinary feats that would make even the most insane coder wince. A famous GNOME hacker (who still is) said something along the lines of this:

    "A GNOME spreedsheet you want Miguel? Don't worry. The way things are looking, I can hack one out in a few days. We will borrow from X, Y, and Z projects since they have most of the functionality we need. It will be a matter of fitting them all together."

    Thus, Gnumeric was born. And I am dead serious on this too. This is exactly what they did for _all_ GNOME sub-projects, which is why the code is such an utter mess today and will never stand the test of time.

    As for the interface sucking... GNOME has that completely covered. In the time I watched over GNOME, it changed fundamental parts of its interface no less than, I'd say, 5+ times. _Nothing_ adheres to the recommended style-guide which was there from pretty much day one. And _nothing_ still does adhere to it, except perhaps projects which should almost not be considered seperate from GNOME.

    Integration of GNOME software is nil. This is what attracted me to GNOME initially. Miguel promised _integrated_ applications. Software that "just works." This has never happened and never will. It was all PR designed to help Miguel build a company around something he still has control over. Thus, Helix Code was born. Which later became Ximian.

    In conclusion, GNOME is a failure. GNOME's goal was a desktop for *ix that grandma could use. As someone else recommended.. try Ximian "they have it all worked out." Which is very much the point--to fill Miguel's wallet (reality hurts, boys and girls). GNOME is only a success if you consider success to be pissing all over KDE (which had no knowledge or connection to GNOME, until Miguel made it GNOME vs. KDE), creating a wasteland of code, luring in the Slashdot crowd with PR after PR stunts. It has nothing to do with their "interface" at all. It's strictly politics that got them whatever they have today.

    1. Re:GNOME is a failure by Ianoo · · Score: 5, Insightful
      Then comes this arrogant troll, named Miguel. He writes to the town's newspaper (Slashdot.org) about the evils of KDE. He claims that KDE is dependent on Qt and that Qt is EVIL. It is EVIL because it is not GPL. It is EVIL because it can take over the desktop just like MICROSOFT. And we know how EVIL MICROSOFT is, right? REALLY EVIL.
      Well it seems that although QT is now GPL'd, licensing for the commercial version still has a lot to do with this debate. Read the article.
      "A GNOME spreedsheet you want Miguel? Don't worry. The way things are looking, I can hack one out in a few days. We will borrow from X, Y, and Z projects since they have most of the functionality we need. It will be a matter of fitting them all together."
      Go ahead and accuse GNOME of borrowing things - but just remember KDE picked the existing off-the-shelf commercial QT toolkit (then licensed under the QPL which is incompatible with the GPL) when they began their project.

      Just what is wrong with this approach? KDE decided to write KHTML instead of using Gecko, whilst GNOME is now going to use Gecko as their primary HTML layout engine in the DE. Which is better? I'd say Gecko is much more standards compliant than KHTML, even with the latest patches. The point is that for really huge projects like a HTML layout engine, you need huge resources. A lot of KDE developers work on KHTML when if they'd used Gecko, they could be working on far more interesting things.

      Also, surely it's better than free software projects share code. So many people are put off GNU/Linux & BSD by the fact there are 500 different text editors and not one of them works properly (except vi ;)). Ringfencing code is not something anyone should be doing.
      As for the interface sucking... GNOME has that completely covered. In the time I watched over GNOME, it changed fundamental parts of its interface no less than, I'd say, 5+ times. _Nothing_ adheres to the recommended style-guide which was there from pretty much day one. And _nothing_ still does adhere to it, except perhaps projects which should almost not be considered seperate from GNOME.
      Have you ever actually used GNOME? All the control panels, Nautilus, Epiphany, Evolution, Gnumeric, GIMP (v2+), Gaim and more now obey the HIG. KDE has changed their metaphors just as many times as GNOME, too. Whatever happened to the taskbar stuck to one side of the screen? KControl and Konqueror have had their menus and sections reorganised several times. So what?
      Integration of GNOME software is nil.
      Wrong again. GNOME applications use FreeDesktop's drag-and-drop specification (which works 95% of the time in the apps that I use), and there is the bonobo component model which works very nicely and is in many respects technically superior to KParts.
      In conclusion, GNOME is a failure. GNOME's goal was a desktop for *ix that grandma could use. As someone else recommended.. try Ximian "they have it all worked out." Which is very much the point--to fill Miguel's wallet (reality hurts, boys and girls).
      No, that was never GNOME's goal. GNOME's original goal was to create a desktop without the QPL/QT licensing issues that KDE had. Now that KDE no longer has these issues (for the most part), it is chugging along nicely as a good large free software project. Very few free software projects have definite roadmaps or even definite goals. As for Ximian/Novell/RedHat/Sun, their commercial support of GNOME makes it better, not worse. Their code is still available under the GPL and you can quite happily acquire it and use it and hack it without stuffing anyones' wallet.

      In conclusion, you're a troll. Have a nice day.
    2. Re:GNOME is a failure by Anonymous Coward · · Score: 0

      GNOME is successful because it has GNU-blessing. They kissed RMS's egoistic anus and became famous. It it was not related to GNU, it would be in the same level with IceWM, FVWM, Evolution, etc.

    3. Re:GNOME is a failure by Anonymous Coward · · Score: 0

      which works 95% of the time in the apps that I use

      wahahaha
      fuckstick, call me when it actually DOES work.
    4. Re:GNOME is a failure by Ianoo · · Score: 1, Insightful

      There are just as many non-compliant apps for Windows as there are for open source systems. You ought to see some of the crap people put up with in free utilities and things.

    5. Re:GNOME is a failure by james_underscore · · Score: 5, Insightful

      Its an interesting point - GNOME was originally started because Qt, which KDE was based on, wasn't "free software". But now it seems KDE is more "free software" than GNOME is.

      Remember part of the point of free software is not just that its free to use, but free to modify and use the code for new programs. The only "drawback" being that if you base your software on free software, you are required to make your modification free software too.

      Perens says in the article that his decision is not because of one being technically superior, but because you can make proprietary GNOME software for free, but if you make KDE software it has to be either GPL or you pay a lot of money to the makers of Qt.

      The reason for this, I assume, and I haven't got the time to check it out, is because GNOME libraries are mostly LGPL, whereas the core Qt library for KDE is GPL only. The "Lesser" LGPL license lets you make proprietary software by screwing over free software developers and using their libraries without giving anything back to the community that provided the entire platform you are developing on. Even GNU says you should not license you're free software libraries LGPL.

      The irony is that, as you point out, GNOME was supposed to be a "free" alternative to KDE, with all the GNU zealots following behind it for that reason. But now it seems the GNOME developers are getting fucked by the "open source" crew that were originally blamed for the travesty of KDE using a non-free development kit.

    6. Re:GNOME is a failure by Anonymous Coward · · Score: 0

      Too bad Gnome's development is going to pick up, because Gnome is the Corporate dekstop not KDE. KDE is overly bloated with features no one uses.

      I love how moderators blindly mod up trolls like this.

    7. Re:GNOME is a failure by Anonymous Coward · · Score: 0

      I agree with you the Gnome is a fucking piece of shit but, since it's free software: SEND PATCHES OR SHUT THE FUCK UP

      Turbo Glass

    8. Re:GNOME is a failure by Anonymous Coward · · Score: 0

      KDE decided to write KHTML instead of using Gecko, whilst GNOME is now going to use Gecko as their primary HTML layout engine in the DE. Which is better? I'd say Gecko is much more standards compliant than KHTML, even with the latest patches.

      Standards compliant != better, you know.

      Incidentally, which rendering engine did Apple choose? Hint: it was one of those two, and it wasn't Gecko.

    9. Re:GNOME is a failure by Ianoo · · Score: 1

      They chose KHTML because they could understand the code. It would have taken them longer to get to grips with Gecko (because it's big and beautiful!) and do the hacks they wanted to do to make it work with Quartz natively rather than through the abstraction layers in Gecko which allow it to be ported to so many platforms. Whilst this is great for porters, it does increase the size of the code, whereas Apple probably wanted something tighter.

    10. Re:GNOME is a failure by DAldredge · · Score: 1

      This is the same GNU project that 'fired' the GNU/Hurd OS lead because the lead wanted a MORE FREE license for the docs than RMS.

      They should practice what they preach.

    11. Re:GNOME is a failure by iwbcman · · Score: 3, Insightful
      Moderators Mod the parent post down. This is obvious flamebait material and it is factually wrong. And this counts as interesting ? When GNOME came out QT was not GPL. QT only became GPL significantly later-remember why Debian refused to include KDE for so long? QT did finally become GPL- but it is hampered by a dual-licensing model. Now this license, as a buisness model, has worked well for QT-but it is not *free* for commercial development, and Burce Perens has explicitly stated this as one of the goals for UserLinux. I support Trolltechs licensce model- it is a good model for non-comercial Linux software development-but it is not good for commercial Linux software development, because one has to pay royalty fees to use it- and this is the (cost)barrier Perens wants to avoid. Your statement:
      "reinventing an already _GPL_ desktop.. which KDE was ALWAYS GPL, but it didn't seem like it because Miguel spewed PR crap that said KDE was anything but GPL"
      is pure and simple bs. Go find out a little about the history involved before you spout such nonsense. Not to mention that those who developed for KDE could have written their own toolkit from scratch, like GNOME did, instead of making use of Trollteches then completely propietary software. Miguel was not alone in opposing the then current licensce for QT. If he had been alone, GNOME would have never come into being. Your statement:
      "During the next few months, GNOME magically catches up to KDE"
      Is a) false b) incoherent and c) counter the values of the opensource community You imply that GNOME "took" things from already existing projects to implement their application base. Well, firstly, code reuse is the point of opensource software. Secondly GNUMERIC is not part of the GNOME desktop. And lastly GNOME did not "catch-up" to KDE- the fact remains the direction KDE is going and that of GNOME are different and there is no "catching up". GNOME is inferior to KDE as regards the tight-nit integration which KDE inherits from QT. But GNOME is superior in all things UI-from a solid HIG, through clear, graspable configuration defaults to an aesthetic touch par none in the Linux GUI world. Moreover GNOME has fundamentally changed its direction from the GNOME-1 days. IF a comparision were to be made one would have to compare GNOME1 with KDE2 -but with the advent of GNOME2 things are going in a markedly different direction, one which I believe is a better choice IMHO. Your statement:
      "In conclusion, GNOME is a failure"
      Is utter nonsense. GNOME has not failed, on the contrary it has garnered more support than KDE ever has had- I personally like aspects of KDE/QT but I refuse to use it as my desktop or to inflict it upon simple users as an administrator. For developers KDE is an awesome desktop- but not everyone is a developer and new users only need to click once on one config option and poof! something changed and they have no idea what they did nor how to reverse it..... You statement:
      "Which is very much the point--to fill Miguel's wallet (reality hurts, boys and girls)."
      What a load of bs. Certainly Miguel has profited from GNOME, he is a very industrious entrepreneur, but I guess the KDE-fan boys feel *morally* superior because instead of profitting themselves they just help Trolltech to their, substantially greater, profit.....OF course money is involved in these things: get a grip, money plays a role in almost all apects of life-but the values Miguel has expressed embody common values of the opensource community as opposed to those expressed by Trolltech. Go get a life, Mr. Fanboy. I'm sorry your feelings got hurt when GNOME2 came out and chose a different path- are you still recovering from those wounds ?
    12. Re:GNOME is a failure by Anonymous Coward · · Score: 0

      Even GNU says you should not license you're free software libraries LGPL.

      Read it more carefully. I wish people would stop misquoting that page. You should avoid the LGPL *IF* your code provides something that is unique and not already provided by proprietary code. Qt does not fall into that catagory... it's just a graphics toolkit. Putting it into the Linux desktop development toolchain would mean making Linux development more expensive than Windows, and tying it to one vendor... as well as sabotaging any commerical adoption of the Linux desktop.

    13. Re:GNOME is a failure by Anonymous Coward · · Score: 0

      Uhm, at the time the GNOME project was started, Qt was not GPLed.

    14. Re:GNOME is a failure by ultrabot · · Score: 2, Insightful

      But now it seems KDE is more "free software" than GNOME is.

      It's more RMS, not more free. GPL is not more free than e.g. LGPL or BSD, it's exactly the opposite.

      The "Lesser" LGPL license lets you make proprietary software by screwing over free software developers and using their libraries without giving anything back to the community that provided the entire platform you are developing on.

      It's in the interest of a library developer to have as many users as possible, proprietary or not. LGPL is in fact a recommended license for libraries, and GPL libs should be reserved for tasks where nothing else will do.

      The idea of a UI toolkit is not to offer anything revolutionary that would warrant GPL - just to offer a standard useful API to do the obvious. If you can only use the API to do GPL applications, well, that sucks.

      --
      Save your wrists today - switch to Dvorak
    15. Re:GNOME is a failure by damiam · · Score: 2, Interesting
      The way things are looking, I can hack one out in a few days. We will borrow from X, Y, and Z projects since they have most of the functionality we need. It will be a matter of fitting them all together. Thus, Gnumeric was born. And I am dead serious on this too.

      Nice story, but it's bullshit. Gnumeric couldn't have borrowed code because there was no one to borrow from. Neither KSpread nor OpenOffice Calc were around: Gnumeric was the first of the modern Linux spreadsheets. The only options around at that time Oleo and Siag. You don't get an app of Gnumeric's quality (it's probably the best OSS spreadsheet around, including OO.o) by copying all your code from Siag and Oleo.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    16. Re:GNOME is a failure by Anonymous Coward · · Score: 0

      The only reason Gnome still exists is because of giant egos. It's a shame to see such a complete and total waste of effort.

    17. Re:GNOME is a failure by Anonymous Coward · · Score: 1, Insightful

      Well it seems that although QT is now GPL'd, licensing for the commercial version still has a lot to do with this debate.

      Which is appalling. The entire reason that GNOME was started is because Qt wasn't GPLed. Qt was relicensed under the GPL, and Trolltech are now being shunned for doing exactly what everyone asked them to!

      Go ahead and accuse GNOME of borrowing things - but just remember KDE picked the existing off-the-shelf commercial QT toolkit

      I believe the original poster's point was that GNOME just picked up a load of code and threw it together. This is a completely different thing to basing your software around a well-designed toolkit. Simply glomming disparate systems together may get immediate results, but is terrible for long-term prospects. That is one of the reasons why KDE has shot ahead of GNOME in the past couple of years, IMHO.

      KDE decided to write KHTML instead of using Gecko, whilst GNOME is now going to use Gecko as their primary HTML layout engine in the DE. Which is better? I'd say Gecko is much more standards compliant than KHTML

      Yes, Gecko is more standards compliant. It's also loads more code, far more difficult to understand, needs much more resources, and not _much_ more standards compliant at all. If you look at the difference between the old version of KHTML and the modern day design, you will see an amazing amount of progress. This is not a coincidence.

      The point is that for really huge projects like a HTML layout engine, you need huge resources.

      A rendering engine isn't a massive amount of work. And the KHTML developers have clearly demonstrated that you don't need huge resources - they are 99% of the way to being a Gecko killer, simply by working smarter, not harder.

      KDE has changed their metaphors just as many times as GNOME, too.

      Huh? That's not true at all.

      Whatever happened to the taskbar stuck to one side of the screen?

      The taskbar, by default, has never been stuck to either side of the screen. You've been able to move it there of your own accord since at least KDE 1.0, IIRC.

      KControl and Konqueror have had their menus and sections reorganised several times. So what?

      So what? GNOME do things like switch out window managers and control panels. If all you can come up with for KDE is rearranging menus and stuff, then you've proved the OP's point.

    18. Re:GNOME is a failure by Anonymous Coward · · Score: 0

      those who developed for KDE could have written their own toolkit from scratch, like GNOME did,

      GNOME did no such thing. They used the already-existing GTK+ toolkit, which was originally written for the GIMP. Qt was chosen over GTK+ for KDE purely on technical merit.

      instead of making use of Trollteches then completely propietary software.

      That's an outright lie. Go and read the original QPL. In no way are you justified in calling it "completely proprietary".

      For developers KDE is an awesome desktop- but not everyone is a developer and new users only need to click once on one config option and poof! something changed and they have no idea what they did nor how to reverse it.

      Also complete bollocks. KDE can be run in kiosk mode, which prevents anything like this from happening. As far as I know, no such work has been done on GNOME.

    19. Re:GNOME is a failure by Anonymous Coward · · Score: 0

      wow you are good at flinginf lies and FUD.

      have you thought of running for congress?

      EVERY single thing you bring up applies to Windows.

    20. Re:GNOME is a failure by rabidcow · · Score: 1

      The "Lesser" LGPL license lets you make proprietary software by screwing over free software developers and using their libraries without giving anything back to the community that provided the entire platform you are developing on.

      How are you screwing them over if they CHOSE to allow this?

      And you are giving something back, just not in the form of source code. If the application you create has some unique value, then the platform is more valuable because of it. If it doesn't, then who cares about the source anyway?

    21. Re:GNOME is a failure by Anonymous Coward · · Score: 1, Insightful

      GPL is supposed to protect the users, by forcing the developers to release source code. The RESTRICTIONS on the GPL are intended to have a good effect in promoting free software.

      The GPL is LESS FREE than the LGPL, which in turn is LESS FREE than the BSD license. Less free because of more restrictions. The restrictions have a good effect for users so they are usually good.

      UserLinux wants maximum freedom for DEVELOPERS, so the platform will be rich with apps and thus attractive to users. Users can still insist on 100% free (GPL) software, no change there. But users who want to be able to choose either proprietary software or GPL can do that.

      I am both a user and a developer so I can see the advantages of GPL, LGPL and BSD from both sides. Perens is doing the right thing here IMHO.

      And you are just an idiot for claiming that the GNOME developers are somehow getting f***ed because of LGPL libraries in GNOME. Is QPL better than LGPL because you can pay $2000 for a dev kit instead of just $0? Yeah right that makes a lot of sense.

      But you can write GPL software for either one if you want, for $0 in each case.

  10. Bruce is right, I'll tell you why... by Janek+Kozicki · · Score: 2, Interesting

    I prefer gnome to KDE. And I see that KDE is more advanced.

    by Bruce's decision I see some hope for gnome to speed their development. That's why I think it is good.

    I also hope that decision about mozilla and gumeric + OOffice will solve their greatest problem: its own widget set. (I prefer galeon to mozilla - mainly because of native widget set == less bloated)

    to conclude: I think that Bruce made the best possible decissions, and I really hope it will be a great success.

    (btw, sawfish is my WM, not gnome, which for me is too bloated ;)

    --
    #
    #\ @ ? Colonize Mars
    #
    1. Re:Bruce is right, I'll tell you why... by zhenlin · · Score: 1

      Sawfish is the GNOME1 WM. GNOME2 uses Metacity, which is a lot more lightweight than Sawfish, but alot less configurable too.

  11. I'm pretty sure it wouldn't be "bastard" by Moth7 · · Score: 1

    Don't you keep up with poll choices you insensitive clod?

  12. re: why gnome over kde? by thedude13 · · Score: 1, Redundant

    what are the reasons for choosing gnome instead of KDE? i've read some of the white papers but i haven't seen anything that says why they are choosing gnome. i think KDE is a better desktop and should be included instead (i used to be a hardcore gnome user until KDE 3 and gnome 2 came out then i switched and haven't looked back), but if it doesn't fit with their model, it doesn't fit with their model

  13. Re:why ignore the obvious solution? KDE only! by Anonymous Coward · · Score: 0

    Maybe because Gnome is being pushed commercially by Novell, and Red Hat. It would make it easier for developers to only have to use one toolkit, instead of two. It would also bring support costs down. Since Novell, and Red Hat already went Gnome, it wouldn't make sense to go against the run of the mill.

  14. OK by Anonymous Coward · · Score: 0

    Each to their own.

    kde, gnome libs should be core libs for some distros. At least that way people can decide which wm to use.

    Do you remember when you were a kid and if you could not decide on something, your parents would make the choice for you.

  15. Re:why ignore the obvious solution? KDE only! by iamplupp · · Score: 5, Insightful

    please dont start the KDE vs Gnome war... KDE and Gnome should both do everything they can to get better while sharing between them as much as it's possible without removing their individuality. . I would prefer to have not one but two great desktop environments to choose from.

  16. Why the licensing argument is bogus by fritmebufstek · · Score: 5, Informative

    Try to find a commercial Gtk app. After googling, you'll perhaps find some from Ximian ( which can arguably be ruled out ), and perhaps a few more. Now try to find a commercial Qt app. You'll find hundreds ( including high-profile ones from Adobe and others ).

    This means that commercial developers are willing to pay for a quality toolkit, as much so on Linux as on other OSs. Free software folk needn't worry either, as Qt on X is free as in both.

    1. Re:Why the licensing argument is bogus by kosmosik · · Score: 1

      Try to find a commercial Gtk app.
      VMWare, Loki Games installer.

    2. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      These are not Gtk applications by any standard definition - you listed an installer and OS switching utility. Big deal.

    3. Re:Why the licensing argument is bogus by DAldredge · · Score: 1

      The makers of QT claim that you have to have a 1200 USD /DEV license IF, according to their site,
      "
      Use the Qt Commercial License to:
      Build commercial software.
      Build software that is not sold, but that advances the business goals of a commercial enterprise"

      With the makers of the toolkit saying you have to pay if you use software written with the toolkit to 'advance business goals' it brings pause to some.

    4. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      The KDE developers are making fools of themselves and showing what a bunch of childish flamers they are. For your information, GNOME (and by extension GTK) already has had two million commerical desktop deployments in the last few months alone -- with many more millions in the pipeline.

      Your claims that a few haphazard minor apps written with Qt as a base somehow prove it is better to act as base for UserLinux are ridiculous. I'm not surprised that the TrollTech shills are up in arms about this... there is a lot of money to be made ripping off developers for Qt licenses, if Qt can be *forced* into the linux development toolchain.

    5. Re:Why the licensing argument is bogus by fritmebufstek · · Score: 1

      That is the sales folk of TrollTech talking. It is arguably as wrong as MySQL's interpretation of the GPL. If your use of Qt is allowed under the GPL, you don't need a license. TrollTech cannot in any way limit the rights they have already given you under the GPL.

    6. Re:Why the licensing argument is bogus by arvindn · · Score: 4, Insightful
      The reason there weren't too many commercial apps was that until recently gtk lagged far behind Qt. (The gtk file selector was a joke, for example). But gtk2 was a vast improvement, and now the 2 are for practical purposes equal. (File selector is getting fixed in 2.6). So expect to see a lot more gtk apps soon.

      And its not like there aren't any now. Mozilla uses gtk (though not exclusively) and netscape which is based on mozilla is closed source. This wouldn't have been possible if gtk were GPL. Similarly for openoffice and staroffice.

      Thirdly, big companies like Adobe can pay for Qt. But userlinux is targeting much smaller enterprises as well, and its doubtful if they can.

      Fourth, there's the issue of control. What insurance do you have against Qt jacking up the price of a developer license?

    7. Re:Why the licensing argument is bogus by DAldredge · · Score: 1

      That may be true.

      But who do you think the PHB's will listen too?
      And why would you want to trust a company that lies about when you have to buy a license?

    8. Re:Why the licensing argument is bogus by manyoso · · Score: 4, Informative

      More reasons why the licensing argument is bogus:

      The emerging Linux cell phone market: choice? Qt
      IBM PDA reference implementation: choice? Qt
      Adobe? Qt
      Samsung? Qt
      Sharp? Qt
      Boeing? Qt
      Daimler? Qt
      Chrysler? Qt
      Disney? Qt
      Fujitsu? Qt
      General Electric? Qt
      Hitachi? Qt
      Honda? Qt
      HP? Qt
      IBM? Qt
      Intel? Qt
      Mitsubishi? Qt
      NASA? Qt
      NEC? Qt
      Shell? Qt
      Siemens? Qt
      Sony? Qt
      Toshiba? Qt
      Toyota? Qt
      Unilever? Qt
      Volkswagen? Qt

      Hmm, I'm starting to sense a pattern here. Now, go find the list of ISV's or commercial companies developing with GTK+. And no, RedHat and Sun don't count. Why you ask? Because they are distributions silly. You didn't see me listing all the distributions that support or prefer KDE/Qt.

      And yet another reason the so-called licensing issue is bogus? The FSF prefers GPL'd libraries as a matter of principle. Not LGPL. That is why they changed the name to 'Lesser' and put up the why-not-lgpl paper. So, the FSF would rather Qt and GTK+ were both GPL with *no* ability to support proprietary developers... gratis or otherwise. Besides, shouldn't the community benefit from some form of recompense from proprietary developers using our Free systems? Yes, we should and with Qt, we do.

      Some community names went around spreading this ridiculous 'licensing problem' with Qt as deliberate FUD. And now we all have to clean up after their mess.

    9. Re:Why the licensing argument is bogus by fritmebufstek · · Score: 1

      As I said, a few others. Now compare that to the number of commercial Qt apps.

    10. Re:Why the licensing argument is bogus by Ianoo · · Score: 1

      Ximian's apps aren't commercial, for the most part they sell support packages and their code is still available under the GPL.

      The licensing argument is still very much a valid one, however. I heard that the only reason Sun's Java Desktop is built on GNOME and GTK is because they were scared of QT's licensing costs. The rumor is they even considered buying out TrollTech and releasing QT under the LGPL, but sadly no. Sun's work on moving StarOffice/OpenOffice to a more sane toolkit will be to GTK rather than QT for the same reasons.

    11. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      I don't care : Qt is GPL. It does not belong to a company anymore, but to the community of GPL developers.

    12. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      Ahh yes the Games installer, just what every corporation needs.

      asshat

      Go back to yer WINE

    13. Re:Why the licensing argument is bogus by jmorris42 · · Score: 3, Insightful

      How about another major Gtk vs Qt advantage. Go look at the GNU Win CD or The Open CD and count the Qt/KDE apps. Or let me save you the time and do it for you. Zero. Think that just might matter to Enterprise customers working in a diverse environment?

      The pisser with the Qt license is that a project must decide before writing the first line of code which license they plan to release under and you can't change your mind later. You can't dual license either. And if you opt for free you can never port to an unfree system.

      The KDE camp still refuse to admit they made an unholy alliance with the devil and will forever be damned for it. The GNOME camp saved the Free Software world by realizing the danger and running balls to the wall to quickly organize themselves and catch up close enough to KDE/Qt to prevent it from ever becoming a defacto standard.

      --
      Democrat delenda est
    14. Re:Why the licensing argument is bogus by Lussarn · · Score: 1


      These are not Gtk applications by any standard definition

      totaly laughable. Can you point me to the standard definition of an application using Gtk. I haven't found one using google.

    15. Re:Why the licensing argument is bogus by DAldredge · · Score: 1

      Maybe you don't.

      But the people who sign the check, they care.

    16. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 1, Insightful

      >And if you opt for free you can never port to an unfree system.

      Laughable. This is the case for every GPL code. Don't use Linux then.

    17. Re:Why the licensing argument is bogus by fritmebufstek · · Score: 1

      Why would a Linux distro have to worry about its toolkit not being free on Windows ? And about you calling TT the devil, that's just ridiculous. They have made available a great toolkit under the GPL, and have committed voluntarily to continue to do so indefinitely. This deserves a lot of respect.

    18. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      totaly laughable. Can you point me to the standard definition of an application using Gtk. I haven't found one using google.

      Your spelling alone is totally laughable.
      Please use your precious Google to find out how to think objectively.

    19. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      We are talking about KDE and Gnome there, not about GPL vs GTk, or paying for widgets for some closed-source applications. The Qt licensing is NOT a problem for KDE developpers : it is GPL so it is free, as Gnome or the kernel are.

    20. Re:Why the licensing argument is bogus by ultrabot · · Score: 2, Insightful

      More reasons why the licensing argument is bogus

      It's a different thing to voluntarily choose a commercial toolkit, and be forced to pick one because it is the only way to get the LAF right for the desktop platform.

      Besides, shouldn't the community benefit from some form of recompense from proprietary developers using our Free systems? Yes, we should and with Qt, we do.

      Community wouldn't benefit. Trolltech would.

      I think it's simply better to use some of the money that the companies will save by Peren's choice of GTK and use it to improve GTK. This money will be well spent and the fruits will benefit the companies and the developer community as a whole, instead of paying for development of something they have to purchase again and again.

      Choosing Qt will make the companies bitches of Trolltech for all eternity.

      --
      Save your wrists today - switch to Dvorak
    21. Re:Why the licensing argument is bogus by fritmebufstek · · Score: 1

      "Gtk is _now_ equal to Qt, important issue will be fixed in 2.6". ( freely quoted, emphasis mine ) Small companies can certainly pay for Qt. I know a lot of people ( lots of them KDE developers ) who own small companies that develop exclusively Qt based software. For commercial developers, the money they save through the quality of Qt ( develop faster == pay less developers ) is easily worth the license ( which amounts to one tenth of the price of a single developer ).

    22. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      >What insurance do you have against Qt jacking up the price of a developer license?

      The GPL licence...

    23. Re:Why the licensing argument is bogus by fritmebufstek · · Score: 1

      Another argument is that making KDE the default desktop does not in any way force 3rd party developers to use Qt if they don't want to. Gtk apps run perfectly on KDE desktops.

    24. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      Actaully there are MANY commercial GTK apps. There are MANY commerial GTKmm apps! Go read the GTKmm mailing list and you'll see company names in emails, that if you work hard you can find that they use GTK. Most of these companies just don't publisize that they use GTK because it pointless.

      Now answer me this, show me a commercial grade app using KDE libraries as well.

    25. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      I meant : GPL vs LGPL or BSD licence.

    26. Re:Why the licensing argument is bogus by vidarh · · Score: 2, Insightful
      You're conveniently listing large corporate and government users for which the QT license fee is peanuts.

      And pointing out that the FSF prefers the GPL is hardly a good argument for why one should choose a GPL'd toolkit for a distro intended for enterpise users... The FSF is hardly a bastion of support for corporations.

    27. Re:Why the licensing argument is bogus by manyoso · · Score: 1

      "It's a different thing to voluntarily choose a commercial toolkit, and be forced to pick one because it is the only way to get the LAF right for the desktop platform."

      That is why the KDE proposal specifically includes GTK+ support ;)

      "Community wouldn't benefit. Trolltech would."

      Both the community *and* Trolltech benefit. We all benefit. And that is the point. Trolltech makes Free Software which the community benefits from. Get it?

      "I think it's simply better to use some of the money that the companies will save by Peren's choice of GTK and use it to improve GTK. This money will be well spent and the fruits will benefit the companies and the developer community as a whole, instead of paying for development of something they have to purchase again and again."

      This is dumb. Trolltech uses the money to pay for improvements to Qt which the community benefits from. That money is well spent and the fruits benefit the companies and the developer community as a whole. Oh, and the developers don't have to pay TT 'again & again'.

      You are reduced to an anti-TT rant which makes no sense. TT supports the community.

    28. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      It's a different thing to voluntarily choose a commercial toolkit, and be forced to pick one because it is the only way to get the LAF right for the desktop platform.

      Did you not read the article? (Why did I even ask that?)

      UserLinux will not even have the Qt libraries.

      UserLinux will not support Qt.

      At all.

      If you try to run Qt software on an out-of-the-box UserLinux installation, it will not work.

      If the companies listed by your parent switch to UserLinux, they will actually have to waste money producing their own UserLinux derivative with Qt support, in order to continue to use the proprietary software they currently have.

      I can respect the decision to go with Gnome as a GUI, but I simply do not understand Perens' decision to exclude Qt completely.

    29. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      > was that until recently gtk lagged far behind Qt.

      They still lag behind in multiple areas.

      > The gtk file selector was a joke, for example)

      It's still a joke!

      > File selector is getting fixed in 2.6

      You are aware of the fact that it was meant to be fixed for Gnome 1.4 already, promised to be fixed for Gnome 2.0. You are aware that this promise has been delayed to Gnome 2.2 ("It will really make it this time!") and now that Gnome 2.4 has been released yet again delayed to 2.6? On which moon behind neptune are you living?

      > But userlinux is targeting much smaller enterprises as
      > well, and its doubtful if they can.

      It even scales better for small companies as they can't afford wasting salary on their GUI-person just to produce source code which is three times as large, changes the API monthly, changes the "future vision" ("Corba, Bonobo, Mono") quarterly (without successfully delivering any of these completely) and with documentation that you wouldn't even give to your most evil foe.
      Qt in comparison delivers an excellent API, excellent documentation, true cross plattform support and has proven to work for thousands of customers.
      Given that $1500 is a developer's weekly salary nobody will take these costs into account (and if you really have to Trolltech will permit you to use Qt in advance for a half year without payment as part of their startup program).

    30. Re:Why the licensing argument is bogus by manyoso · · Score: 1

      "You're conveniently listing large corporate and government users for which the QT license fee is peanuts."

      Oh? Would you like me to list the number of small/independent ISV's that have chosen Qt? That list is larger than the one above.

      BTW, I pointed out the FSF argument to preempt the inevitable erstwhile FSF developer crying, "... but what about freedom for the poor proprietary developers?" which is inevitably issued when so-called 'license issue' supporters fail with all the other arguments.

    31. Re:Why the licensing argument is bogus by ultrabot · · Score: 1

      That is why the KDE proposal specifically includes GTK+ support ;)

      It has a vague promise, but I would like to *see* KDE running on GTK+. The choice has to be made now, and there is no GTK-KDE *now*.

      Mostly it refers to Freedesktop and doesn't really promise that KDE will run on Qt.

      Both the community *and* Trolltech benefit. We all benefit. And that is the point. Trolltech makes Free Software which the community benefits from. Get it?

      The money will come from the corporations that are paying for the development of UL. It's fair to not expect the companies to pay the Trolltech tax whenever they want to develop some closed source stuff on the platform.

      If I was a company that considered financing UL, I would heavily question the choice of Qt as the default toolkit.

      You are reduced to an anti-TT rant which makes no sense. TT supports the community.

      I'm emphatically not anti-TT. They have a great business model, nothing wrong with that. I just want to see UL succeed, and Gtk way is easier to sell to commercial companies. Many companies would cringe if they were told that developing for Linux is more expensive than developing for Windows. Especially if they are operating on low margins, which are becoming more commonplace.

      If I was to start developing a closed source application (I could, if I lost my day job or whatever) Qt would not be an option for me. Only the big/medium size ones with steady income can afford it.

      --
      Save your wrists today - switch to Dvorak
    32. Re:Why the licensing argument is bogus by ultrabot · · Score: 1

      UserLinux will not support Qt. At all.

      One word: apt-get. It's still debian.

      If the companies listed by your parent switch to UserLinux, they will actually have to waste money producing their own UserLinux derivative with Qt support, in order to continue to use the proprietary software they currently have.

      I suppose it will be easy to run a company-standard customization script to install whatever was not installed that is needed.

      --
      Save your wrists today - switch to Dvorak
    33. Re:Why the licensing argument is bogus by twistedcubic · · Score: 1

      Maybe it's because QT resembles MS Windows more than GTK, or some other non-technical reason. That Gnome contains Evolution is probably a big reason nobody mentions. By the way, some of the companies you list above write GTK apps, though I'll give you the benefit of the doubt on all of this since I'm not going to bother to do the research.

    34. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      well that makes sense. I shouldn't use GNOME because it can't run QT applications.

      OMG Userlinux is SCREWED

    35. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      Well, VmWare is definitely Gtk+ and it's definitely an application. Why isn't it a Gtk application?
      Btw. VmWare isn't OS switching utility. (What ever that means) It's a virtual machine application.

    36. Re:Why the licensing argument is bogus by LMCBoy · · Score: 2, Interesting

      It has a vague promise, but I would like to *see* KDE running on GTK+. The choice has to be made now, and there is no GTK-KDE *now*.

      You don't understand. The KDE proposal sugests that UL include both Qt and GTK libraries, it says nothing about trying to "port" KDE to GTK, which is a completely ridiculous prospect.

      If I was to start developing a closed source application (I could, if I lost my day job or whatever) Qt would not be an option for me. Only the big/medium size ones with steady income can afford it.

      Oh, who cares? If you want to develop and distribute closed source apps, why don't you do it on Windows? In case you didn't notice, the Linux culture values freedom. [Note that this does not include most "enterprise" software development, which is typically for internal use only. In this case, they can simply use the Free Edition of Qt. As long as they never distribute the code, they don't have to abide by the GPL.]

      --
      Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
    37. Re:Why the licensing argument is bogus by Kashif+Shaikh · · Score: 1

      "Fourth, there's the issue of control. What insurance do you have against Qt jacking up the price of a developer license?"

      What assurance do you have that GTK2.4 is going to be compatible with GTK2.8?? As an end-user who doesn't contribute code but uses the library - you want a library that has a firm API. Case in point: GTK1.x apps had to be re-written to take advantage of GTK2.x. Because it happened in the past, it can happen in the future. You should also look at what redhat did - people didn't care much about open-source, but the fact they eliminated RHN for RH9 etc.

      Besides, the developer license is only a measly $1500 per developer(one platform). This isn't a royalty, but a one-time fee(they're charing people who use the developer-tool not end-users). Compared to the annual salaries of programmers(i.e. 50K+), it would only cost the company 1/50th of a persons salary. This cost is re-couped with ROI on the good, stable API with good documentation resulting in more productivity. Plus if you find a bug, Trolltech will fix it for you. Not too bad for $1500 bucks.

    38. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      which is three times as large,

      GTk/GNOME is a hell of a lot less bloated than KDE/Qt.

      changes the API monthly

      GNOME and GTK have committed to both API and ABI (you do understand the difference, don't you) backwards compatiblity for the entire 2.x series, and it is tested and checked very carefully -- not something the KDE project has ever done. It was a preqreuisite of SUN (and others) choosing it for their desktop.

    39. Re:Why the licensing argument is bogus by ultrabot · · Score: 1

      The KDE proposal sugests that UL include both Qt and GTK libraries, it says nothing about trying to "port" KDE to GTK,

      Well, they promise some kind of integration. I expected this to mean that Gtk apps will look like Qt apps in the future, if that is wanted.

      Oh, who cares? If you want to develop and distribute closed source apps, why don't you do it on Windows?

      So basically you are suggesting that Linux is only good for OSS apps? I tend to believe in the commercial success of Linux in the near future, my app might only be usefull in context of Linux, or the company I am writing my app to uses Linux on desktops.

      In case you didn't notice, the Linux culture values freedom.

      Perhaps you tried to write GNU/Hurd culture?

      The freedom might be severely compromised if we don't get significant corporate backing (and subsequently, corporate dependency on Linux). Some big company (with more serious claims than SCO) might choose to squash Linux, and if we don't have lots of wealthy corporate users, we just might be screwed.

      --
      Save your wrists today - switch to Dvorak
    40. Re:Why the licensing argument is bogus by platypus · · Score: 1

      Thirdly, big companies like Adobe can pay for Qt. But userlinux is targeting much smaller enterprises as well, and its doubtful if they can.

      Yeah, as can be seen on the fact that no small graphic studios exists because they can't afford photoshop, no small windows shop exists because they can't afford Visual C, no small groceries exist because they can' afford a cash register and so on.

      Fourth, there's the issue of control. What insurance do you have against Qt jacking up the price of a developer license?

      GTK, that's why it should be included in Userlinux.

    41. Re:Why the licensing argument is bogus by cmbofh · · Score: 0

      >> which is three times as large,
      > GTk/GNOME is a hell of a lot less bloated than KDE/Qt.

      Oh come on, please don't quote out of context. He was referring to the source code *the developer* needs to write:

      >> It even scales better for small companies as they can't afford wasting salary on their GUI-person just to produce source code which is three times as large...

      You're not seriously suggesting that you need more code when programming for KDE than for GNOME, are you? If you do please back that up with some numbers.

      George Staikos knows both:
      "Based on my experience porting GTK applications to Qt, the resulting code is typically 30%-60% smaller than the GTK equivalent (in terms of lines of code)."

      I won't comment on the general bloat level of GNOME vs. KDE but I've yet to see any real comparison between the two that's beyond mere prejudice.

    42. Re:Why the licensing argument is bogus by platypus · · Score: 1

      he FSF prefers GPL'd libraries as a matter of principle. Not LGPL. That is why they changed the name to 'Lesser' and put up the why-not-lgpl paper. So, the FSF would rather Qt and GTK+ were both GPL with *no* ability to support proprietary developers... gratis or otherwise.

      Yeah, it's really annoying that certain FSF people which don't have a problem to comment on anything and the kitchen remain silent on this fact for so long.

    43. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      And BTW: the vast majority of code is in the backend... the page you quote was a) written by a zealot, and not a genuine comparison, b) missing the point by a mile, c) mostly inaccurate.

    44. Re:Why the licensing argument is bogus by platypus · · Score: 1

      Maybe it's because QT resembles MS Windows more than GTK ...

      Which is actually a damn good reason to _include_ QT in UserLinux. Why is left as an exercise to the reader.

    45. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      [ Long list of TrolTech customers ]

      What are you, a TrollTech salesman?

      Look, dipshit, any company in IT can produce a long list of customers. BORING. I bet all those companies are using Visual Basic and SCO Unix as well. So what.

      But, I love how you came out of the closet and announced yourself as TrollTech's little bitch. It's long been suspected that KDE is merely a front for TrollTech and their sales ambitions, but please show good sense and avoid saying so in public.

    46. Re:Why the licensing argument is bogus by alienw · · Score: 1

      Who the fuck writes commercial apps in fucking PYTHON, you dumbass?

    47. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      What the hell does that have to do with it, thicko. You can write "commercial" apps in any language. The point is: the LOC has nothing to so with the toolkit... I suppose it was a little bit too subtle for your kind.

    48. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      Red Hat? All of their stuff is Python, from the installer to the redhat-config-* to up2date.

    49. Re:Why the licensing argument is bogus by damiam · · Score: 1
      Case in point: GTK1.x apps had to be re-written to take advantage of GTK2.x.

      QT 1.x and 2.x were also source incompatible. What's your point?

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    50. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      Who the fuck writes commercial apps in fucking PYTHON, you dumbass?

      Yeah, real commercial apps are written in Visual Basic.

      Get real. Commercial development can be and is done in every language, from assembler to shell scripting and everything in between. Python is a better tool than most of the other options. For some project it's a better tool than all of the other options.

    51. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      Well for the big names it is not really a deal to get a commercial qt license. But there is a real problem there, I know at least of one or two excellent shareware projects which would be badly needed on the linux side, the reason, the developer simply could not afford to fork out a whopping USD 1000 for his project and he simply didnt want to go the GPL route.

      Another project which I remember was IBM themselves, who simply could not do a Qt/KDE port of eclipse due to GPL reasons, the GPL is sort of legally incompatible to their license, given the bad speed of the GTK version of eclipse a QT port would have been badly needed.

      s solution would be a little bit more flexibility for TrollTech towards smaller developers with a more flexible per sold copy license or small developers license.

    52. Re:Why the licensing argument is bogus by madhippy · · Score: 1

      [Note that this does not include most "enterprise" software development, which is typically for internal use only. In this case, they can simply use the Free Edition of Qt. As long as they never distribute the code, they don't have to abide by the GPL.]

      most enterprises outsource dev work to 3rd party software companies - software is perhaps 'internal' to the enterprise, but my understanding of the Qt licensing would indicate that this is commercial development - i.e. you can't use the free edition, you have to buy the commercial edition.

      one disadvantage of any sort of licensing issue is the administration of the licences - i.e. you've got to audit that you have the right number of licences or face potential fines etc, there's also the lag time, add a developer to a project and wait a few weeks for the licence purchase order to go through...

    53. Re:Why the licensing argument is bogus by Elektroschock · · Score: 1

      Statement in KDE CVS digest:

      "The big fuss this week was the exclusion of QT, and and by extension, KDE from UserLinux. The main reason being that QT is licenced under the GPL, with the option of a closed source license for proprietary development. So with a stroke, about half of the desktop developers are excluded from an initiative that among other things targets the enterprise desktop. I believe that this shows a fundamental misunderstanding of the economics of free and open source software. What is the scarce resource? Is it customers and users? I don't think so. The value proposition in FOSS is so good, customers will come. The scarce resources are developers. One wonders at the wisdom of pissing off half of your most valuable resource.

      Paradoxically, this situation will incite many to code. Peter Rockai committed two Debian focused projects, both of which have goals of simplifying the configuration of KDE for Debian users. One is a DebConf front end, the other an Apt front end. Zach Rusin extended KConfEdit, adding the capability of configuring KDE over the network. No, neither KDE or Gnome are going away soon."

    54. Re:Why the licensing argument is bogus by Gnulix · · Score: 3, Funny

      >>The gtk file selector was a joke, for example)
      >It's still a joke!

      ...and a bad one at that!

    55. Re:Why the licensing argument is bogus by Gnulix · · Score: 1

      Many companies would cringe if they were told that developing for Linux is more expensive than developing for Windows.

      Why is it more expensive to develop using QT than Windows? Tools cost money as well and it isn't like all development libraries are free in the Windows world. Just take a look at what some third party suppliers charge for their Windows stuff!

      The most important point is; with QT only the developer needs a license, not all end users. You know what? With Windows you need, at least, a Windows license...

      Especially if they are operating on low margins, which are becoming more commonplace.

      Bruce keeps referring to this being an enterprise distro. So it isn't target at your typical mom'n'pop store. A company that calls itself an enterprise and can afford a couple of QT licenses is seriously screwed up (ala the old dot-com:ers.)

    56. Re:Why the licensing argument is bogus by Bimble · · Score: 1

      I thought the point of UserLinux was to encourage businesses to use Linux as a desktop OS. The argument that it should choose an interface API based not on what businesses are already using but instead on what you'd _like_ them to use shows that you're not thinking like an enterprise customer.

      If you want UserLinux to see widespread adoption in the enterprise, you need to be able to point to all those big names who already use libraries included in the distro. You need to throw in the QT libraries at the very least, so you can broaden the software support of the distro. If the best people can come up with is, "Use apt-get," it's definitely heading nowhere. In the enterprise, users usually aren't going to have the privileges to run apt-get on their own machines.

      Personally, I'm not enthusiastic about the project in any event. After proposals to use UserLinux get filtered through a few meetings before getting to the decision-makers, the only argument they'll hear is, "You should standardize on our desktop instead of on the desktop that you already have in place." If every aspect of the distro is standardized on one technology and one alone, you won't even have "flexibility" as a selling point.

      --
      Naked.
    57. Re:Why the licensing argument is bogus by Gnulix · · Score: 1

      I suppose it will be easy to run a company-standard customization script to install whatever was not installed that is needed.

      But then you are pretty muched screwed when it comes to commercial support. Then you might as well use a standard Debian distro!

    58. Re:Why the licensing argument is bogus by don.g · · Score: 1
      If you want to develop and distribute closed source apps, why don't you do it on Windows?

      Because I'm no great fan of Windows - I like the unix development environment too much.

      In case you didn't notice, the Linux culture values freedom.

      Er. Who do you mean by "the Linux culture", and what do you mean by "freedom"? Do you mean the freedom to use closed-source software in kernel development?

      --
      Pretend that something especially witty is here. Thanks.
    59. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      Because giving users a system that looks a lot like Windows but then catches them out on the fine details provides hours of amusement to the techies?

    60. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      It isn't so much the costs for their own development, it's that they need a platform they can provide to their customers, and obviously they're going to build on that same platform themselves. Telling their customers that they have to pay a third party if they want to build apps on the platform Sun is providing them with is not considered to be a valid option. Especially as there can be no guarantees as to how much that cost might be in the future.

    61. Re:Why the licensing argument is bogus by IamTheRealMike · · Score: 2, Insightful
      Hmm, I'm starting to sense a pattern here. Now, go find the list of ISV's or commercial companies developing with GTK+.

      In fact quite a few do, especially when writing software specifically for Linux. For instance, VMware, Real, Loki, there was some photo website company who support Linux (can't remember their name now) who have a GTK app to upload images and stuff.

      Really, having a big list of companies who use Qt is not that useful. The fact is that NO major platform in existence today requires you to pay big bucks to write proprietary software for their platform. Not Windows, not MacOS - Linux should be no different. It'd be a serious competive disadvantage if it did. Yes, Apple and Microsoft charge for developer tools but it's nonetheless possible (and with stuff like .NET these days even easy) to develop for the platform entirely for free, and sell the resultant products as proprietary software.

      And yet another reason the so-called licensing issue is bogus? The FSF prefers GPL'd libraries as a matter of principle.

      It may have escaped your notice that most people ignore the FSF. The FSF (or really RMS) recommends people refer to Linux as "The GNU system, powered by the Linux kernel" or something like that. Yet nobody does.

      That's because while RMS and the FSF have some great ideas (and software), not everything they say makes sense. This is one such thing.

      The FSF want libraries to be GPL because they want all software to be GPLd, eventually. In fact, this could be achieved by making glibc GPLd, and in fact at one point RMS did try and do that - the glibc maintainers publically disowned him despite being long time GNU developers (some of the earliest in fact).

      Besides, shouldn't the community benefit from some form of recompense from proprietary developers using our Free systems? Yes, we should and with Qt, we do.

      This line of reasoning is an extremely poor one IMHO - by this logic don't all free software developers deserve recompense? What about server developers who couldn't care less about widget toolkits? Don't they deserve recompense from proprietary developers too?

      I know - why not make most of our libraries GPLd? Oh yes, I know why: because then there'd be no proprietary developers at all.

      In fact that's the main argument against Qts licensing - it's a slippery slope. Why should the widget toolkit be special? glibc is perhaps just as important, why not make that GPLd too?

      Some community names went around spreading this ridiculous 'licensing problem' with Qt as deliberate FUD. And now we all have to clean up after their mess.

      That's an interesting viewpoint. The alternative view is this: if the original KDE developers had paid more heed to the ideology of the FSF (the organization they now claim as allies so willingly) and simply worked on a new widget toolkit (maybe GTK, maybe something else) rather than take a convenient shortcut, there'd be no mess to clean up! We'd have one major desktop environment which would have more people working on it. There would be no licensing flamewars, no KDE vs GNOME trolls. We'd just be getting on with building a great desktop.

      It's certainly a powerful lesson for the future - the only thing that makes our platform different is the licensing, the way we let anybody who wants to use it, modify it, and build upon it.

      If we don't have that, we might as well just let Apple and Microsoft duke it out.

    62. Re:Why the licensing argument is bogus by IamTheRealMike · · Score: 1
      Why would a Linux distro have to worry about its toolkit not being free on Windows ?

      A Linux distro might not, but there's a lot of free software developers still on Windows you know. Portability has always, right from the start, been a big concern of the GNU project. Linux is only one (albiet the flagship) free software project.

      The whole point of free software is that anybody should be able to use it - white or black, muslim or christian, criminal or saint, Windows user or Linux user. The point is not to play favourites, or to try and "lock in" people to Linux, despite the temptation.

    63. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 1, Insightful

      Im sorry, but this is only half of the problems, yes you have the better license in gnome, but face it.
      KDE has one of the nicest cleanest APIs out there in existence (probably the best one since BeOS went down) whereas gnome is an awful collection of mediocre C based apis where they tried to put a little bit of OO on top of it making things even harder to code for, apple made the same mistake in the past and microsoft still does, apple already moved away from the OO in C concept to a much saner one microsoft is on its way. Gnome especially ximian also wants to do that but gets into the patent shooting sight of microsoft that way.

      Im sorry, but if time constraints are my real problem which it normally is I honestly would consider to pay the high bill to TrollTech for a commercial app and hook myself into KDE instead of going the gnome way and having to pay with a much longer development time.

      Technically kde is by far superior to anything from the gnome side. From the UI side like it or hate it but gnome died for me when they took out the splitting and tabbing in nautilus and even removed the html viewing (which you at least can put back in), i prefer a split view instead of digging myself through 200 layered windows to find the right one for the directory I need to access.
      Not the situation on the KDE side is ideal, for small developers the unflexible Qt license is a real problem, but things are not rosy on the gnome side either and wont be for a long time.

    64. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      No the Qt does not really resemble windows API wise, the Qt is more like a cleaned up java swing api, excellent toolkit to code for there is no better out there and an excellent showcase of what you can do with a sane usage of the C++ api. API wise GTK is a real mess, but very close to the really awful win32 api for windowing, which makes it really a mess.

    65. Re:Why the licensing argument is bogus by Natalie's+Hot+Grits · · Score: 1

      "Community wouldn't benefit. Trolltech would."

      Trolltech IS the QT Community. When trolltech benefits, everyone benefits because of better QT.

      Qt's price is why you can port a linux QT app to the mac in negligable time... for free.

      Qt's price is why you can write KDE with all its features and quality in the amount of time it has taken... for free.

      Qt's price is why Qt is the easiest to use, most robust, simplest, highest performance, and most powerful GUI toolkit available... for free.

      Qt's price is why Konquror is the lightest weight, fully featured, fastest, and most compliant web browser on the planet... for free.

      Qt's price is what makes Quanta become the best web development kit on the linux platform... for free.

      Everyone who uses the desktop (including windows users who unknowningly install Qt applications) will benefit from trolltech's profits.

      --
      Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.
    66. Re:Why the licensing argument is bogus by be-fan · · Score: 1

      One word: apt-get. It's still debian.
      >>>>>>>>>>
      Not on an enterprise desktop.

      --
      A deep unwavering belief is a sure sign you're missing something...
    67. Re:Why the licensing argument is bogus by Spoing · · Score: 1
      The sticking point for QT is that it's an either/or situtation for commercial apps. *IF* it starts out GPL, and you want to move it into the commercial arena, you CAN'T; the licence doesn't allow it.

      You have to know up front that the app will be commercial and buy a QT licence first.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    68. Re:Why the licensing argument is bogus by autopr0n · · Score: 1

      Thirdly, big companies like Adobe can pay for Qt. But userlinux is targeting much smaller enterprises as well, and its doubtful if they can.

      If you can't afford Qt, then you probably can't afford to pay programmers, or even to buy computers for them to program on.

      The vast majority of bussness do their coding in house and don't release it. They can still do this with the GPL'd QT (although trolltech would like them to purchace a license). And if that's not good enough, they can still write KDE aps using GTK.

      --
      autopr0n is like, down and stuff.
    69. Re:Why the licensing argument is bogus by mccoma · · Score: 2, Informative
      Yes, Apple and Microsoft charge for developer tools

      Apple gives the development tools away with the OS or the tools can be downloaded (after registering).

    70. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0
      But gtk2 was a vast improvement, and now the 2 are for practical purposes equal.

      I've programmed with qt3.x and gtk2.x under both gnome and kde desktop environments. I can't agree that the two are equal. I want to give gtk/gnome a nod because I started in that environment. But IMHO qt/kde is far superior to gtk/gnome. Will gtk/gnome continue to get better? Yes, and so will qt/KDE.
    71. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 1, Interesting
      Yes, Apple and Microsoft charge for developer tools but it's nonetheless possible (and with stuff like .NET these days even easy) to develop for the platform entirely for free, and sell the resultant products as proprietary software.

      Apple and Microsoft charge a license fee for their runtime/desktop, so you aren't comparing apples to apples here.
      The alternative view is this: if the original KDE developers had paid more heed to the ideology of the FSF (the organization they now claim as allies so willingly) and simply worked on a new widget toolkit (maybe GTK, maybe something else) ...

      First you presuppose the KDE developers didn't consider this issue, which is a big assumption. Second, you present a scenario where there never would have been the quality KDE we have today. I say the KDE/Gnome competition have been a good thing for both desktop environments.
    72. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      I work for a small company and we use Qt exactly because we can't afford to work around a toolkit with important functionality missing and documentation lacking. Sun and other big companies can build internal support for 'improving' Gtk and leverage that commercially.
      We need something that just works because we must concentrate on our core business. (Well, actually, Sun should too because we have a far better return on investment than they have)

    73. Re:Why the licensing argument is bogus by TKinias · · Score: 1

      scripsit be-fan:

      Not on an enterprise desktop.

      Not what on an enterprise desktop? No apt-get?

      If the firm requires qt apps, the admin does the relevant apt-get when he makes the image that all the desktops will use. If the users aren't installing unauthorized software, and the firm doesn't have any standard qt software, then the lack of qt libs is irrelevant.

      --
      In principio creauit Linus Linucem.
    74. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0
      Show us where the FSF states that a propietary+GPL license is better than a LGPL one. The FSF says that in some cases (where the free software library doesn't have competition from a similar proprietary one), a GPL only license is preferred because it can give free software an advantage. Ie free software can use this library and proprietary programs can't.

      Now tell us how this argument applies to Qt.

      This has been pointed out many times. The continual use of this argument by KDE developers just comes down to lying.

    75. Re:Why the licensing argument is bogus by benjamindees · · Score: 1
      Thirdly, big companies like Adobe can pay for Qt. But userlinux is targeting much smaller enterprises as well, and its doubtful if they can.

      Give an example of a company that can afford to do in-house development but can't afford to purchase Qt.

      --
      "I assumed blithely that there were no elves out there in the darkness"
    76. Re:Why the licensing argument is bogus by jmorris42 · · Score: 1

      Wrong. GIMP runs just fine under Windows. A GPLed Qt app could not be so ported without violating the Qt license. You don't have to believe me, go read the license.

      --
      Democrat delenda est
    77. Re:Why the licensing argument is bogus by Keith+Russell · · Score: 1

      Amen, brother!

      Portability has always, right from the start, been a big concern of the GNU project.

      And portability has also been Qt's most distinctive feature. Just pay attention to the fact that you can have portable or Free, but not both.

      The point is not to play favourites, or to try and "lock in" people to Linux, despite the temptation.

      I can't emphasize that enough. It's Trolltech's bad attitude in a nutshell. Their motivation is revenge against Microsoft Corporation. It's developers and end users that take the damage, though.

      --
      This sig intentionally left blank.
    78. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      > GNOME (and by extension GTK) already has had two million commerical desktop deployments in the last few months alone -- with many more millions in the pipeline.

      You mean, the _potential_ for two million commercial desktop deployments by 2006? You just don't roll out two million desktops just like that :)

    79. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      > Look, dipshit, any company in IT can produce a long list of customers.

      OK, then please get a list of companies like this which use GTK . Why that during all these discussion nobody has come up with such a list ?

    80. Re:Why the licensing argument is bogus by fault0 · · Score: 1

      > Loki Games installer.

      The Loki Games installer is actually open source. The reason gtk was selected over Qt is that the toolkit needed to be shared linked, and the fact that gtk 1.2 is much smaller than qt 2.x.

      Who knows which one would have been used today; Qt/embedded is smaller than GTK 2.x is.

    81. Re:Why the licensing argument is bogus by dublin · · Score: 1

      You're missing the point if you think the FSF cares at all about promoting the GPL. You see, the GPL is evil in the eyes of the FSF here because it's working in favor of what is the greatest of all evils in the FSF's twisted worldview: if KDE were included, a COMPANY might actually MAKE MONEY on software.

      In the FSF's eyes, this is intolerable - whether that position is logically consistent, or even consistent with their positions last week is irrelevant - the only thing that matters, indeed the only thing that drives the FSF mentality is a deep-seated hatred and bigoted intolerance of commerce in software.

      --
      "The future's good and the present is nothing to sneeze at." - Roblimo's last ./ post
    82. Re:Why the licensing argument is bogus by innocent_white_lamb · · Score: 1

      OK, then please get a list of companies like this which use GTK . Why that during all these discussion nobody has come up with such a list ?

      Probably because a centralized list of GTK "customers" doesn't exist, precisely because it is not necessary for developers to obtain a license and get on such a list.

      --
      If you're a zombie and you know it, bite your friend!
    83. Re:Why the licensing argument is bogus by JimMcCusker · · Score: 1

      Xerox, that's who. They just don't bother to tell anyone that they do.

    84. Re:Why the licensing argument is bogus by TrentC · · Score: 1

      [Note that this does not include most "enterprise" software development, which is typically for internal use only. In this case, they can simply use the Free Edition of Qt. As long as they never distribute the code, they don't have to abide by the GPL.]

      TrollTech doesn't believe so, according to TrollTech's own FAQ.

      Note that last sentence: "Consequently we recommend using commercial licenses for all internal software development."

      Jay (=

    85. Re:Why the licensing argument is bogus by cmbofh · · Score: 0

      > the vast majority of code is in the backend

      What does that have to do with anything?
      We're comparing GUI toolkits w.r.t. the amount of code the *user of the toolkit*
      (== the app developer) has to maintain.
      At least that's what the grandfather of my first post was talking about.

      The page I had replied to was
      a) Written by a zealot
      b) Quoting out of context
      c) Making (IMHO) wrong assertions without the slightest hint of data to back that up.

      You think that's ok?

      Talking about zealots: I got to know George Staikos as a very competent developer and I appreciate his opinion. But you may believe what you want.

    86. Re:Why the licensing argument is bogus by Anonymous Coward · · Score: 0

      What does that have to do with anything?

      The. Vast. Majority. Of. Code. In. Most. Apps. Has. Fuck. All. To. Do. With. Interface. In fact, in an ideal situation, most of it would be autogenerated.

      We're comparing GUI toolkits w.r.t. the amount of code the *user of the toolkit* (== the app developer) has to maintain.

      No you, and zealot-boy George Staikos, are not!

      You are comparing how much code it takes to write an app in one language compared to another -- you can write GNOME/GTK apps in virtually any language if you like, and as another post in this thread says, you can write very concise GTK apps in Python if you prefer. The fact that his isn't obvious to you, or Georgey-boy, makes it clear that neither of you have a fucking clue, and should probably keep your doltish fanaticism to youselves... or at least stick to preaching to ignorant KDE zealots who'll believe any old shite.

  17. My $0.02 by anaphora · · Score: 1

    And most important: non-programmer users don't care what GUI toolkit their application is built upon. The GUI issue is a developer, not user, discussion.

    *raises hand* I'm a user, and I care what GUI toolkit my application is built on. I prefer KDE. It looks more appealing to me. It seems to operate better on my system. I like the included programs packaged that can be used only on KDE. However, I don't care which GUI these guys choose, because I won't be using UserLinux anyway.

    1. Re:My $0.02 by Anonymous Coward · · Score: 0

      You don't know what a GUI toolkit is do you? KDE is not a GUI toolkit.

      The GUI toolkits in question are Qt and GTK+, and both have about the same flexibility of look and feel at this point so one doesn't look fundamentally better than the other.

      GNOME and KDE, which are desktop environments are a different story.

    2. Re:My $0.02 by Anonymous Coward · · Score: 0

      KDE provides APIs; there are actual KDE apps, not just raw QT apps.
      The gui toolkit question does indeed include KDE.
      KDE is also a desktop environment, as you stated.
      Partial information can be misleading.

  18. Any Lua binding for GTK? by Anonymous Coward · · Score: 0

    The future of building interfaces for applications is with interpreted languages - not statically typed verbose languages like C, C++ and Java. It's far easier to prototype a GUI in an interpreted language in a 1/3 the lines of code and the speed hit is not significant.

    So, is there a Lua binding for GTK?

    1. Re:Any Lua binding for GTK? by vidarh · · Score: 1
      There has been for a couple of years, along with Guile, Python, Javascript, Ch (interpreted C/C++), Perl, Pike, PHP, Ruby, Scheme, S-Lang, Smalltalk and TCL, to mention a few typically interpreted languages with complete or partial bindings (a lot of compiled languages are obviously supported as well, including C/C++, Objective-C, C#, Java, Haskell, Erlang, Eiffel etc.. For some of these languages there are even several alternative bindings.

      I've no idea about the quality of the various bindings, though. The official ones are Ada, C, C++ and Python, the rest are various third party efforts.

      I'm sure there are more languages as well.

    2. Re:Any Lua binding for GTK? by Anonymous Coward · · Score: 0

      But no Lua binding for GTK, it would seem.

    3. Re:Any Lua binding for GTK? by alext · · Score: 1
      Good point.

      Unfortunately you're in the wrong forum if you want to help determine actual requirements and priorities.

      This audience will still be arguing about C / C++ GUI systems when the rest of the world has moved on (to Java, Dotnet and their successors). I don't pretend to understand why this is, but after three years of putting the case for VMs as a fundamental part of Linux, I've discovered that responses to debates here in /. can be categorized roughly as follows:
      • 50% join in thinking that the issue is about language and syntax
      • 45% profess no interest on the grounds that C/C++ can do everything
      • 5% of respondees "get it" and recognise that this is a problem to be addressed but have widely divergent views on the way forward
      Maybe try the Parrot, DotGNU or Kaffe mailing lists?
  19. Well by Anonymous Coward · · Score: 0

    BP has stated explicitly that the only reason for choosing GNOME over KDE is the fact that GNOME is LGPL and therefore more friendly to proprietary software developers.

    My suggestion is to make KDE the default GUI due to its technically superior API, toolkit, and framework, but include the GTK+ libraries for proprietary developers if they want - we can even hack GTK+ to assume KDE's widget styles so it looks consistent.

  20. Window by grub · · Score: 1, Offtopic


    I'll be the sole vote for WindowMaker. Small, fast, compatible with KDE & Gnome etc..

    --
    Trolling is a art,
    1. Re:Window by Anonymous Coward · · Score: 0

      I'm adding you to my friends just for that comment.

      Non-bloat that works.

    2. Re:Window by jbplou · · Score: 1

      WindowsMaker is a very good windows manager, very fast as well. But I think it doesn't really matter, because UserLinux is pointless. Between RedHat, Mandrake, and SuSe what choice does this offer taht the others do not?

  21. Re: why gnome over kde? by J.+J.+Ramsey · · Score: 2, Informative
    "what are the reasons for choosing gnome instead of KDE?"

    Sigh. It's all here: On the GUI Selection in UserLinux.

  22. Re: why gnome over kde? by DAldredge · · Score: 3, Insightful

    One reason may be the 1,200 USD per developer to develope closed source apps for KDE.

    Gnome doesn't have such a charge.

  23. Anti Competitive? by Moth7 · · Score: 2, Interesting

    So it's anti-competitive to prefer one option for doing the job that you want done? Was I anti-competitive for un-selecting the KDE checkbox when I did my minimalist install? As I see it, this is a prime example of competition that they can thrive on - they both have to prove their case and one gets included - if thats not competition then I don't see what is.

    1. Re:Anti Competitive? by SkArcher · · Score: 1

      Did you possibly fail english in school?

      By any reasonable measure of the term competition is served by actually having a competitor.

      The non inclusion of KDE as an available choice means that GNOME has no competition in the UserLinux package. You unselected the KDE checkbox when doing your install by choice. This decision unselects the KDE checkbox for all who would use UserLinux, and does not give the option to recheck.

      This isn't about your personal choice, it is about you _having_ a personal choice, regardless of what it actually is.

      --

      An infinite number of monkeys will eventually come up with the complete works of /.
    2. Re:Anti Competitive? by Moth7 · · Score: 1, Insightful

      No, I didn't fail English at school, I haven't taken it yet, and am predicted an A actually. But whether or not I failed English at school and am still there or not is irrelevant. You are phrasing this like if Gnome is included in UserLinux, KDE won't exist anymore. KDE isn't the OS - just the face of it. There are still a multitude of other distros out there. The whole discussion point here is about which one is going to be used in a certain pre-packaged solution. It is perfectly acceptable for one or the other to get the job on this distro since they are finding one for a specific purpose. It's all apples and oranges. I don't suppose it would be anti-competitive if a rally team chose a Mclaren over a Benz would it?

    3. Re:Anti Competitive? by Anonymous Coward · · Score: 0

      Did you possibly fail logic in college?

      UserLinux not choosing to incorporate KDE doesn't mean that KDE is no longer a competitor of GNOME, it just means that in this case a decision about how to best use limited resources was needed. Bruce held a little competition in his mind and GNOME won.

      Now if you are going to provide UserLinux with unlimited funding, manpower, and time, I doubt Bruce would be so quick to make a judgement call of this nature. But I'm guessing that you are either unwilling or unable to do so. In which case someone needs to decide whether to duplicate a lot of efforts within the UserLinux project or whether to use those same efforts to move the entire project forward in a more meaningful fashion.

      Note to all whiners: don't like it? So what? Last time I checked, the source code for every last byte of a working GNU/Linux system was available for you to use in any way you see fit (abiding by the license of course). If you think you can do better, please feel free to go right ahead. There are probably 100 different distros out there, and right now this one doesn't even have an install disk (that I'm aware of). So who cares? Really.

    4. Re:Anti Competitive? by vidarh · · Score: 1
      Last I heard people weren't being forced to use UserLinux. KDE is available, for free, to anyone who care to install it. So a Linux distro chose not to include multiple versions of everything, big deal. If you have a problem with it, make your own alternative (based on UserLinux if you so choose) distro with KDE only and people will have even more choice.

      I'd love a distro that only provide a trimmed down set of apps, as it would save me the hassle of going through the guesswork of what I should remove or add to get a usable install, and let me focus on installing just whichever of the apps I commonly use were missing.

      Obviously, with the number of apps available for Linux, you can assemble a usable, consistent desktop in a large number of ways, and I'm sure there's more than enough space for multiple distro's trying to do it right. I for one would stear clear of any KDE only ones, just as expect KDE fans to stear clear of Gnome only distros, or take the trouble of packaging and installing KDE on it.

    5. Re:Anti Competitive? by otprof · · Score: 1
      By any reasonable measure of the term competition is served by actually having a competitor.

      True.

      The non inclusion of KDE as an available choice means that GNOME has no competition in the UserLinux package.

      This is technically true, but misses the point. In the world of OSS, there is a hefty amount of competition. UserLinux is supposed to be a subset of that larger world of software, targetted to a specific audience. Companies have a huge range of choices for which software solutions they will implement (thus, competition). By choosing UserLinux they would have indicated that this particular subset of packages, so configured, are the best fit for their IT structure.

      So, is anyone being slighted, or locked out of the competition? No. If companies decide that KDE is essential for their desktops and workstations, they will not implement UserLinux. RedHat or somebody else will benefit, or maybe UserLinux will reconsider and switch to KDE. Capitalism and free markets at work.

      You unselected the KDE checkbox when doing your install by choice. This decision unselects the KDE checkbox for all who would use UserLinux, and does not give the option to recheck.

      By choosing UserLinux, knowing its benefits and liabilities, they have made a choice. They have already "checked the box" for which GUI they want.

      This isn't about your personal choice, it is about you _having_ a personal choice, regardless of what it actually is.

      They do have a choice. They can choose UserLinux or not. Plus, if they decide after they implement UserLinux that they would rather have KDE (for instance, if the KDE group fulfills their list of objectives in their proposal), then they can easily add it. There is no vendor lock-in, and no restriction of freedom.

      Your arguments seem to me to reflect the current MS-dominated, proprietary software world. When we choose to install XP, we make an implicit agreement to work within the bounds and requirements of XP. MS has shown increasing amounts of control over the total desktop experience, since it supports their business model.

      UserLinux, and Perens, have no desire for this level of control. The goal is not to achieve dominance on the desktop in order to lock other vendors out. The goal is to set the desktop free, and their strategy regarding GUI is their best effort to make that possible. They might be wrong, and they may need to change their mind later on, but noone should accuse them of trying to take away choice.

      Bryan

    6. Re:Anti Competitive? by TKinias · · Score: 2, Insightful

      scripsit SkArcher:

      This decision unselects the KDE checkbox for all who would use UserLinux, and does not give the option to recheck.

      Not really. apt-get install kde will `recheck' it nicely, regardless of whether it's included on the installation media or supported by UL. That's why basing UL on Debian is so important.

      --
      In principio creauit Linus Linucem.
    7. Re:Anti Competitive? by TrekCycling · · Score: 1

      More to the point, what about all those distros out there (Xandros, Lycoris, Lyndows) that use KDE only. Often a customized version of KDE. KDE is getting used. You have your options KDE whiners. I don't understand why it's okay for some distros to choose to go primarily with KDE, but not for others to go primarily with Gnome. Grow up.

  24. Why argue? by fiskbil · · Score: 3, Insightful

    Why do people always have to argue that you should use this or that? The beauty of it all is that you can choose, if you do not like a distribution that ships with only Gnome then don't use it. If it's based on debian you might just as well install debian and KDE (if that's what you like) or grab a source-dpkg or a dpkg and install KDE on UserLinux afterwards. I realize that many see the need for a common environment with less choice. Mostly to make it easier to move from some other OS to GNU/Linux. But those who want KDE in UserLinux are probably competent enough to get it on their own or use another distribution, they probably won't have a problem choosing between Gnome and KDE. :) Arguing can be interesting and sometimes good, but this just seems like a pointless discussion to me.

  25. Or... Because it will be Debian Based... by HighOrbit · · Score: 2, Insightful

    apt-get install kde.

    For those users stuck inside the default gui and without knowledge of the command line (the real target audience of "UserLinux"), I am sure there will be a front-end installer to add new packages. Just include alternate guis as optional packages to be added at the users' descretion. Why stop at KDE? You could include any number add-in optional packages that are not "default". Anyway..., multiple packages that all do the same thing (like guis) will simply increase the complexity, bloat, and confusion for the target audience. Select one good one, and they can add others if they so desire.

    This whole debate sounds to me like what the BSDers call "bikeshedding". Arguing ad nauseam over minor details like colors because the deep-down architectural stuff is beyond intelligent discussion for most folks.

    1. Re:Or... Because it will be Debian Based... by TKinias · · Score: 1

      scripsit HighOrbit:

      This whole debate sounds to me like what the BSDers call "bikeshedding". Arguing ad nauseam over minor details like colors because the deep-down architectural stuff is beyond intelligent discussion for most folks.

      You've piqued my curiosity. What's the connection between a bicycle shed and this use? Maybe I'm just being braindead, but it's not obvious to me...

      --
      In principio creauit Linus Linucem.
    2. Re:Or... Because it will be Debian Based... by HighOrbit · · Score: 1

      Here is a link on the usage of the term "bikeshedding" amonst the unix folk.

      http://www.unixguide.net/freebsd/faq/16.19.shtml

  26. Please stop and think a bit before you post... by Ploum · · Score: 3, Interesting

    Please ! Stop to feed the troll !
    The mailing list becomes really full of this old and crappy Troll...
    There's no place for two DE in UserLinux... So there's a choice. If KDE was choosen, all gnome's fans will stand up !

    I talk a lot about the Desktop and I continue to receive comments about that.

    Well ! everyone has is own choice.. We don't have to speak so long about it !
    Who is the winner of the Gnome/KDE war ? MS Windows of course ! Like .doc is the winner of the .sxw/.abw war !

    1. Re:Please stop and think a bit before you post... by Anonymous Coward · · Score: 0

      If KDE was choosen, all gnome's fans will stand up !

      What, both of them?</troll>

    2. Re:Please stop and think a bit before you post... by Ploum · · Score: 1

      Ok guy, you've got the point here :-) it's so classic, but always funny...

  27. Down but not out by arvindn · · Score: 2, Insightful
    Offtopic: Slashdot editors, could you please avoid posting links to linuxworld. The ads are highly intrusive and there's javascript on the page that autoreloads it every minute or so, presumably to serve newer ads.

    Back on topic. I have to say it is really sad to see KDE left out (and I say this as a long time gnome user). KDE is definitely the more mature and enterprise ready project. But then I can see Bruce's point of view. It doesn't make sense to support both, and Qt's licensing could easily put off commercial/proprietary developers.

    Had the KDE and GNOME teams not thumbed their noses at each other for so long, and actually worked on interoperability issues (remember all the bitching when Redhat released bluecurve), all this could have been avoided. I mean, in that case it wouldn't have been difficult to support both.

    Still, its very early in the game and there's miles to go, and both projects can compete if they work with a unified vision. Its encouraging to see that they're doing just that. The KDE proposal, for example, was big on integration (GTK, OO.o, mozilla).

    Also, nobody is stopping a KDE/debian enterprise collaboration, which seems to be on the cards. On the whole the commercial interest from the big vendors has helped greatly. So while the userlinux decision is definitely a sad thing, the future looks bright.

    Uhh.., looks like this is my 500th post! Excuse me while I go out and get a breath of fresh air :)

    1. Re:Down but not out by vidarh · · Score: 1

      The KDE and Gnome teams ARE working on interoperability issues, and have been for years. It's the users that are bitching and thumbing their noses at eachother.

  28. Re: why gnome over kde? by Anonymous Coward · · Score: 0

    Read more carfully then. It's because of licence issues.

  29. Good Post - Mod Parent Up by Anonymous Coward · · Score: 0

    Gnome is the BEST!

  30. Re:why ignore the obvious solution? KDE only! by Anonymous Coward · · Score: 2, Interesting

    No, the real question is: why do any of us give a rat's ass what GUI a vaporware Linux distro uses? Are we suddently experiencing a shortage of prepackaged binary distros or easy-to-build source-based distros? Personally, if it had only KDE I wouldn't touch it, except if it were Knoppix. And Knoppix is already Knoppix, so I don't need UserLinux to be Knoppix for me. I use one K-program in my daily life, KMail, and even that doesn't really excite me-- I'd switch but the momentum for doing so is just not quite there. So I think your assertion that KDE beats GNOME hands down is not a "fact", rather an "opinion".

    For my part, I think GNOME beats KDE by a long shot because it is based on C and not C++. The number of competetent C developers far outweighs the number of competent C++ developers. C is certainly more common on the rest of a Linux system. Finally, I am given to understand that in terms on internationalization support and various accessibility functions, GNOME is ahead of KDE (or was momentarily). I think there are a lot of factors that you may not have had to consider when choosing a GUI that someone attempting to make an "enterprise" distro would think of.

  31. I don't understand this... by Chordonblue · · Score: 3, Insightful

    If someone wants to recomplile their own version of UserLinux, can't they? Why not start a spinoff project - call it UserLinux - K Edition or whatever? This was done with Knoppix (Gnoppix).

    Seriously, what's the big dealio? It's all open source!

    --
    "...Well, there's egg and bacon; egg sausage and bacon; egg and spam; egg bacon and spam; egg bacon sausage and spam..."
    1. Re:I don't understand this... by peope · · Score: 1

      The thing with UserLinux is that all players want a standard base to work with.

      Standardisation, simplification and predictability.

      Starting multiple spinnoffs will probably go against the idea of the project in the first place.

      But sure. If one creates a spinoff-project and it becomes successful because of widespread adoption. Probably the ones on the original path will be happy about seeing a project, with the same goals as theirs, being successful.

      I dont think the guys behind UserLinux are trying to advocate for a specific desktop enviroment for its own cause.

      They have probably chosen the path they belive is most benificial to the goals of the project.

      I salute the guys behind UserLinux for their work and I am quite excited looking at the possibilites of this project.

    2. Re:I don't understand this... by Anonymous Coward · · Score: 0
    3. Re:I don't understand this... by Telex4 · · Score: 2, Insightful

      There are, broadly speaking, several general reasons why Perens' decision have been criticised:

      1) If you succeed, you will make GNOME A de-facto standard and do to KDE, XFCE etc. what Windows did to Netscape

      2) You won't succeed because cutting out KDE will castrate your system

      3) You are wrong; KDE is better

      Personally, I'm open to discussions around reason 1, and I quite agree with the 'KDE side' on reason 2.

      What isn't made very clear in Perens' article is that by removing KDE, you don't just remove an alternative desktop environment, you also remove all applications that use Qt & KDE. If you start to think about it, then, you are cutting out all of the KDE apps like Kontact, Kolab and Quanta that will really be a boon in the enterprise market, and that have no equivalents that aren't Qt/KDE. You'll also cut out the massive number of Qt-based commercial apps that already exist from companies like Adobe, Opera, Samsung and lots of others listed in this comment.

      In other words, cutting out Qt/KDE and simply not offering KDE as a desktop environment are different propositions. That is why Perens' proposal will castrate UserLinux.

      A much better solution is to have GNOME as the only desktop environment, include Qt/KDE libs and apps, and then work through freedesktop.org so that Qt/KDE and Gtk/GNOME apps seamlessly interoperate. Then you can have an office using GNOME, Kolab, Kontact, Epiphany, a GNOME equivalent of KIOSK and all the other best technologies without ever needing to know about the bits underneath. Then those who wish to use it as a development platform also needn't worry about maintaining both toolkits, since their software can make a choice and still interoperate with all of UserLinux without a problem.

    4. Re:I don't understand this... by twener · · Score: 1

      > You'll also cut out the massive number of Qt-based commercial apps that already exist from companies like Adobe, Opera, Samsung and lots of others listed in this comment.

      This is not entirely true, you will see the shipping start of big static Qt linked packages like Opera is available today as static version. Let's not talk about load times, memory usage, etc. ;-(

    5. Re:I don't understand this... by TrekCycling · · Score: 1

      Nevermind that as you just stated there are PLENTY of distros that only include or primarily feature KDE include Xandros, Lindows, Lycoris, etc. It's almost mind-boggling for the KDE-drones to whine about this when they have so many KDE exclusive distros AND they have primary billing on distros like SuSE and Mandrake. What the hell do you people want? Some of us like Gnome. And because of that some of us my CHOOSE Gnome. Live with it.

    6. Re:I don't understand this... by drinkypoo · · Score: 1

      The fact remains that in order to get Qt libs one has only to apply apt to the problem and one can then use all the Qt-based libraries one wants. UserLinux will be based on Debian. The idea behind not simply including Qt in the system from the beginning is to promote GTK-based software, not to prevent people from using Qt-based software.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    7. Re:I don't understand this... by Chordonblue · · Score: 1

      I never said KDE wasn't better - I'm not going there one way or the other. My point was that since all of this is open source, what the hell does it really matter?

      This is Bruce's pet project. There is absolutely nothing stopping anyone from using it as a base and providing KDE libs. Paraphrasing what someone else said here; make GNOME the desktop and provide the KDE libs for the apps through something like freedesktop.

      In fact, I'll bet that were an organization be willing to work with Bruce on a parallel fork - he'd be all for it.

      --
      "...Well, there's egg and bacon; egg sausage and bacon; egg and spam; egg bacon and spam; egg bacon sausage and spam..."
  32. Standards drive acceptance. by jasonbowen · · Score: 2, Insightful

    The Linux that gains acceptance will be wrapped around one way of doing things. This is how business works. The beautiful thing about this is that a major corpororate/development workstation distribution can rise that major software developers can target and business can point to as their distribution of choice due to it's uniformity. There will always be the ability to roll your own and as long as people like Mr Volkerding want to keep alternate distributions going we will have other choices too.

    1. Re:Standards drive acceptance. by Anonymous Coward · · Score: 0

      The beautiful thing about this is that a major corpororate/development workstation distribution can rise that major software developers can target and business can point to as their distribution of choice due to it's uniformity.

      This is precisely the point. Choice is great for users. It's great for developers. It's lousy for developers developing for users. It spreads their support and development burden on to a wide plain that has nothing to do with their application.

      With ULs potential committment to GNOME, and the Java Desktop, there are two potentially large "Enterprise" desktops that developers will want to support, and thankfully, they're both on the same page with regards to the GUI.

      Now those developers can focus on getting their applications working rather than fighting infrastructure.

  33. MOD UP by Anonymous Coward · · Score: 0

    He raises some good points about Mr. Perens.

  34. This is rediculous by Anonymous Coward · · Score: 0

    WHen businesses make apps .. they usually prefer one api to program against. The commercial license for Qt stinks. You have to pay. That raises the bar for entry. Get over it. Think abou this the next time your boss complains about how much VS.NET costs or lays off another one of your co-workers because of lack of cash. Using Gnome is a good business move. This isn't about choice, this is about what the secretary is going to use, etc. Just let Bruce do what he wants .. if you dont like it .. start your own project.

    1. Re:This is rediculous by Anonymous Coward · · Score: 0

      from what i read of the license for mysql, this is the same reasoning. mysql also seems to charge for certain types of commercial apps

    2. Re:This is rediculous by truth_revealed · · Score: 1

      First of all, it's spelled "ridiculous". Secondly, what's the problem with paying for high quality software that saves you a lot of time and money in terms of productivity? I'm afraid that many companies are starting to equate free software with the notion that programmers are a "dime a dozen" because their work has no monetary value. Do you really think that the money saved by Linux really goes towards hiring new programmers? Ha! It goes to executives in the form of self-congratulatory bonuses for keeping costs low.

    3. Re:This is rediculous by ultrabot · · Score: 1

      Secondly, what's the problem with paying for high quality software that saves you a lot of time and money in terms of productivity?

      Stating the obvious: because it's cheaper?

      For example, some poor tosser in eastern Muktananda earns $300 a month, and decides to implement a closed source application to run on UserLinux. You expect him to sell his house and shell out for Trolltech?

      --
      Save your wrists today - switch to Dvorak
  35. MOD UP by Anonymous Coward · · Score: 0

    KDE was there first. If you remember, GNOME came later and the only strong point about it was that it's the "GNU" choice. So for every good project out there, make a GNU-equivelent and get all the fame. Unfair. And moreover, i think gnome is too overbloated.

  36. Re:What's the big deal by ultrabot · · Score: 5, Insightful

    if you really disagree with their choice on which GUI to include, make your own distribution and include just KDE with it.

    What's better, you can just apt-get kde on UserLinux.

    Gnome will be the default, supported option. It's sensible to pick only one to "officially support", and let the hackers use the other to their heart's content.

    Gnome is the better "supported" option because it doesn't require royalties for closed source development. This matters in countries where you can buy 3 developer months for single license of Qt (and for 3 developers, you need 3 licenses).

    --
    Save your wrists today - switch to Dvorak
  37. Re: why gnome over kde? by Anonymous Coward · · Score: 0

    Simply because Qt is GPL and Gtk is LGPL. But in both cases, they are Free. Neither the kernel allows you to make a closed-source derivative kernel. So what ? Does it make Linux non Free ?

  38. a little thinking is required by bstadil · · Score: 1
    The beauty of it all is that you can choose

    If you bothered to read the context of the discussion this is considered a negative in this case.

    The stock FOOS arguments does not allways play even in Slashdot, sometime a little thinking is required.

    --
    Help fight continental drift.
    1. Re:a little thinking is required by fiskbil · · Score: 1

      Sorry if my post wasn't clear on this. I meant that you can choose distribution, so there's no need to complain about distributions that limit choice.

      If the lack of KDE bugs you just choose another dist and be happy with it.

    2. Re:a little thinking is required by Anonymous Coward · · Score: 0

      Incorrect. A little thinking would reveal that one is always free to chose a distro with KDE support, such as KNOPPIX.

    3. Re:a little thinking is required by bstadil · · Score: 1
      Incorrect. A little thinking would reveal that one is always free to chose a distro with KDE support, such as KNOPPIX.

      I know I am responding to an AC so a bit pointless, but the issue at hand is what to do with UserLinux, so mentioning another distributions merits does not make sense for this debate.

      Your point is akin to responding to a debate over whether to include Wine in UserLinux with You can always use Windows XP Yes we know this, but does that mean we should include Wine or not?

      --
      Help fight continental drift.
  39. For crying out loud, people. by mcc · · Score: 4, Insightful

    Bruce Perens is making a GNOME-only linux distro. There's no reason for you to try to stop him. It isn't like there aren't 9000 other distros to choose from. Heck, it isn't even like there aren't ten to thirty other linux standardization movements similar to what Perens is doing.

    Perens is convinced that in order to do what he wants this distro to do, he needs to choose one desktop environment and focus to it. He's also convinced that GNOME was the right choice for this. You know what? If he's wrong, all that will happen is that his distro will fail. Life will go on, and only Bruce Perens will have lost any time from it. In the meantime, if you like, you can go and make a KDE-only linux distro of your own, and it will succeed or fail or whatever.

    I think Perens has an interesting little experiment going on here. If he's wrong, he's wrong, and if he's right, you know what? Once he has something good, you can take what he did, fork it, and add/insert KDE. Huzzah. In the meantime, who cares?

    1. Re:For crying out loud, people. by demachina · · Score: 1

      I think you are failing to see the forest for the tress. For Linux to be REALLY successful on the desktop there needs to be one distro, or a very small number of distro's, which have critical mass in terms of development, testing, quality assurance, applications and support.

      Every time a new splinter group is created the main thing they achieve is massive duplication of effort, doing builds, setting up net infrastructure, testing builds, developing the 150th new GUI installer, keeping on top of security updates and most importantly testing to insure that it works well.

      The reason the Linux kernel is so successful is that there is more or less just one, granted with some variants, but everyone focuses on one kernel and it gets a lot of good testing and there isn't a lot of duplicated effort.

      So far it appears Bruce is lacking the diplomatic skill and vision to pull together competeing interests to create a critical mass distro, which is what everyone was hoping for in the wake of Red Hat's misguided demise. UserLinux hasn't even started yet and Bruce has already created a massive schism that will drive off half his developer and user base. Why, well we don't know why. There is absolutely no reason KDE couldn't be maintained as an option like just about every other distribution around. By having it as an option you pick up a whole lot of developers and users to support it. By shunning it, they leave and you instantly destroy any shot you had at critical mass. By telling KDE developers and users, "big deal, roll your own" your just creating another splinter and another massive duplication of effort.

      Its about time this community grew up and realizes that 9000 distro's IS NOT A GOOD THING. Just because you CAN do 9000 distro's doesn't mean you SHOULD do 9000 distro's. It does give 9000 egos an opportunity to be a distro boss but thats about all it accomplishes.

      As for the GTK versus Qt thing I would echo other comments that any company that is developing commercial GUI software is likely to pick Qt. Fact is GTK works but it is a complete mess of a programming API. If you are investing a lot of money in developing serious GUI software, well designed, C++ offers so many compelling advantages, developers will pay for the commercial license because its cheaper in the long run to start on top of a solid toolkit.. Your programmers time is the expensive thing. A Qt license is cheap by comparison. C is great for kernels but it isn't a rational choice for developing complex GUI's.

      About the only group the Qt license punishes is developers attempting to develop proprietary software on a shoestring and I dont imagine they are the highest priority group. The bulk of the software that matters is either open source or serious commerical software both of which work just fine with the Qt license, as is.

      --
      @de_machina
    2. Re:For crying out loud, people. by Elektroschock · · Score: 1

      Well, he seems to be not very wise to chose a desktop environment that is not ready for the desktop yet. Who shall use Gnome? While KDe based distributions entered the desktop market, RedHat with Gnome withdrew.

    3. Re:For crying out loud, people. by Anonymous Coward · · Score: 0

      Disagreed.
      Having a large number of distributions can be useful, for specialisation. Want a router on a floppy? It's doable. Want KDE but no harddrive? Try thin clients of some sort, or knoppix. Etc...
      That said, there are far too many redhat spinoffs; most will fade into obscurity; some will have enough interest to survive. While they can, great.
      The diversity of distributions is one thing that has allowed linux to grow as quickly as it has.
      As more parts get standardised, hopefully maintaining a small distribution will become easier; as distributions mature, there will likely be less that are popular for any given task.
      Customisation will always be important; being able to share customizations shouldn't be taken lightly, and may actually avoid some duplicated effort.

    4. Re:For crying out loud, people. by Anonymous Coward · · Score: 0

      Bogus argument, because other than Routers, there really are no specialized Linux distros.

      99% of the 9000 Linux Distros are exactly the same -- they run Apache, Gnome/KDE, and provide some system tools and an update mechanism. The only added value is packaging stuff like porting to other platforms or CD-ROM boot.

      All-in-all, the Linux distro market has very little specialization and a whole lot of duplicate effort and vendor-proprietary stuff.

    5. Re:For crying out loud, people. by rking · · Score: 1

      So if I've got this right; you're not planning on using UserLinux yourself, you don't think many other people will use it and yet you think it's an important enough issues to have made 15 posts about already? WHY?

    6. Re:For crying out loud, people. by Anonymous Coward · · Score: 0

      Ever seen knoppix? morphix? smoothwall? the linguistic live-cd based on morphix recently mentioned on /.? the morphix games-cd? Peanut linux?
      There are a -lot- of specialty distributions. It's easy to overlook them in the waves of varients on redhat (and to a lesser extent debian), but they are out there.
      Proprietary extensions tend not to catch on; there's Suse's yast, and to an extend Xandros, but it tends to be somewhat marginalizing.
      Porting to other platforms is also pretty crucial; that said, you might want to run NetBSD instead of linux for that.

    7. Re:For crying out loud, people. by firewrought · · Score: 1
      Once he has something good, you can take what he did, fork it, and add/insert KDE. Huzzah. In the meantime, who cares?

      Your post is convincingly written, yet deceptive. Yes, I can "take it and fork it", but if I'm a KDE-fan (and I am), I miss out on all the software that was written to target Gnome instead of KDE (especially stuff like taskbar extensions and themes that must run in their native desktop environment).

      The fact is, this is a substantial loss for people who prefer KDE (assuming that UserLinux accomplishes its goals). It's not trivial as you imply.

      Note: even though I exclusively use KDE, I support Bruce's decision to standardize on one desktop environment. It will hurt KDE, but it will probably help Linux.

      --
      -1, Too Many Layers Of Abstraction
    8. Re:For crying out loud, people. by luisdom · · Score: 1

      If he's wrong, all that will happen is that his distro will fail.
      No, what will happen is that we'll have yet another "unifying" distro that will balcanize again the linux market, which goes in the opposite direction that BP wants.

  40. Hey! by MikeXpop · · Score: 1

    I'm an insensitive clod, you insensitive clod!

    --
    Etiquette is etiquette. He kills his mother but he can't wear grey trousers.
  41. Linux is all about choice... by Murmer · · Score: 2, Interesting

    ...until somebody makes a choice you disagree with, apparently.

    We're all aware that the whole point of this "free software" exercise is that people are free to do whatever they want with it as long as they share, right? Even if other people think it's a bad decision?

    --
    Mike Hoye
  42. No kidding by ultrabot · · Score: 2, Funny

    I sense another Holy War incoming over this.

    So you are saying that a holy war between Gnome and KDE will be coming? Proponents of various desktops trolling and flaming each other on Slashdot?

    We are truly living interesting times.

    --
    Save your wrists today - switch to Dvorak
  43. C bindings for GTK+. Not for QT by peope · · Score: 1

    One thing about GTK+ is that it is not restricted to C++ as QT. GTK+ has an object-oriented model but written in C with C++ bindings.

    This gives you more choices than QT when programming.

    Also, not being in contact with Trolltech (a company I am sure is very good), I assume the advancement of the QT library is in the hands of this company. With little input from other developers.

    It is not only the license that has effect of how free your code is. Not when you take on account that the main base will evolve.

    The kernel eg is free. But should you want to take it in a different direction, you will need to put in your own patches against the "clean" kernel. Others will not maintain it for you. But the lower parts are shared by multiple other applications that you dont have control of. So you dont have a free space where you can play freely. You need to make sure your version of a library or kernel, fits with most other apps using it.

    Personally I use KDE. Acctually primarily for that big nice clock defaulting in your right bottom corner =). And it has a kick-ass window-manager.

    Gnome is really pretty. But a little too bugged out at the moment. I see great potential there.

    UserLinux moving towards gnome will make me have a little tear in my eye, since I love my kde-desktop so much. But I think it can be a good choice in the long run.

    P.S. Everybody stating what kind of desktop-enviroment they prefer is not trying to be flaimbaiting. Given the nature of this article it is quite on topic giving pros and cons of our different enviroments.

    1. Re:C bindings for GTK+. Not for QT by ultrabot · · Score: 1

      One thing about GTK+ is that it is not restricted to C++ as QT.

      Neither is Qt. I've read that PyQt (Python bindings for Qt) is pretty nifty.

      --
      Save your wrists today - switch to Dvorak
    2. Re:C bindings for GTK+. Not for QT by Anonymous Coward · · Score: 0

      And your point is? What are those PyQT bindings written in, what do they need to be compiled with???

      Using C for a base library has a number of nice side effects, like: 1. Not needing a C++ compiler 2. Not having to worry about ABI changes because C is so simple and C++ is so complex and the namemangling is a mess (yes, this by itself is not a complete argument, but read below, my point is that the extra complexity to support C++ isn't worth it because C++ doesn't add much value). 3. In the case of GTK+, they wanted a library designed for scripting with a large number of runtime introspection features. C++ has RTTI, which is a joke, so the complexity of coding these features in C or C++ is a wash.

      Now those last two leads into the further discussion: A possible advantage or disadvantage of C is that it is fundamentally simpler than C++. Because of the object and type model of C++ things like name mangling and funky calling convention rules are required. These are not required in C. Of course, this comes at a price: You simply don't have namespaces, template specialization, and a predefined object model in C. However, if you are like me, you believe that all of these features in C++, although based on sound principles, have miserable implementations in C++, and C++ is a miserable monstrosity because of it. Object oriented programming might be good, but the C++ delivered framework isn't very flexible or complete, it only supports a very limited set of essential OO features, so you have to implement this stuff yourself anyway. Thats where you get things like QObject, CObject, the whole MS ATL COM mess, etc, etc.

      Qt is a good example of this. They wanted to write an object oriented library using a common OO technique: the subject-observer (yes it goes by other names) model. Unfortunately, C++ has no constructs for this, so they had to put together a complete signal/slot framework and a preprocessor to support it.
      The GTK people coded the same thing in C and it is quite complex, but still rather elegant because the code isn't contrived to sit on top of some broken object model. Even with this complexity, because the constructs boil down to simple structures, and C functions, one can interface to this from anything as long as they know the platform C calling convention, which is usually very simple and straightforward.

      I complain that C++ is too complex. When people reply that C++ is complex because it has more features than C, I respond that I understand that features come at a price, but that the features in C++ are so broken that it is not worth it. Common Lisp and Python are complex in their own right, but they have something that C++ lacks: elegance.

    3. Re:C bindings for GTK+. Not for QT by Hard_Code · · Score: 1

      Restricting widget toolkit to a particular language is not a critique of end user experience! It is a critique that something is not fulfilling your particular geek fetish! Give it up, who the fuck cares if it has a better end user experience (which I'd wager Qt does, as it is pretty well reknowned for its quality and used in many applications (even commercial, where "sales" matter)).

      --

      It's 10 PM. Do you know if you're un-American?
    4. Re:C bindings for GTK+. Not for QT by vurian · · Score: 1

      > This gives you more choices than QT when programming.

      No, it doesn't, because there are bindings for C, Python, Ruby, Java, Perl, Objective C. Choices enough, and that's without mentioning that coding to Qt in C++ is about as easy as using Java, if not easier. It all boils down to: you need less lines of code if you code in C++/Qt than if you use GTK/whatever -- and fewer lines of code means fewer bugs.

    5. Re:C bindings for GTK+. Not for QT by peope · · Score: 1

      Aside from your post being vulgar, offensive and making assumptions of what I tried to explain.

      QT is IMO a good toolkit. The biggest concern for me is that it more or less forces me to program in C++. A language I feel makes my day more complex than a C counterpart would do.

      It limits developers which can lead to less incentive for developers to embrace the platform.

      Personally I will embrace any choice between GTK+ and QT as they both are very competent libraries.

      For me it is a choice between a ferrari and a mercedes with an automatic gearbox. I wouldnt say no to the mercedes with the automatic gearbox (QT) although I would have preferred to play with the gears on the ferrari (GTK+).

      Me making binary distributions would cause problems because of the ABI incompatibilities. Increasing the need to compile it with static libs. It would increase the binary. (binary by convencience. sources available)

      Maybe it is some sort of geekish fetish from my side. But as a developer geekish fetishes might not be such a bad thing.

      Having guidelines for the design of a program or system that are not needed at the moment for the specific task, may soon enough be relevant when the program or system develops. Thinking refactoring.

      Also. I am not just looking at the current state of GTK+ or QT. A design-choice for a library to be C++ is in my opinion poor in terms of quality. But good in terms of development of the library.

      A library is to be used over and over and over. Putting more of an effort to make it geekishly fetishly perfected in design might be a good design choice.

      And please. Be civilized.

    6. Re:C bindings for GTK+. Not for QT by Hard_Code · · Score: 1

      "The biggest concern for me is that it more or less forces me to program in C++."

      We are not talking about programmers. We are talking about users. This USERLinux, specifically aimed at users with open and acknowledged concessions towards them.

      "Me making binary distributions would cause problems because of the ABI incompatibilities. Increasing the need to compile it with static libs. It would increase the binary. (binary by convencience. sources available)"

      These are not insurmountable technical problems. Again, that has nothing to do with user interface/environment aspect. I don't think the future of C++-based apps are at all threatened. Support is getting better and better for C++ and ABI in GCC, etc. If anything the industry as a whole is migrated more AWAY from C than towards it, so the future is definately going to look less C-ish (if not C++, something else, C#, etc.).

      --

      It's 10 PM. Do you know if you're un-American?
    7. Re:C bindings for GTK+. Not for QT by peope · · Score: 1

      Good tools for the developer means good applications and availability for these applications for the user.

      Choose good tools for the user. I agree with you. But good tools for users are often what is good for the developers since they create the applications.

    8. Re:C bindings for GTK+. Not for QT by fritmebufstek · · Score: 1

      Please do your homework. There are very certainly C bindings for Qt, I've heard someone say on IRC, he liked the C bindings for Qt a lot better than the native Gtk stuff.

    9. Re:C bindings for GTK+. Not for QT by Anonymous Coward · · Score: 0

      I've heard someone say on IRC, he liked the C bindings for Qt a lot better than the native Gtk stuff.

      Now there's a convincing argument.

  44. Re:What's the big deal by Anonymous Coward · · Score: 0

    And that is exactly what is happening. Well, we are not making our own distribution per se, and we're not repeating the mistake of begrudging the choice of some GNOME/GTK+ developers, but yes, we're moving on ;) If you read the position paper it is clear it wasn't meant as opposition at all. Just a solution to a problem.

    Many of us were/are quite excited by Bruce's main proposition: a cost-sharing non-profit to support enterprise grade linux. We were upset to see the project make such a wrong-headed decision, but that's ok since the captain is determined to make it and we aren't obliged to go with him.

  45. Choice Costs Money by reallocate · · Score: 4, Insightful

    Nuts. Choices like that cost money. If a business lets their employees choose either KDE or Gnome, then that business has to spend money supporting both KDE and Gnome. Why would a sensible business do that?

    Business users, regardless of the operating system and regardless of the "desktop environment", typically use a very few applications, day in and day out. The rest of their "desktop" sits there, unused.

    A smart business will lock down the desktops of their employees as much as possible, providing access to only the applications emloyees are authorized to use.

    All this adolescent whimpering about "choice" is silly and completely beside the point.

    --
    -- Slashdot: When Public Access TV Says "No"
    1. Re:Choice Costs Money by ankit · · Score: 1

      Exactly my sentiments. Choice is great for users who want to play with it. Not for a novice who wants to "learn" one thing. Not everyone has the time to explore GUI options under linux, and as you said, the cost to support multiple GUIs does not add to the productivity of the company.

      --
      Don't Panic
    2. Re:Choice Costs Money by 10Ghz · · Score: 1, Insightful
      Nuts. Choices like that cost money. If a business lets their employees choose either KDE or Gnome, then that business has to spend money supporting both KDE and Gnome. Why would a sensible business do that?


      Why not let the decision-makers at that company make that decision? The company could choose just one UI, but they could choose between KDE and GNOME. Now, Bruce Perens makes that choice for them.
      A smart business will lock down the desktops of their employees as much as possible, providing access to only the applications emloyees are authorized to use.


      Tools to do just that already exist in KDE, but they are not available for GNOME. So KDE has a clear advantage there.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    3. Re:Choice Costs Money by Anonymous Coward · · Score: 0

      Why not let the decision-makers at that company make that decision?

      Just who do you think IS going to be making it?

      The company could choose just one UI, but they could choose between KDE and GNOME. Now, Bruce Perens makes that choice for them.

      No he's offering them AN option. UserLinux is his product. The business can choose to use UserLinux, or not. How does this remove any choices?

    4. Re:Choice Costs Money by reallocate · · Score: 1

      >> Why not let the decision-makers at that company make that decision? The company could choose just one UI, but they could choose between KDE and GNOME. Now, Bruce Perens makes that choice for them.

      That's an option, but one that could easily add cost to the decision. Managements is unlikely to recognize either "KDE" or "Gnome". Acquiring the expertise to make a rational choice adds to the cost. From a business perspective, remember, almost all of any UI's capabilities will go unused. As program launchers -- their primary purpose -- KDE and Gnome are identical.

      The basic point is this: Beyond a certain threshold of functionality, choice of a UI is a secondary concern for businesses. Both KDE and Gnome are beyond that threshold. Perens is smart to pick just one.

      >> Tools to do just that already exist in KDE, but they are not available for GNOME. So KDE has a clear advantage there.

      Perhaps. Better yet, don't install or offer anything you don't want used. Environments I'm familiar with gave their employees Windows machines with Office. Nothing else. A limited set of other approved apps was available for installation after an employee's supervisor had approved the request. Automatic inventories ere periodically conducted, which flagged all unauthorized software.

      --
      -- Slashdot: When Public Access TV Says "No"
    5. Re:Choice Costs Money by Lumpy · · Score: 1

      Let's top that. Using KDE or Gnome is even worse for a company that want's it locked down.

      We use xfce on X terminals every app you need is configured as an icon on the toolbar and we run a second Desktop manager to give you desktop icons and a desktop folder to your ~/

      want to run Elf bowling? sorry, it's not there, you cant install it.

      and everything you do is backed up nightly, and when you are done for the day you simply power off your X terminal... no pesky logging off is needed.

      Corperate needs skilled IT workers that work smart.

      --
      Do not look at laser with remaining good eye.
    6. Re:Choice Costs Money by reallocate · · Score: 1

      Good for you. Too many folks must believe businesses think computers are something other than an expense. That's wrong. They're a tool, like any other tool. Once a tool meets your reuqirements, buying extra goodies is a waste of money. Imagine all those Pentium 4's sitting on desktops out there used by people reading email and writing reports. It's like buying Porsche's for the mailroom.

      Once, when working at a place where 99 percent of the computers were used for email and simple word processing, I suggested giving everyone 286 machines running DesqView, Word for DOS 5.5, Excel for DOS (although few actually knew how to construct a spreadsheet), and an email program. Of course, people looked at me like I was nuts.

      --
      -- Slashdot: When Public Access TV Says "No"
  46. Re: why gnome over kde? by Reziac · · Score: 5, Insightful

    [Reads article.. geez, the things I admit to doing around here...]

    Yep, I don't see any holy war material either, even tho I like KDE and detest Gnome. What Bruce says boils down to "All right, I'm tired of arguing about this, it's time to pick ONE (because this here project is partly about a focused direction instead of including everything plus a dozen kitchen sinks), and this here SDK is what I prefer for those there reasons. So we'll go with the desktop that matches this here SDK."

    Perfectly reasonable as a project decision, even if I personally disagree with the choice it led to.

    --
    ~REZ~ #43301. Who'd fake being me anyway?
  47. Did Bruce Perens have ideological motives by ihummel · · Score: 1

    I just wonder whether the reason that Bruce chose Gnome doesn't have something to do with Qt not being completely Free as in speech at first and the fact that Trolltech still puts out a non-free version for that other OS.

    1. Re:Did Bruce Perens have ideological motives by Anonymous Coward · · Score: 0

      It's not free as in beer for proprietary development.

      Isn't that good?

      The library is GPL'd. IOW, if you release your software under the GPL, you don't have to pay. If you release closed source, you have to pay.

      I still can't see how a leader of the free software movement can promote proprietary development.

      Derek

    2. Re:Did Bruce Perens have ideological motives by twistedcubic · · Score: 1

      I wouldn't call Bruce Perens' decision not to promote non-free software "ideological". I mean, that's closely related to what he does for a living.

    3. Re:Did Bruce Perens have ideological motives by ihummel · · Score: 1

      Actually, the X Windows System version of the library toolkit is dually released under the GPL and the QPL. The Windows version is proprietary only.

    4. Re:Did Bruce Perens have ideological motives by ihummel · · Score: 1

      Actually, I think it is a good thing. My point is that I suspect that Bruce Perens doesn't, and would rather use something that is totally Free. To recap, I suspect that Perens didn't make this decision on merits, but on licensing and maybe, just maybe, on history as well.

      While the merits of the two environments can be argued up the wazoo, and have been, KDE/Qt is more prevelent, more popular, and is the default on more distros than GNOME. Additionally, Qt is used in more commercial software releases on Linux and elsewhere than GTK/GNOME. In fact, I am using one of those products right now: Opera.

    5. Re:Did Bruce Perens have ideological motives by Anonymous Coward · · Score: 0

      There are strong motives (read "money") behind Gnome, which is the ugly base desktop for the prettier Ximian add-on (owned by Novell et al.).

      I wouldn't be surprised if they have been sweet talking Perens into this non-sense.

  48. So what's new? by Hatta · · Score: 1

    The fact that you linked to the original story doesn't make it not a dupe. The fact that linux world is now hosting the articles isn't news either. Please.

    --
    Give me Classic Slashdot or give me death!
  49. Here's the Trolltech Troll by Anonymous Coward · · Score: 5, Interesting

    The argument is this :

    SCO's bosses at Canopy controls Trolltech which controls Qt which controls KDE.

    (do an nslookup of www.trolltech.com and www.kde.org to verify that last bit of logic)

    The second contention that's a touchy subject is "Canopy controls Trolltech". Somebody is going to post a link to the trolltech site that says "only 8% of Trolltech is controlled by SCO/Canopy".

    Then what the hell is Ralph Yarro (Darl Macbride's boss) doing on the board directors of Trolltech?
    Link here for the skeptical.

    The issues is real simple. If Canopy doesn't control Trolltech and Trolltech support Linux, then why haven't they

    1) Come clean on exactly what their relationship is with Canopy ... and ...

    2) Voted Ralph Yarro of the board.

    Trolltech should come clean. What is their relationship with Canopy? Does canopy have contractual rights to sit on the board? Do they owe debt to Canopy? Does Canopy have warrants on Trolltech? The silence is deafing. Speak Trolltech, tell us the truth.

    The sad thing is QT is a good product. They could increase their respect and marketshare by telling the Canopy chumps to take a hike.

  50. Bah by Hard_Code · · Score: 1

    It has always seemed to me like KDE was a much more seamlessly integrated environment. From the start, Qt seemed like a superior toolkit which has accommodated significant feature bumps without drastic reorganization or need for rewriting apps. It's all fine and good to say "GNOME/GTK is now technically equivalent", but while Gnome has been catching up KDE is now floating out a whole flotilla of new features which are *specifically* targeted at the very enterprise audience that UserLinux says it is targeted at: kiosk mode, remote access like VNC, etc.

    KDE just seems like the more technically advanced and "end-user oriented" of the two.

    --

    It's 10 PM. Do you know if you're un-American?
    1. Re:Bah by a_hofmann · · Score: 1

      when you are speaking about gnome having catched up to kde, you should not forget the backend.

      while the original gtk+ core is c code, which gives good performance but makes developing bigger apps painful, the now really mature gtk-- library is a modern c++ toolkit. it does not depend on language extensions and preprocessors like moc, but rather uses modern c++ language features and programming techniques to fulfill the same requirements.

      that's why i think gnome is the better desktop from a programming point of view, and that just because of this will continue to develop faster than kde (as it did in the recent time).

    2. Re:Bah by Hard_Code · · Score: 1
      when you are speaking about gnome having catched up to kde, you should not forget the backend.

      while the original gtk+ core is c code, which gives good performance but makes developing bigger apps painful, the now really mature gtk-- library is a modern c++ toolkit. it does not depend on language extensions and preprocessors like moc, but rather uses modern c++ language features and programming techniques to fulfill the same requirements.

      that's why i think gnome is the better desktop from a programming point of view, and that just because of this will continue to develop faster than kde (as it did in the recent time).


      So which GTK is the real GTK? Is one an "old" deprecated version and one "new", or just different bindings to the same thing? Do the widgets act and look alike? Does the gtk-- have C backwards compatibility or does gtk+ have to be used? What sort of consistency guarantee is there accross apps then? It's interesting to hear that there is a C++ version, but I wonder how this is going to affect consistency. Is there a project-wide declaration to only build new stuff on gtk--? If not then I think there should be. There are enough toolkits to begin with, without having to worry about different versions for different languages, etc.

      I really anticipate seeing how gtk-- will match up against Qt, if it is really as mature and modern as you say. Should be interesting.
      --

      It's 10 PM. Do you know if you're un-American?
  51. Don't ask, don't tell, don't know. by Anonymous Coward · · Score: 0

    As already pointed out. Gnome is business friendly. While Trolltech can flick through their sales records and make a good estimate of how many QT commercial apps there are. The Gnome licensing means that a company can write a commercial Gnome app without telling anyone, anything.(kind of like the BSD's). Don't be surprised if you get a rude surprise (like Microsoft gets a rude surprise with stealth Linux)

    1. Re:Don't ask, don't tell, don't know. by Anonymous Coward · · Score: 0

      > The Gnome licensing means that a company can write a commercial Gnome app without telling anyone,anything.

      This "can" is a big one , because it has NEVER materialized to attract ISVs. On the other hand , QT has enjoyed a very big user base for proprietory applications.

  52. I want my 5 minutes back! by Qbertino · · Score: 0, Troll

    Errm, pardon me, but who in holy hell are these UserLinux people and who's this Bruce Perens guy?
    Do I have to know them?
    Am I wrong or have these people not yet managed to roll out even the faintest resemblence of a Linux distro which, if it were there, would be nothing but a sad and sorry rippoff of the Debian project. No?
    As far as I can see from here there's nothing but a bunch of blockheads on mailing lists, webforums and slashdot generating nothing but a big heap of pointless media hype. Heavens, give us a break on people trying to generate by the most pointless of OSS discussions, KDE vs. GNOME.
    I want my 5 minutes back.

    --
    We suffer more in our imagination than in reality. - Seneca
    1. Re:I want my 5 minutes back! by TrentC · · Score: 2, Insightful

      Errm, pardon me, but who in holy hell are these UserLinux people and who's this Bruce Perens guy?

      If you don't know that Bruce Perens is a former Debian Project Leader and the primary author for the Debian Social Contract and the Debian Free Software Guidelines (which was reworked into the OSI's Open Source Definition, a group he co-founded), or that UserLinux is his attempt to provide an DFSG-compliant reference distribution to high-priced Enterprise Linux solutions that can be developed and extended by Linux vendors, then why should I care who you are or why you felt the need to mindlessly babble on /. about a topic you admit you know nothing about?

      I'm a GNOME user, but to be honest, I'm not losing any sleep over UserLinux's decision to pick GNOME over KDE because I'm not the target market for the distribution (although the use of GNOME means I may be more likely to look at early builds and see if I can contribute); Bruce has his goals, they're clearly outlined on the UserLinux site, and if can't come to some kind of accomodation with that, you're welcome to not contribute to the project.

      Jay (=

    2. Re:I want my 5 minutes back! by Anonymous Coward · · Score: 0

      Yeah, the whole point of "User Linux" has been forgotten due to this KDE/Gnome framework.

      User Linux is an attempt to address the problem that Enterprise Linux distos from RedHat and SUSE are really fucking expensive -- more expensive than MS Windows in many cases. So, basically, its supposed to be a community-supported distro that has the same stability and support options as RedHat.

      However, more troubling than the desktop flamewars, is the idea that User Linux is going to be a fork off Debian. We'll see if they can even manage to wrangle Debian's ancient software and stalemate-oriented development products into a real, working distro that's anywhere near RedHat's quality. I kinda doubt it.

    3. Re:I want my 5 minutes back! by An+Onerous+Coward · · Score: 1

      Evidence: You don't know who ESR is.

      Evidence: You're surprised that Slashdot would draw its readers into a Gnome/KDE flame war.

      Conclusion: You, sir, must be new here.

      BTW, there's absolutely nothing wrong with ripping off the Debian project. Knoppix did it. SuSE did it. I think both Lycoris and Lindows did. As for ESR (Eric S. Raymond), he's been hailed as the great mainstreamer of Open Source, and derided as a glory hound and a libertarian gun-nut. It's up to you and Google to decide, but for better or for worse, he's something of a mainstay in the Linux world. So yes, you do have to know who he is.

      --

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

  53. One Word by Markus+Registrada · · Score: 1
    Whiners.

    Of greater moment is the choice of MySQL vs. PostgreSQL. Similar license issues pertain, and the differences in fundamental capability are much greater.

  54. i use... by Anonymous Coward · · Score: 0

    Perl/Tk. anybody else can do what they want :)

  55. Both are needed by salesgeek · · Score: 1

    Neither KDE nor Gnome is ready to be the only choice . Both are very very good compared to what we had four or five years ago, and both offer developers quite a bit. Unfortunately, some Linux apps are dependent on QT and others on Gnome, and ultimately, it's a showstopper when joe user wants to install software and discovers they can't (or it is difficult) because of dependencies on a library that is part of KDE or Gnome and they don't have it and cant get it because the IT dept won't let them.

    --
    -- $G
    1. Re:Both are needed by An+Onerous+Coward · · Score: 1

      As I understand it, KDE is able to run Gnome apps by calling the GTK libraries, while Gnome can call Qt libraries. So even if they don't install the KDE desktop, it might be possible for UserLinux to include enough libraries to get the apps working.

      Also, in a business environment, Joe User shouldn't be installing his own software anyways. So I would hardly call this a "showstopper."

      --

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

  56. my take on the situation by morgajel · · Score: 1

    ok, We gotta look at who this is targeted at-
    a) enterprise systems
    b) everyone else
    c) geek elite

    a) enterprise systems- ok, if we're going to look at business deployment, you gotta look at who will be using it- at the previous companies I worked for, there were 350 employees and about 20 tech-saavy ones(10 were IT related). The thing you gotta look at here is the other 330 employees probably have never heard of linux.

    /me puts on flame-proof armor.

    It has been my experience that completely clueless users prefer kde because it's more 'polished*' than gnome- it looks and feels like a cross between windows and macintosh. This makes the transition easier for people who don't want to dig to get something to work. This was the case with my wife and my younger brother.

    * by polished I mean comes with the most user-level tools. Some may call this bloat, I call it usability for the unwashed masses.

    b). everyone else- I'm curious what the actual breakdown of gnome/kde/box/other WM's actually is. From my limited experience, most people that I know use kde or fluxbox/blackbox. I can only think of two or three off the top of my head that use gnome. It would make sense to include the most popular. Obviously my own experience is probably not an accurate reflection of reality. I think slashdot should run a poll on this.

    c). Geek elite - This is sort of silly, but they usually are the ones making the decisions. They'll use what they want and we'll like it until someone branchese off a tree of their own. That would completely defeat the purpose of this project.

    The goal is to unite linux into one standardized distro to base things off of(IIRC). While I agree they need to watch out for bloating, there has to be a few exceptions. Otherwise this will just turn into another United Linux.

    and we don't want that.

    --
    Looking for Book Reviews? Check out Literary Escapism.
    1. Re:my take on the situation by RParr · · Score: 1

      I use/support both Gnome and KDE. I have, until recently, primarily supported/installed Red Hat. Red Hat defaulted to and better supported Gnome so we generally went with that.

      Over the last two years I have installed many systems which migrated both business and home users from Windows to Linux. Half stuck with the default Gnome on Red Hat; the other half got RH 7.3 with KDE or SuSE 9 with KDE. Some businesses had both classes or users. Most were running, pretty much, the same set of client sw (OpenOffice, Mozilla, file mgr, Gimp, ...) to perform similar tasks.

      Those that received KDE desktops are very happy campers. They have migrated from using Windows to using Linux with very little problems and very little training. They are tickled (for the most part) with their Linux systems.

      Those that received Gnome desktops are very UN-happy campers. Several find it so difficult and confusing they want their Windows systems back.

      I understand the licensing argument (I think). I was more in favor of Gnome licensing but have been somewhat swayed by argument that KDE's GPL (give back) or QT license (support further development) may be better, in the long run, for the Linux community than Gnome's LGPL (free without having to give back).

      I understand the desire to standardize on one desktop BUT feel a Gnome system, with no KDE support, does not really compete with the competition (Windows, OS-X, KDE, etc.). I appreciate the foundation may be better in some way, the app faster, etc. but if it does half of what I need a little faster or more elagantly it is still inadequate.

      BUT, for me, the bottom line is my KDE users have been migrated easily and relatively painlessly and my Gnome users want their Windows back.

  57. Re:What's the big deal by ankit · · Score: 5, Interesting

    Its just like you can simply download and install mozilla/firebird/opera/etc on any windows machine - internet explorer would only be the default. You dont have to use it.

    UserLinux is targeted at the enterprise community. It probably (and hopefuly) be used by non-geeky types who simply use what is installed on their computers. You can see KDE go the same way as netscape if UserLinux ever becomes popular.

    I am not sure what the right approach would be though. It makes sense for an OS to have a consistent "face" to a non-techie user. Though choice is great (and it is the reason why I use linux), it can be a hinderance for someone who is not inclined to try out 5 different window managers before she decides which one to use!!

    --
    Don't Panic
  58. "UserLinux" = misleading name by Florian · · Score: 4, Insightful
    The first thing UserLinux needs to fix is its own name. Given that it will not be end/home user distribution, but a business OS designed to compete with the expensive "enterprise" offerings of RedHat and SuSE, it should be better called "Free Enterprise Linux". (The term "free enterprise" would also communicate to corporate people what "free" in "free software" is about.)

    If UserLinux was an end user-oriented distribution, it surely had to pick KDE instead of Gnome, since KDE is the more integrated and stable GUI and is less messy in the architecture underneath (while Gnome/GTK has the lead in 3rd-party applications and, since recently, UI polish).

    But for a "Free Enterprise Linux", there must not be any hidden costs for enterprise software development. This demands that libraries and SDKs should, where possible, be LGPL- or BSD-licensed, and not GPLed with for-pay-exceptions (like in Qt and MySQL).

    Of course, the question remains if, due to its proprietary-friendly licensing and relatively conservative (=stable) design process, FreeBSD wouldn't be the better "Enterprise Linux" anyway. After all, the GPLed Linux kernel could be ditched in favor of a BSD kernel with almost the same arguments the UserLinux project now ditched the GPLed KDE libraries in favor of the LPGLed Gnome libraries.

    But since Linux is all the hype even where it doesn't make too much sense (like in PDAs, for which Minix would be much better suited), it's good that the "UserLinux" project attempts to prevent that commercial distributors do the same horrible mistakes with Linux and their "enterprise" distributions the proprietary Unix vendors made in the 1990s.

    -F

    --
    gopher://cramer.plaintext.cc http://cramer.plaintext.cc:70
    1. Re:"UserLinux" = misleading name by po8 · · Score: 1

      Of course, the question remains if, due to its proprietary-friendly licensing and relatively conservative (=stable) design process, FreeBSD wouldn't be the better "Enterprise Linux" anyway. After all, the GPLed Linux kernel could be ditched in favor of a BSD kernel with almost the same arguments the UserLinux project now ditched the GPLed KDE libraries in favor of the LPGLed Gnome libraries.

      I'd be running BSD on my home boxes quite happily, but for two things. First, much random PC hardware that I own has drivers only for Linux, and I'm not willing to do a bunch of device driver porting or throw working hardware away. Second, a bunch of the apps I run have Linux binaries, but not BSD binaries, available, and I'm not willing to do a bunch of application porting and compilation.

      Why is my story relevant? Because enterprises have the same issues I do, but maybe more so.

      I'm a big fan of the BSDs. After all, 2.9BSD was the first minicomputer OS I ever worked on/in. I think there are a number of niches where BSD is exactly the right thing. But I'm not convinced that general-purpose enterprise desktop appliances is one of them.

    2. Re:"UserLinux" = misleading name by mrroach · · Score: 1

      > The first thing UserLinux needs to fix is its own name

      They are. That name is only a placeholder.

      > If UserLinux was an end user-oriented
      > distribution, it surely had to pick KDE instead of
      > Gnome, since KDE is the more integrated and stable
      > GUI and is less messy in the architecture
      > underneath

      I'm curious why you say that. My initial instinct, since I have looked at both is to dismiss you outright, but to give the benefit of the doubt, what technical aspects make Gnome's architecture "messy"?

      > while Gnome/GTK has the lead in 3rd-party
      > applications and, since recently, UI polish

      Isn't that what users actually care about? It seems from your own argument that you should object more to them calling it DeveloperLinux, although even the basis for that claim is unsupported in your "argument"...

      -Mark

    3. Re:"UserLinux" = misleading name by Anonymous Coward · · Score: 0

      BSD has pretty good binary emulation for linux. Hardware support is also good, but as you said, imperfect, although the number of platforms is greater.

  59. Widowmaker by Krapangor · · Score: 1

    And easy to program, too !

    --
    Owner of a Mensa membership card.
  60. Simple choice! by lexcyber · · Score: 1
    --
    - To understand recursion, we must first understand recursion -
  61. explain to a non geek, svp by cinnamon+colbert · · Score: 2, Insightful

    why is "choice" good. I am serious here. For me, and my coworkers, all non geeks, having a single OS/office , eg windows 2000/XP and office 2000/xp is great - a guy emails me a complex doc, and it opens without problems, all of the support staff everywhere know this system, I have never run across an unsupported peripheral piece of hardware (dont flame me - i am a typical user and this is my experience). It is really not clear to me that I, personnally, gain anything by having choice. True, I gain "freedom" to have my desktop do something else, but I loose "freedom" of interaction with others, the freedom have most of the IT people able to help me, the freedom to have plug and play (true, ms is not 100% great, but I will wager it will always be better then a fragmetned open source movement). I guess "choice" of "freedom" from the evil MS empire is just not that important to me. I turn off my computer at the end of the day, go home, and don't worry about it. It is just not that big a deal. And as for the "ethical" issues, as long as there are starving children in the world, worrying about the gates monopoly is way way down on the list As for the cost, if you factor in what I am paid, and how we work, and the cost of support and all that, at least for my company (we have a high proportion of high paid engineeers and scientists) the cost differential (only the diff is important right ?) is just not that important.

    1. Re:explain to a non geek, svp by tempfile · · Score: 1

      The freedom of interaction is guaranteed by open standards. Proprietary systems destroy interoperability as soon as you choose an alternative piece of software. Microsoft works towards destroying interoperability deliberately. The lack of interoperability between different applications is entirely the fault of proprietary software in general and Microsoft in particular.

  62. Re: why gnome over kde? by twistedcubic · · Score: 1

    You could read the paper, or hear the real truth: many people find it hard to take seriously a desktop environment with a default girly pastel-colored look (Windows XP is an exception, for its ubiquity). People may want to push a more conservative-looking desktop towards businesses. Gnome is it. We wouldn't be having this conversation if KDE weren't so "Crayola" by default.

  63. Predictions of the failure of UserLinux by Anonymous Coward · · Score: 0

    KDE is a fine desktop environment but it does not make or break a distribution.

    That argument ignores the very distribution that UserLinux uses as its base which, unlike other popular GNOME-centric distributions, didn't even include/support KDE until QT was made GPL: Debian.

    And speaking of treating other DE's as second class citizens, Debian and Redhat did it with KDE for the longest time(some may argue that the latter still does) but complaining about it ignores the fact that KDE-centric distributions treat GNOME in the same manner(arguments can be made that some still do.)

    1. Re:Predictions of the failure of UserLinux by Anonymous Coward · · Score: 0

      Lack of QT apps breaks a distribution aimed at desktops.
      Not having kde as a desktop isn't a problem. Not including kde as a desktop environment is ok. Not including QT, much less kde-libs, is idiotic.

    2. Re:Predictions of the failure of UserLinux by Anonymous Coward · · Score: 0

      Wishful thinking. I have yet to come across a QT app that is necessary for desktop operation and doesn't have a non-QT counterpart.

  64. Most projects loose, that is capitilism by cinnamon+colbert · · Score: 1

    At least in my area of the market, lab equipment for scientist, a lot of stuff looses out in the market place - that is how markets work. Assuming software is a standard product, which behaves like refridgerators and pdas, one would expect most of the launched products to have a small market share. Of course, the loosers are bitter, but our current capitilist system really does not care about loosers - you are suppose to retrain yourself and move on

  65. Thriving on competition? by Sunnan · · Score: 1

    But darlings, we're competing amongst ourselves.
    Cooperation is the solution.
    It's kind of a bummer that Bruce went this route since I have a hunch that the projects would've merged within a couple of years.
    And they got to, I mean really.

    Using the same session managers, settling on a file manager, a configuration system, and so on.

    Both QT and GTK could still be available as options for developers, if they were made compatible.

    On competition.

    1. Re:Thriving on competition? by Anonymous Coward · · Score: 0

      It's kind of a bummer that Bruce went this route since I have a hunch that the projects would've merged within a couple of years.

      So what's changed? Are you suggesting that the choice of Gnome as the desktop for a single distribution that doesn't even exist yetis going to significantly aggect whether the two projects merge or not? Sorry but this whole thing has been blown insanely out of proportion.

    2. Re:Thriving on competition? by Sunnan · · Score: 1

      Yeah, I guess you're right.
      It's just that it sparked some flames again.

  66. Target audience by DarthSepulsive · · Score: 1

    The target audience for this distribution is businesses who want to roll out in-house software. They want 1 desktop, 1 toolkit and if possible no licensing costs. GNOME/GTK fits the bill.

    The only thing that worries me a bit is that by leaving out KDE/QT he's cutting himself off from all applications that exist for KDE/QT. This might be a bit short-sighted. Because if you can choose between a GNOME/GTK only distribution and one which has GNOME as it's default, but also provides the KDE/QT libraries to run KDE/QT apps, I'll choose the second. I can still develop my apps using the free GTK toolkit, while leaveraging the existing KDE/QT apps where they are better than existing GNOME/GTK applications.

    But in the end it is his distribution. He calls the shots. The KDE/QT people can go and fork his distribution adding in KDE/QT. It's Open Source after all.

    1. Re:Target audience by 10Ghz · · Score: 1
      The target audience for this distribution is businesses who want to roll out in-house software. They want 1 desktop, 1 toolkit and if possible no licensing costs. GNOME/GTK fits the bill.


      And you can write closed-source in-house apps with for free qith Qt just fine! GPL allows that! And most companies do NOT write software, they use software, yes, but they don't write software.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    2. Re:Target audience by TrentC · · Score: 1

      And you can write closed-source in-house apps with for free qith Qt just fine! GPL allows that!

      But the Qt Free Edition isn't available for any platform other than Unix/Linux; which means your GPL-licensed application has to use the non-GPL-licensed versions of Qt if you plan to port it to Mac OS X or Windows.

      And Trolltech would prefer you use their Qt Commercial Licensed version if you "[b]uild software that is not sold, but that advances the business goals of a commercial enterprise," regardless of the platform.

      Jay (=

    3. Re:Target audience by 10Ghz · · Score: 1
      But the Qt Free Edition isn't available for any platform other than Unix/Linux; which means your GPL-licensed application has to use the non-GPL-licensed versions of Qt if you plan to port it to Mac OS X or Windows.


      Well, you can't really use GNOME on Windows or Mac either. And to my knowledge, GTK+'s Windows-support isn't that good. No-one with a half a brain would use GTK+ to do Windows-developement! Can you name any Windows-app (besides GIMP) that uses GTK+? So your argument is pointless.

      It seems that developers rather develop for Windows with commercial Qt than free GTK+.

      And Trolltech would prefer....


      So? Of course they would like it if people bought their product. But they can't stop people using the GPL'ed version, assuming they agree with the license.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  67. Canopy has hooks into Trolltech by Lost+Penguin · · Score: 1

    Trolltech has been hornswaggeled into selling shares to Canopy. (SCO buddy)
    If Canopy seizes control (Hostile takover), KDE is gone.
    I can hear it now:
    "KDE contains our QT IP, we want all your computers to be Fed-x'ed to Lindon Utah or we sue everyone."

    --
    I am the unwilling control for my Origin.
    1. Re:Canopy has hooks into Trolltech by 10Ghz · · Score: 1

      Are there STILL morons spreading FUD about this??? Hey idiot, here are some fact for you:

      Canopy and SCO combined own about 5.7% of TT. They do NOT in any shape or form "control" the company.

      Those shares were sold to Caldera. Caldera used KDE and invested in TT. Caldera then turned to SCO, and SCO got those shares. There's not much TT could do about it.

      TT couldn't buy those shares back if SCO is unwilling to sell.

      SCO/Canopy COULD NOT take over TT. TT is a privately owned company, with TT-employees owning over 60% of the shares.

      If Qt ceases to be available under the GPL, it get re-licensed under the BSD-licence, as required by the Free Qt foundation.

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    2. Re:Canopy has hooks into Trolltech by Ralph+Yarro · · Score: 1

      On behalf of Trolltech, I can confirm that Canopy has NO control or influence over our company or the future of QT. Glad I could provide this reassurance.

      Director Ralphie.

      --

      The real Ralph Yarro posts as Anonymous Coward. Anyone else is an impostor.
  68. Re: why gnome over kde? by Anonymous Coward · · Score: 0

    There is no charge for Gnome apps which are closed source because the GPL won't allow you to distribute closed source Gnome applications to begin with. But I can distribute closed source applications with Qt if I pay for the license. Gnome does not allow that choice.

  69. Re:What's the big deal by Anonymous Coward · · Score: 0

    If you don't like the distribution, don't use it. Simple as that. Keeping the OS simple and maintainable as a laudable goal, and I would find it difficult to argue with them just because my personal choice GUI wasn't included (though neither Gnome or KDE are *my* personal choice :-)). The beauty of open source is that anyone can do this -- if you really disagree with their choice on which GUI to include, make your own distribution and include just KDE with it.

    This just goes to show the troubles that Linux will continue to face as it becomes more widely adopted. It's going to be impossible to keep the Open Source ideal of choice and expect wide spread adoption. Companies don't want to support multiple versions of Linux. Thus a single version is going to be what drives Linux in business. Then you have a single entity controlling Linux. So much for Open Source ideals.
  70. Oh, the irony by truth_revealed · · Score: 3, Interesting

    Bruce writes:
    It is possible for us to make our system entirely royalty-free for solution developers, both Free and proprietary. This dictates some software choices: GNOME and PostgreSQL rather than KDE and MySQL, simply because of the way those products license proprietary developers. This will support a large ecosystem of both Free and proprietary solution developers by lowering the financial barriers to entry all the way to zero.

    So, let me get this straight - he wants to discourage the use of GPL'd code in UserLinux in order to have businesses create proprietary applications that can not in turn be included into UserLinux because they will not be free?

    Sounds like an interesting one-sided ecosystem.

    If he took this commercial-friendly argument to its logical conclusion he would dump the GPL'd Linux from UserLinux in favour of BSD. But then it would not be much of a UserLinux, would it?

    1. Re:Oh, the irony by An+Onerous+Coward · · Score: 1

      Look at it from a business perspective. You want to create an application. Under Gnome/GTK, the choice is as follows: a) Make it GPL. b) Keep it proprietary. Under KDE/Qt, the choice is: a) Make it GPL. b) Pay a (pretty reasonable) license fee to Trolltech to make it proprietary.

      Now if--as some have argued--Qt is really superior to GTK, then some larger companies would probably rather have the second choice. But for many GPL-skittish companies, ESR seems to figure that the licensing costs will be a deal-breaker, and impede adoption of Linux overall.

      You claim that this reasoning implies that the distro should be BSD-based. I have absolutely no idea where you're coming from there. He's not trying to "discourage the use of GPL'ed code," merely keep potential users from being pushed into it.

      --

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

    2. Re:Oh, the irony by Anonymous Coward · · Score: 0

      He's not trying to "discourage the use of GPL'ed code," merely keep potential users from being pushed into it.

      Of course.

      He's not trying to "discourage the use of GPL'ed code," merely keep potential users from using it.

    3. Re:Oh, the irony by mrroach · · Score: 1

      There is no irony here, only pragmatism. Bruce has made it clear that he wants to leverage Debian's huge developer and (high-quality) package base. That is esential, because starting from scratch is just not logical. That makes linux/debian the practical solution.

      He also wants to make development for proprietary software as easy as possible. Two separate goals. It just so happens that those two goals lead to different licenses at either end. BFD.

      -Mark

    4. Re:Oh, the irony by TrentC · · Score: 1

      So, let me get this straight - he wants to discourage the use of GPL'd code in UserLinux in order to have businesses create proprietary applications that can not in turn be included into UserLinux because they will not be free?

      The proprietary applications he's talking about would never be distributed with UserLinux anyway; he's talking about in-house applications.

      Example: I used to be a supervisor at Fry's Electronics, where much of their software used in-house is developed in-house; two in particular are "Store Master", where supervisors can track stock flow, place reorders or special orders, etc.; and a similar program called "Merchant Master" that I've never seen it firsthand myself, but I assume that buyers use to manage relationships with vendors.

      Given that TrollTech's page for Qt Commerical Licensing says that you should use Qt Commercial Licensing if you "[b]uild software that is not sold, but that advances the business goals of a commercial enterprise", that means Fry's would have to pay a minimum of $1500 per developer per year to port Store Master and Merchant Master to using Qt. And that's just for a single-platform license; if they wanted to maintain a Windows version as they convert their desktops to Linux(1), that jumps to $2300 per developer per year. (If they were to go with the Enterprise Edition licensing, which inlcudes platform-independant extensions for database and network access, those prices jump to $2300 and $3500 repsectively.)

      If they were to port these programs to GTK+, their licensing costs to developers is $0. And the last I checked, it's not against the terms or the [L]GPL or otherwise illegal to keep private modifications private.

      Thus Bruce Perens' decision to go with GTK+ and GNOME; it may not be in the spirit of the Linux community to let people be selfish with their code and keep it to themselves, but it is within the rights granted by that community.

      If he took this commercial-friendly argument to its logical conclusion he would dump the GPL'd Linux from UserLinux in favour of BSD.

      A disguised BSD troll are we, then? Because your logic is flawed if you believe being "commercial-friendly" only means you have to be willing to let people sell your freely-given code back to you in a proprietary system. The GPL may not be commercially friendly to businesses who sell software to make a living, but it's sure commerically friendly to businesses that use software to make a living.

      Jay (=

      (1) This is a rhetorical example only. No knowledge of Fry's IT planning should be inferred.

  71. The reason why by Synn · · Score: 2, Insightful

    It's actually pretty simple. Both GNOME and KDE are quite good and equally comparable as far as features and usability. Sometimes one may be better in one area and worse in the other, but they pretty much stack up well against each other.

    The difference is that KDE uses QT which is GPL and GNOME uses GTK which is LGPL. The LGPL is more friendly towards proprietary software which is something that the target audience of UserLinux(corporations) will want.

    So UserLinix has chosen GNOME.

    It's not the desktop at issue, it's the library licensing.

    1. Re:The reason why by platypus · · Score: 1

      he LGPL is more friendly towards proprietary software which is something that the target audience of UserLinux(corporations) will want.

      So UserLinix has chosen GNOME.


      This is a non-sequitur. While it's right that LGPL the LGPL per se is more "friendly" towards companies wanting to develop proprietary software, this argument doesn't suffice for prefering GTK over QT. There are just more factors involved in that decision. And QT is used much more often than GTK for proprietary development, so actually that argument is wrong. This is because using QT saves much more money spend for developer time than it costs.

      I think one reason why GTK was choosen was exactly that btw. because now customers have to pay more money to ISVs offering Userlinux development (since they need longer to fullfil a task), and OTOH the ISV doesn't have to share some of his (smaller) revenue with trolltech.

      But I think the decision to leave out KDE/QT really will hurt userlinux, because it really hinders adoption of windows shops which often are coding using C++, Visual basic, and so on, but seldom are coding in C. Also, QT on windows is very good, so good that I know companies which prefer to pay for QT instead of using MFC etc., even if they don't plan to port their software to other plattforms.

      If you read the mailing list, the proponents of including KDE/QT seem to have much more practical experience and are arguing much more with real life examples than the GTK only camp - this speaks for itself. The only tangible argument I've seen was something about Mr. Perens' prospective investors/clients prefering GTK.

      If coding for GTK in C is to be the main alternatice against .NET and winforms, MS won't have to break out in a sweat about this.

    2. Re:The reason why by damiam · · Score: 1
      If coding for GTK in C is to be the main alternatice against .NET and winforms, MS won't have to break out in a sweat about this.

      Perens doesn't mention this, but another advantage of GNOME is that it has excellent C# bindings, so .NET programmers can easily develop GNOME apps with Mono and GTK#. This in addition to the myriad of higher-level languages GTK already supports, including Perl, Python, Ruby, C++, Java, Ada, TCL, Scheme, PHP, Pascal, and a few others. QT does have a decent group of bindings as well, but they're lesser in quantity as well as (subjectively) quality.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    3. Re:The reason why by Anonymous Coward · · Score: 0

      It's a good thing that Gtk has more language bindings, one of which is gtkmm which is designed much better than Qt, and another which is Gtk#.

    4. Re:The reason why by be-fan · · Score: 1

      That's the thing, though. They're not evenly matched. There is tons of stuff that both GNOME and KDE tried, but that KDE managed to pull off and GNOME did not. Kparts, KIO, DCOP, etc, are an integral part of a modern KDE desktop, and they give all applications powerful features transparently. Meanwhile, you could remove the GNOME equivilants (bonobo, gnome-vfs, orbit) and nobody would notice because the GNOME desktop just doesn't leverage these underdeveloped technologies. So the choice was not between two equals, with licensing terms being a tie-breaker. Rather, a (dubious, for reasons others have mentioned here) licensing issue was used to trump all the other benifets provided by KDE>

      --
      A deep unwavering belief is a sure sign you're missing something...
    5. Re:The reason why by Anonymous Coward · · Score: 1, Informative

      > one of which is gtkmm which is designed much better than Qt, and another which is Gtk#.

      gtk has a number of high quality bindings, but Gtkmm is certainly NOT one of them.

      I'm a MFC programmer by day, and a Linux hobbist by night, and about a year ago, I was looking for something to learn. I did not want to learn Qt.. I prefer GNOME to KDE, and I did not want to learn pure gtk, I'm a C++ programmer, not a C programmer.

      I ended up starting to learn Gtkmm by writing a IM client (imagine that :) ). I gave up after a month or so because half of the classes in gtkmm worked as expected in the docs, and half of them didn't . I also found the toolkit much harder to learn and use than MFC, but I was willing to stick with it nonetheless. I ended up learning Qt soon after, and I was highly impressed by it's ease of use. It seems to be quite elegent toolkit. However, it didn't look like my desktop of choice, so after a while, I learned wxWindows, which uses gtk on X11, and have never looked back.

      I urge all C++ developers to look at wxWindows for GNOME-related development, and Qt of course for KDE development. Gtkmm however, just has a very half-baked feeling that makes me wonder if most people who write applications with it have to look at it's source to do things.

  72. Bruce Perens: Theory of Evolution by tacocat · · Score: 4, Insightful

    According to the article he mentions that UserLinux is intended to be based upon Debian. The reason why is extremely important to understand:

    The overall viability of UserLinux will be based upon the size and quality of the ecosystem of solutions around it, both Free and proprietary. So, in order to get any Free Software into businesses, our Free system must promote the creation of a large collection of proprietary solutions that do not exist today. As we penetrate the enterprise, we will continue to move Free Software higher up the application stack, until these businesses make use of Free Software predominantly. But you need proprietary software to get in the door.

    We are looking at what is best described as an evolutionary process of development. This follows a more organic than Project Management path.

    In the beginning there was Minix and it was expensive and not free but it worked well enough. Following this was the development of a free replacement called Linux.

    Some time after that came Applixware, an Office Products Suite. It was expensive but it worked. Following this was StarOffice and now OpenOffice.

    Given these two, we have evolved the software industry to such a point that there is now a very adequate if not excellent free software which can provide us with:

    • A base Operating System: Linux
    • A very suitable browser: Mozilla
    • A very suitable Office environment: OpenOffice
    But before each of these could exist, there was a non-free proprietary variant. Not always the case: Xfree, Postgresql, vi, emacs, and so on. But they do exist.

    The point that is so important here to understand and except is that Open Source, Free, non-Proprietary software is getting really good all the time.

    Distributions themselves are following the same path. SuSE and RedHat cost money, but Debian and it's variants are getting better and gaining a larger percentage of users who consider these to be "good enough" to use every day.

    In order to effectively provide a "good enough" solution to the Businesses, Open Source communities have to provide all of their free software as easily as possible. But it is extremely important to make it possible for someone to develop a proprietary software solution to fill in the niches that Debian is missing today so that Free Software, as a whole, can move into an ever increasing circle of "good enough" for users.

    If there are any barriers of any kind to that entrance it will hurt the overall effectiveness of this process. Any questions or concerns, current or future, about the licensing of software development under Qt, MySQL or anything else, will only make it less attractive to a developer to invest in making a product for UnitedLinux only to have it completely fucked up by a bunch of whining lawyers.

    Personally, I'm rather surprised that he didn't select GNUstep as the desktop of choice. Long term, it might be the best of the three options mentioned.

    1. Re:Bruce Perens: Theory of Evolution by zangdesign · · Score: 3, Interesting

      You make a good point about GNUStep - by selecting it, you open up the work of Mac software as well. Some not-so-drastic changes to the code and a recompile later, you've got an x86 version of PPC application.

      Perhaps GNUSteppers should start THEIR own distro.

      Heck, with the licensing options, all the major desktops should have a distro. Let the market decide!

      I'm not kidding.

      --
      To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
    2. Re:Bruce Perens: Theory of Evolution by Anonymous Coward · · Score: 0

      When did minix cost? It was free as far back as I can remember, back when there was Linux .9 kernels. In fact wasnt Minix Linus's idea for linux?

      http://www.cs.vu.nl/~ast/minix.html

    3. Re:Bruce Perens: Theory of Evolution by Anonymous Coward · · Score: 0

      Minix was published along with a book, and the book publishing house owned significant rights to Minix (or all rights, not certain). The legal status of a Minix distribution was decidedly muddy. If you bought the Minix book, and downloaded patches to Minix and applied them yourself, you were clearly legal. But that's not a good long-term solution.

      Many years too late, Minix was finally GPL'ed and you can distribute it now. And it has new life running microcontroller projects and such. It ought to be great for a PDA. But it's years too late to conquer the world, because Linux is so successful and much more advanced.

      Minix, on the other hand, is smaller and easier to understand. It does less than Linux and scales less well, but it is a better fit for tiny hardware (thus the new life in microcontroller projects and such).

      For a beginning OS course, Minix is still the way to go; Linux is much more sophisticated and thus more complex. (I'd hope an advanced OS course would study Linux, hopefully giving extra credit to anyone who fixes a bug or adds a feature to Linux.)

    4. Re:Bruce Perens: Theory of Evolution by Anonymous Coward · · Score: 0

      That was a very good post, well reasoned and clearly explained. It deserves its +5 score.

      I just want to point out a word error: you used "except" where you clearly meant "accept".

      I take nothing away from the rest of it for this error; I just wanted to point it out so you can get the two straight.

    5. Re:Bruce Perens: Theory of Evolution by aperezbios · · Score: 1

      There have been several attempts at creating GNUstep distributions; LinuxSTEP (development halted for now) and Simply GNUstep spring to mind. I'm a devoted GNUstep user, and frankly you could easily make a Debian-derived GNUstep based distro. Are you interested in helping?

    6. Re:Bruce Perens: Theory of Evolution by zangdesign · · Score: 1

      I'm willing to discuss the possibility of such a thing.

      --
      To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
    7. Re:Bruce Perens: Theory of Evolution by norwoodites · · Score: 1

      You know a GNUStep OS (not just another distro) would be a really good thing, maybe use HURD as the kernel.

    8. Re:Bruce Perens: Theory of Evolution by aperezbios · · Score: 1

      lets discuss...send me an email.

    9. Re:Bruce Perens: Theory of Evolution by zangdesign · · Score: 1

      where do I send it? You're email is not public shown.

      --
      To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
    10. Re:Bruce Perens: Theory of Evolution by aperezbios · · Score: 1

      send it to aperezbios@yahoo.com (this is my junk email address) and I'll be sure to check that account

    11. Re:Bruce Perens: Theory of Evolution by cehardin · · Score: 1

      That is happening, slowly though I'm afraid.

      It started with LinuxStep and SimplyGNUstep (which is my project).

      LinuxStep has fiddles out and SimplyGNUstep is kinda there (it's slow going)

      SimplyGNUStep started out as a 100% redo of a distro, but that was too much work. Now it is debian based.

      That means you can install a Sarge Debian system, add the SimplyGNUstep repository, and then pull a whole crap load if preconfigured ready to run GNUstep apps.

      The directory layout is very similar to OS X, which I think is what people want.

      I wrote a little article on this, which you can find here:
      http://www.osnews.com/story.php?news_id=481 8

      Chad

  73. Re: why gnome over kde? by DAldredge · · Score: 1

    The GNOME libs are LGPL.

    You do not have to distribue source that links against unmodified LGPL libs.

  74. Arguing over proposed applications? by daemonc · · Score: 2, Interesting

    Funny that the KDE developers' argument boils down to: "We have these proposed applications, most of them aren't finished yet, or haven't even been started, but they're going to be really great and integrate well with an enterprise desktop, so you should choose KDE and ditch Gnome."

    Thing is, Gnome has the applications NOW, already integrated and complying to a well tested Human Interface Guide.

    Further more, nobody ever said UserLinux wouldn't include KDE apps. There is no reason their "killer apps", should they ever reach a usable state, couldn't be included. The decision is to go with Gnome as the default desktop, and these KDE developers have shown no reasons why this isn't the best choice. There is no need to include both desktops, as a user can only be running one at a time anyway.

    Finally, if you don't like the decision, don't use the distribution! There are plenty of other distributions out there, at least two of which still use KDE as the default desktop (Mandrake and Suse). Funny that you don't see Gnome developers demanding that these distros switch to Gnome.

    Let the whining and flaming commence!

    --
    All that we see or seem is but a dream within a dream.
    1. Re:Arguing over proposed applications? by jas79 · · Score: 1

      Further more, nobody ever said UserLinux wouldn't include KDE apps

      Bruce Perens made it cleary that Qt and kdelibs won't be include. that means no KDE apps.

    2. Re:Arguing over proposed applications? by 10Ghz · · Score: 1
      Funny that the KDE developers' argument boils down to: "We have these proposed applications, most of them aren't finished yet, or haven't even been started, but they're going to be really great and integrate well with an enterprise desktop, so you should choose KDE and ditch Gnome."

      Thing is, Gnome has the applications NOW, already integrated and complying to a well tested Human Interface Guide.


      So, does GNOME have Kiosk-framework? You know, the absolutely needed thing for corporate deployments? KDE has it, has had it for a while now. KDE has just about all the stuff you could need. If it lacks something, it will propably be in 3.2, which is released early next year.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    3. Re:Arguing over proposed applications? by Anonymous Coward · · Score: 0

      > Thing is, Gnome has the applications NOW, already integrated and complying to a well tested Human Interface Guide.

      KDE has more applications than GNOME NOW. Then regarding the applications they are talking in the future is those which are not at all in the GNOME.

    4. Re:Arguing over proposed applications? by damiam · · Score: 1

      Kiosk support is in GNOME 2.6, due out March 2004. GNOME is generally quite good about keeping their release schedules. That said, Kiosk mode isn't absolutely needed for corporate deployments. Quite a few corporations give employees unrestricted access to their own Windows machines, and probably quite a few wouldn't choose to limit their Linux machines either. But, for those that want it, it'll be there.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    5. Re:Arguing over proposed applications? by twener · · Score: 1

      > GNOME is generally quite good about keeping their release schedules.

      And bad at delivering promised features within. "New fileselector in GNOME 2.0. Sorry, will be in 2.2. Again sorry, perhaps 2.4. Damn, but 2.6 finally!"

  75. In Redmond by News+for+nerds · · Score: 1

    he must be laughing his ass off over this stupid flame war.

  76. support from a KDE programmer by Anonymous Coward · · Score: 1, Interesting

    His arguments are well thought out, and I must admit that the lisensing issue had bitten me at least once with respect to Qt. I also realize what this will cost me personally to retool to Gnome, but in the end will likely be worth it. I would have made the same choice a couple of years ago if I had known that Gnome was not also based on Qt (I had already tooled up with KDE by the time).

    Oh well... time to learn yet another GUI API...

  77. Kiss Of Death by nurb432 · · Score: 1

    This entire concept of forcing one or the other will be the kiss of death for the project. In this case the end user needs to be given the choice..

    While I'm all for not giving end users too many choices to confuse matters, the 2 main desktop camps are way too rabid about choosing THEIR desktop over the other. This will just degenerate into a holy war and get nowhere.

    That said, I vote for KDE, since it's much more professional, consistent and mature. Both from a user viewpoint ( the GUI ) and a programmer's view point ( QT/KDE libs )

    --
    ---- Booth was a patriot ----
  78. Re: why gnome over kde? by Anonymous Coward · · Score: 0

    "Perfectly reasonable as a project decision, even if I personally disagree with the choice it led to."

    In terms of the greater question of choice in Linux, it's not a big deal, since we're free to choose another distro. I use Mandrake. I run windowmaker as my graphical environment, but if I want to fire up konqueror, it's no problem, likewise Gnome stuff, even though for the actual graphical environment, I don't use either.

    However, as a "project decision" it's a poor one, since it will make for a poorer distribution than Mandrake. Precisely because users have choice, you want to create a distribution that is a good choice.

  79. Re:What's the big deal by Anonymous Coward · · Score: 0

    UserLinux is targeted at the enterprise community. It probably (and hopefuly) be used by non-geeky types who simply use what is installed on their computers. You can see KDE go the same way as netscape if UserLinux ever becomes popular.

    I don't buy that argument for a minute for the simple reason that KDE exists and is quite popular now w/o a UserLinux distro in existance. It's not the same kind of situation as netscape and IE were in which was a unified platform that had only one distribution. For a situation like the one you describe to occure it requires that UserLinux essentialy not only take the corprate world by a storm but also all the other distros too.. .and frankly I just don't see that happening.

  80. Is "proprietory-friendly license" so important ? by pirhana · · Score: 2, Interesting

    As someone who have read almost all the mails in the list so far, I think the decision to go with GNOME was taken in a BAD way atleast. First there was a lot of discussion about the technical merits of these 2 and later it was decided to go with GNOME based almost solely on "proprietory friendly" license of GTK. If that was the only criteria for selecting the softwares, then what is the purpose of discussion? its easy to compile a list softwares with the above license. Also, as far as I understand(someone correct me if I am wrong in this please) QT has been adopted by the ISVs far more than the GTK. It boasts of a customer base including IBM, Adobe , Samsung and many many other high profile companies. So if all these companies have found the technical mertis of QT(better documented APIs, more powerfull, architectural superiority etc.) more than the "proprietory unfriendly"[sic] nature of the license, then why the same logic does not apply to Userlinux? . The same goes with Epiphany also. It seems to be (not finalized though) decided that Epiphany would be the default browser. There was a lot of discussions about browser choice also. Mostly it was agreed that Mozilla firebird was the best choice . But then at the end Epiphany was chosen(?) based solely on the "better GNOME integration".Again why there needs to be a lot of discussion about the technical merits if at the end some criteria like "proprietory friendly" nature of the license and "Gnome integration" are going to be the sole criteria. Is these 2 factors so important to give such a huge weightage over technical merits and everything else ? After carefully reading all the mails also, I have not found a good answer for these concerns. Perhaps I am missing something. But anyway I wish all the best for Bruce and his effort.

  81. Re:What's the big deal by ultrabot · · Score: 5, Insightful

    Companies don't want to support multiple versions of Linux. Thus a single version is going to be what drives Linux in business.

    There will be at least RHEL, SUSE, and now UL.

    So much for Open Source ideals.

    I don't see any conflict with OSS ideals. You are not forced to use UL, it's all Open Source, you can install whatever you want, you can install UL apps on other Linux platforms, etc.

    --
    Save your wrists today - switch to Dvorak
  82. Competition by Synn · · Score: 2, Insightful

    Choice is good mostly because it promotes competition. As a user in a business environment, choice isn't good because you want to unify the experience. So your systems admin should be choosing for you.

    But outside that environment you need choices so that you can be gauranteed of getting the best quality.

    It's like, why do we need any other car company except for Ford? Well, because if no other car company came into existance we'd probably still be driving around in model T's. Instead we have many car companies each of which is trying to get us to use their product. They do that by being "newer and better" than the other guy.

    Competition drives innovation.

  83. Why doesn't someone ... by petabyte · · Score: 4, Insightful

    get working on building the KDE add-on.

    I'm pretty much a gnome-only fellow; gnome 2.4 on this gentoo box and dropline gnome on my slackware laptop. That said, I still need qt and the kde-libs. I rarely use them (well, I really only use them for lyx and k3b as there isn't anything like k3b for gtk) but I still need them.

    Stop arguing some stupid holy war (I like gnome and I'm not moving and I have friends that swear by KDE and aren't moving). If United isn't going to take KDE, someone needs to build a dropline-ese KDE that will bold right on.

  84. Re:What's the big deal by sydb · · Score: 5, Informative

    I don't mean to stalk you in this story!

    You can see KDE go the same way as netscape if UserLinux ever becomes popular.

    KDE made a choice when it based itself on Qt. Times change and KDE's problems have changed - KDE is a good Free Software* desktop environment. But because Qt is GPL'd, it presents a barrier to proprietary development that is against the goals of UserLinux.

    If being the default desktop of UserLinux is so important to KDE, why don't they re-implement their desktop ontop of an LGLP'd toolkit?

    If it's not so important that they are willing to do that, then people should stop being upset. In the choice of a default there will be a winner and one or more losers. XFCE lost here too, but they're not whining. Only one desktop can be the default!

    As for the Netscape comparison, I think there were other factors which led to Netscape's demise, like a bloated product (Communicator). Look how people prefer Firebird over Mozilla. There's still time for IE to be ousted - all the time in the world, from now to the end of time.

    * Or is it? Look at what TrollTech say here - TT don't want you using Free Qt on inhouse projects, but the GPL says you can. This makes me distrust TrollTech.

    --
    Yours Sincerely, Michael.
  85. Get the story straight. by Karma+Sucks · · Score: 1, Informative

    First of all this is old news, there is no continuing debate. This is old stuff.

    Second of all, the Qt license discussion is completely moot. Have you even read the proposal?

    Third of all, Bruce Peren's project is vapourware unlike the KDE project which is already progressing. Just look at the latest KDE-CVS-Digest and you see already Kapture and KDebConf coming out of this.

    --
    (Please browse at -1 to read this comment.)
  86. Patents by ultrabot · · Score: 4, Insightful

    Well then, lets put it on the table. This project is not by or for the community. Yet it depends on the contributions of a huge number of developers.

    When, oh when will people realize that the future of Linux and Open Source is dependent on corporate adoption? Bruce says it himself - widespread corporate adoption is necessary to combat the sw patent and other (idiotic) legal threats.

    If the corps are not with us, they will be on the other side and we will lose.

    --
    Save your wrists today - switch to Dvorak
    1. Re:Patents by twistedcubic · · Score: 1


      When, oh when will people realize that the future of Linux and Open Source is dependent on corporate adoption?

      Maybe. But the future of free software certainly doesn't depend on "corporate adoption".

    2. Re:Patents by Elektroschock · · Score: 1

      In Europe there *is* a Linux desktop market, but none of these customers wants Gnome. Gnome may be fine for a solaris linux or an developer desktop but not for the average customer. Gnome 2.x by default looks boring and conservative. Gnome 1.x was fun, but a hacker desktop. I think Bruce tries to reinvent the wheel. There is a Desktop market and it is a KDE desktop market. Probably the states lack behind because RedHats Gnome committment and the KDE license FUD and KDe bashing by ximian. I personally use Gnome sometimes, but I prefer KDE. Gnome's zealotish anti-KDE attitude always seemed to be very silly to me. KDE never started Gnome bashing, they concentrated on their plattform and everything works well together.

    3. Re:Patents by ultrabot · · Score: 2, Insightful

      Maybe. But the future of free software certainly doesn't depend on "corporate adoption".

      Don't underestimate the power of stupid laws and US legal system.

      --
      Save your wrists today - switch to Dvorak
    4. Re:Patents by Anonymous Coward · · Score: 0

      Let me know what your native language is, so I can post condescending and ignorant comments to you with a broken translation from whichever babelfish language I feel is closest.

  87. Get The Story Straight, People by Karma+Sucks · · Score: 1

    First of all this is old news, there is no continuing debate. This is old stuff.

    Second of all, the Qt license discussion is completely moot. Have you even read the proposal? KDE is integrating GTK+ to allow LGPL development.

    Third of all, Bruce Peren's project is vapourware unlike the KDE/Debian project which is well under way independent of UserLinux. Just look at the latest KDE-CVS-Digest and you see already Kapture and KDebConf coming out of this.

    --
    (Please browse at -1 to read this comment.)
  88. Re:What's the big deal by Anonymous Coward · · Score: 0

    >> Gnome is the better "supported" option because it doesn't require royalties for closed source development.

    Then why is that we see a hell lot of QT based proprietory applications and very very less of those GTK based applications ? companies like Boeing, Daimler Chrysler, Disney, Fujitsu, General Electric, Hitachi, Honda, HP, IBM, Intel etc. have developed QT based applications. Why not many GTK based applications ?

  89. What I don't understand by theantix · · Score: 4, Interesting

    I can understand the business decision to go with one DE over the others... this makes good sense. What I *don't* understand is why Perens refuses to include the KDE libs by default. Including the libs and a few choice applications to fill the gaps where kde apps outperform what gnome offers (k3b and others) would do a lot for improving the total package of UserLinux and keep some of the critics at bay.

    If I can put on my tinfoil hat for a second here, the best reason I can think of for not including the KDE libs is to stir up the traditional KDE/GNOME debate and get more coverage on slashdot and other sites. Trolling for media coverage, it's the wave of the future!

    --
    501 Not Implemented
    1. Re:What I don't understand by Brandybuck · · Score: 1

      I agree. I have no problems with a distro choosing one desktop or another as the default. And I have no problems with a distro moving the other desktop off of the first CD image. But removing it entirely, so that the user who wants it must grab it elsewhere, is boneheaded.

      At least include Qt and the core KDE libraries! If they had chosen KDE instead of GNOME, do you think they would banish GTK+? Of course they wouldn't!

      But this is coming from the Debian camp. Though not officially Debian, Bruce was a long time Debian developer. Debian wouldn't distribute the kdelibs back during the "controversy", even though none of the contentious issues touched the LGPL kdelibs. They just didn't want KDE. Not all of the Debian developers, to be sure. Most of them are great people. But there were a significant number of Debian developers who didn't.

      The politics of Debian are strange and convoluted. I fear that UserLinux will inherit them.

      --
      Don't blame me, I didn't vote for either of them!
    2. Re:What I don't understand by IamTheRealMike · · Score: 1
      If I can put on my tinfoil hat for a second here, the best reason I can think of for not including the KDE libs is to stir up the traditional KDE/GNOME debate and get more coverage on slashdot and other sites. Trolling for media coverage, it's the wave of the future!

      Sigh, no, read the article. This whole issue has been misunderstood by a lot of people - Perens is not dropping KDE because he doesn't like it, or he thinks it's a bad desktop - he's dropping it because to business he wants to present a single unified platform.

      Reread that last sentance. The key word there is PLATFORM. If he included kdelibs, he'd now be presenting two platforms, not one.

      This is not a personal snub against KDE or its developers, despite how some of them react. It's about business, and consistancy at the platform level.

    3. Re:What I don't understand by mrroach · · Score: 1

      I'm guessing it's for the same reason that just removing the iexplore.exe executable on windows doesn't satisfy a lot of people's requirements for removal of IE. If it's still there, it's still considered supported.

      Using Opera as an example, statically-linked QT adds about 1.3 Meg to the app size. If it's that important for someone to use qt, statically link.

      -Mark

    4. Re:What I don't understand by Anonymous Coward · · Score: 0

      He's saying that UserLinux will not require KDE, or KDE libraries. A standard UserLinux system will have GNOME and GNOME libraries. If you want to be a certified UserLinux expert, you will have to learn all about GNOME. If you want to also learn KDE, that's fine. If you want to run a KDE app on your UserLinux desktop, that's fine too, and you can even use apt-get to install it. But you should understand that not everyone with a UserLinux certification will be able to support you.

      Got it?

  90. Re:What's the big deal by sydb · · Score: 2, Informative

    This is a better link to the GNU perspective on the matter.

    --
    Yours Sincerely, Michael.
  91. Re:why ignore the obvious solution? KDE only! by Anonymous Coward · · Score: 0

    RTFA? Its about the licensing options of the underlying toolkits, not technical superiority.

  92. Re:What's the big deal by ankit · · Score: 2, Interesting

    I am not denying Qt licensing issues. They are real. And since KDE is based on Qt, it goes against them.

    The point I wanted to make was why the KDE team was so concerned about not being included in UserLinux. If Userlinux is ever to become as popular as they hope it would (and it does not include KDE), it would be a big loss for KDE.

    --
    Don't Panic
  93. Think about users, not geeks by rueger · · Score: 5, Interesting

    Lord, this arcane bickering seems pointless. From my reading Perens' goal is to develop a distro that "just works" for the average corporate user.

    I just wrapped up my semi-annual "download a linux distro and see if the damned thing will work" exercise, and once again I'm falling back on Win2K, which does everthing that I need, and does it with a minimum of BS.

    Over the last few years I've tried RedHat, Mandrake, and a half dozen other distros, on both bare machines and dual boot systems. In every case I hit the wall when trying to implement some simple or essential feature. Every time I found myself led into that arcane and recursive hell known as man pages and how-tos. (and mailing lists, and discussion groups and...)

    I'm good with hardware, and can make Windows do anything I need. I have managed to troubleshoot some exceedingly obscure problems in the past. Still, once again I've abandoned Linux because I can't afford to invest weeks of obscure research just to do day to day work.

    I really want to be rid of Microsoft products. I find them more irritating than useful, and surely don't like MS' business practices.

    I love OpenOffice and have pretty much abandoned MS Office. I like Mozilla, and use a wide variety of freeware and open source products.

    I would in a minute abandon MS Windows if it were practical, but to do that I need a distro that will do what Windows does:

    Find and configure all my hardware, set up internet access and networking to allow all of the computers on our system to share files, and easily allow others to use the printers attached to my PC, easily set up my two video cards and monitors, set up to sync my PalmPilot.

    And have decent looking fonts.

    So far every distro I have tried has blown at least two of these basic goals and has offered no easy way to achieve them.

    Again, I cannot afford to spend days or weeks tracking down the obscure solution to make something like HotSync work.

    It does not matter to me whether this happens with GNOME or KDE. If I can boot from CD and have all of these things come up working, I'll buy it.

    If including only GNOME allows Perens' the time to make a truly reliable installer, then I'm for it.

    1. Re:Think about users, not geeks by Anonymous Coward · · Score: 2, Interesting

      If you're going to wait for Linux to become w2k, you're going to be waiting a long time. Every os requires time to learn (an perhaps even more time if you have to 'unlearn' a previous one) and anyone who isn't prepared to invest that time will likely go back to the os that they're already familiar with.

      Linux is a wonderful os that will do everything you need, but if by 'easy' you mean 'like w2k', then you might as well save yourself some time and just forget about it. It isn't w2k and it never will be.

    2. Re:Think about users, not geeks by cozziewozzie · · Score: 1

      You might want to give Knoppix a try. It's quite good at autodetecting and configuring things and can be installed on a hard disk through a relatively easy procedure, giving you a customised Debian install. Don't know if it can solve all your problems, but might be worth a try.

      And if you have Windows machines lying around, it should be no problem to get good fonts. Besides, there is a Debian package which downloads MS fonts off the web and makes them available to your system. Not sure if it still works, though.

    3. Re:Think about users, not geeks by iii_rjm · · Score: 1
      Now don't take this personally :), but when you said:

      Besides, there is a Debian package which downloads MS fonts off the web and makes them available to your system. Not sure if it still works, though

      You illustrated one of his main points

    4. Re:Think about users, not geeks by cozziewozzie · · Score: 1

      Well, it worked for me :) I just didn't want to give false hope. :P

  94. Re:What's the big deal by sydb · · Score: 3, Insightful

    ...companies like Boeing, Daimler Chrysler, Disney, Fujitsu, General Electric, Hitachi, Honda, HP, IBM, Intel etc. have developed QT based applications. Why not many GTK based applications ?

    That's fine, but that's their choice; they can still do that under a Gnome-default UserLinux. But do you think it would be right for UserLinux to encourage a TrollTech "tax" by choosing KDE? I don't.

    --
    Yours Sincerely, Michael.
  95. Re:why ignore the obvious solution? KDE only! by Anonymous Coward · · Score: 0

    You are speaking out of your fucking fat ass again...

    Lots of claims, no proofs...

  96. Re:What's the big deal by Anonymous Coward · · Score: 0

    So much for Open Source ideals.

    I don't see any conflict with OSS ideals. You are not forced to use UL, it's all Open Source, you can install whatever you want, you can install UL apps on other Linux platforms, etc.

    You're overlooking the big picture. This particular issue is just an example of what's to come as Linux becomes more widely adopted. I expect to see more and more of these kinds of issues over time. If you don't, then it will be because people have agreed to adopt one thing or another. Which means that you're back to a single solution. So much for choice...which means so much for Open Source ideals.
  97. Re:What's the big deal by sydb · · Score: 4, Insightful

    Quite; note that the specific reason Gnome chose LGPL for it's libraries was to encourage popularity!

    --
    Yours Sincerely, Michael.
  98. Re:What's the big deal by platypus · · Score: 2, Insightful

    Strawman. The point from the pro-KDE proponents was that it's better for Userlinux to at least also include the KDE libraries and QT. Then the market can decide.

    Userlinux is free to choose whatever they want into their distro, it's just that they should not pretend to (strive to) be _the_ Free linux enterprise distribution.

  99. Licensing Argument is Bogus by Anonymous Coward · · Score: 0

    If you develop commercial software, the SDK licensing fee means practically nothing. If you don't think your commercial app will bring in much more than the cost of SDK licensing, well, don't get into the business.

    In general, the only trouble with licensing fees is if they are run-time royalties.

  100. Re:What's the big deal by TandyMasterControl · · Score: 4, Insightful

    UserLinux doesn't even *exist* yet. That's a far cry from having a monopolist's power to "persuade" 90plus percent of the market to switch over to using Internet Destroyer instead of Netscape more or less overnight (as they upgrade from windose95 to 98 or 2000).
    There are no grounds to make an MS - UserLinux comparison. In fact it's ludicrous.

    --
    Johnny Quest has two Daddies.
  101. Anticommercial commercial distro by ChrisWong · · Score: 4, Insightful

    It's funny that one would exclude the top C++ GUI toolkit for commercial development for the purpose of making the distribution friendly for commercial development.

    1. Re:Anticommercial commercial distro by IamTheRealMike · · Score: 2, Informative
      It's funny that one would exclude the top C++ GUI toolkit for commercial development for the purpose of making the distribution friendly for commercial development.

      I'm pretty sure the top C++ GUI toolkit for commercial development in terms of statistics would be the Microsoft Foundation Classes, or the ATL (or a mix). It probably isn't Qt.

      You're also overlooking the efforts of the GTKmm team, which is made up of several people with many years of commercial development experience. All the reviews of GTKmm I've seen are positive - it has the advantage of being pretty new and therefore modern. Look at the email addresses of people on the GTKmm lists sometime - there's plenty of commercial development going on there, but GTK doesn't have a dedicated sales team that compiles big lists of them.

    2. Re:Anticommercial commercial distro by Chester+K · · Score: 1

      It's funny that one would exclude the top C++ GUI toolkit for commercial development for the purpose of making the distribution friendly for commercial development.

      Not really. Nobody likes MFC anyway.

      --

      NO CARRIER
  102. Re:What's the big deal by sydb · · Score: 4, Insightful

    Bruce says he wants to provide as default enterprise class support for one (1) desktop environment.

    In his words: Because these service providers are basing their business upon a commodity product, there are already economic limits upon how profitable they can be. The difference between one and two GUIs may spell profitability or bankruptcy for some of our service providers. In a similar vein, internal support and engineering staff at businesses that employ UserLinux would like to have only one GUI SDK to develop for and maintain.

    He also says that anyone is free to install Qt/KDE and the vendors are free to sell support for it if they so choose.

    Now, I don't see how he can do fairer than this without compromising the stated aims of the project.

    --
    Yours Sincerely, Michael.
  103. really by Karma+Sucks · · Score: 1

    Where is the GNOME proposal? Where are the people doing the GNOME work? Nowhere. KDE/Debian is already doing great on its own.

    --
    (Please browse at -1 to read this comment.)
  104. Re:what is the point of ul? all they are doing ... by Anonymous Coward · · Score: 0

    I agree.

    His rationale is that he is focusing the business community on one standard set of solutions (chosen by King Perens himself.) He is saying that if that standard common environment exists, businesses will be quicker to jump on the bandwagon and move over to Linux.

    I personally think that businesses value the choice to determine their own set of tools.

    Perens may be right that it is easier to maintain the one standard solution, but in this case, losing KDE is just losing too much. COmpanies may like standards, choosing from 20 solutions would not make sense.

  105. Re:Is "proprietory-friendly license" so important by ultrabot · · Score: 1

    Perhaps I am missing something.

    Yes - you are missing the difference between a library and an application.

    --
    Save your wrists today - switch to Dvorak
  106. Re:Is "proprietory-friendly license" so important by Anonymous Coward · · Score: 0

    > Yes - you are missing the difference between a library and an application.

    I know the difference between the library and application. But would you care to explain how does it affects my points or arguments ?

  107. Re:Is "proprietory-friendly license" so important by ultrabot · · Score: 1

    I know the difference between the library and application. But would you care to explain how does it affects my points or arguments ?

    My point was that license is hugely important for something that the user might link to while w/ application it doesn't matter as long as it's "free enough".

    As far as your other points go, look and feel are a "technical argument" in an end-user application like a browser.

    --
    Save your wrists today - switch to Dvorak
  108. They should go with XFce by Anonymous Coward · · Score: 0

    GNOME and KDE are too far gone into bloatland.

    1. Re:They should go with XFce by Kethinov · · Score: 2, Insightful
      They should go with XFce

      GNOME and KDE are too far gone into bloatland.
      XFce = minimalism. Minimalism != user friendly.

      (UserLinux == user_riendly) ? (KDE || GNOME) : all_others;
      --
      You're right, I wouldn't steal a car. But if it were possible, I sure as hell would download one!
    2. Re:They should go with XFce by bmzf · · Score: 1

      XFce = minimalism. Minimalism != user friendly.

      Dude, that's pretty biased. Notice that even if XFce wasn't 'minimalism' you set it to be just that: (XFce = minimalism)

      ( I hope you're not writing any software I use ;)

    3. Re:They should go with XFce by FooAtWFU · · Score: 1

      If UserLinux is user-friendly, will it come with randomly generated background music?

      (insert groans here)

      --
      The World Wide Web is dying. Soon, we shall have only the Internet.
    4. Re:They should go with XFce by antiMStroll · · Score: 1

      That's a statement as silly as following with "therefore complexity is user friendly." Your analysis might be relevant at the Ion WM level but you're hard pressed to make a case at the XFce level this way.

  109. Re:What's the big deal by Master+Bait · · Score: 1
    If you don't like the distribution, don't use it.

    Before it even gets out of the gate, it's becoming apparent that nobody is going to be using it.

    --
    "Only in their dreams can men truly be free 'twas always thus, and always thus will be."
    --Tom Schulman
  110. Re: why gnome over kde? by Anonymous Coward · · Score: 0

    > default girly pastel-colored look

    You mean like the snazzy 80s pink and blue pastel in Sun's CDE desktop?

    But I agree with your point. When the "Plastic" theme came out for KDE, all the fanboyz were drooling despite the fact that it had obvious visual issues and looked like a very cheap combination of Win98 and OS X. "Plastic" was pretty much the right word for it - it was a walmart-quality imitation of something else.

    And then they went ahead and made it the standard theme. Pretty sad when the masses of 20-year-olds that masturbate to anime can overrule GOOD TASTE. It's like thinking a girl is cute because she loaded up on makeup.

  111. Mod parent +1 interesting by ultrabot · · Score: 1

    And your point is?

    Come on, drop the rhetoric, you got my point.

    Using C for a base library has a number of nice side effects, like: 1. Not needing a C++ compiler

    Who cares? gcc is here, and it has good C++ support now.

    The rest of the stuff I mostly agree with. However, the Python bindings for Qt are generated from C++ code by Swig, so that they get the OO feel automatically. Seems like a good thing for me.

    --
    Save your wrists today - switch to Dvorak
  112. Qt cost vs Windows. by Anonymous Coward · · Score: 1, Interesting

    One argument that I keep hearing from the KDE/Qt camp is `If you are going to make commercial applications, you can afford to pay the price of a license'. There is even a study that shows that for a team of 10 developers at 75,000/USD year for two years, the price of Qt is peanuts compared to the total investment.

    The flaw I see with this analysis is that it is not in par with the rest of Linux. You do not see sysadmins paying for Apache, Perl, MySQL, Postgress, Python, Slashcode, PostNuke/PhpNuke or any content management system, and I am sure anyone running a porn site, or using Linux in an eneterprise settings is probably mkaing more than the 75,000 per developer listed above.

    Bruce's position is consistent with the fact that there are no strings attached, no special royalties, no special treatment of users: everything is free, and you can build entirely fre e systems with no strings attached with GNOME as the platform.

    Also, 2,600 dollars per license might not be much in Britain or the US, but it is sure a hell of a lot of money for a startup anywhere else where Linux is being deployed: Malaysia, China, India, Brazil, Peru, Colombia, Chile, Argentina.

    Hey, 2,600 dollars will get you a Windows Server edition, Visual Studio and quite a few extra goodies from MSDN, am just not sure that telling commercial developers to ponny up more than they have to for MSDN is a winning position here to promote Linux over Windows on the desktop.

    Hey on Microsoft you can even get the Platform SDK and the Microsoft.NET development tools for free and use SharpDevelop instead, and that my friend is a lot cheaper than Qt is.

  113. By fiat? by Stonent1 · · Score: 1, Troll

    What does that mean? Is he going to spin a small Italian car around and see what it points to? I've never heard the term "by fiat".

    BTW I guess since he lost his job at HP, he's had to clean himself up a bit. I guess he gave up on the Dr. Who lookalike style.

    1. Re:By fiat? by Anonymous Coward · · Score: 0

      It means Gnome was built by Fiat, which certainly explains a lot.

  114. Put up or shut up by Anonymous Coward · · Score: 0

    This argument is rediculous. It's Bruce's project, his time, his effort, his blood sweat and tears to put the project together. If you don't like his decision, don't work on the project and don't use the software. If the project fails because he made a bad decision, then he has noone to blame but himself. Additionally, this decision hasn't prevented UserLinux users from using KDE. They can still install it from the Debian packages.

    Why doesn't KDE start a similar project that only uses QT based software? The two distros can compete head to head. Then we'll see what the business community wants. Nobody bitches and moans that Klaus Knopper only supports KDE on the Knoppix CD. The guys from Gnoppix went out and created their own Gnome based version.

    The beauty of free software is that you have the freedom to do whatever you want with it. Bruce can do whatever he wants. KDE can do what it wants. You can use whatever product appeals to you. The downside to all this freedom is that it quickly becomes very difficult to provide any kind of decent technical support. It's no wonder that it is so hard to debug some users software. They could be using any number of kernels, with hundreds of possible patches, and hundreds of other kernel configuration options. And that's just in the kernel. Add to that the complexity of supporting numerous different desktop environments and you now find that it's nearly impossible to give and kind of decent support. That's why all of the major distro's are finally realizing that you have to have a reference platform to debug against. Otherwise, after spending 20 hours trying to figure out why some users ALSA sound won't work, you discover that they added some weird patch to their kernel that somehow breaks sound. This happens all the time. It's why projects like OpenBSD won't even try to give support if the user is using anything other than the stock kernel.

    But what's disgusting about this argument is that KDE developers and users feel entitled to have KDE included in UserLinux. They don't care about the fact that someone else is going to have to do the work to support it. All those persons whining about this decision ought to put up or shut up. Start your own QT focused project. Or even better, if you're such fair and upstanding people, start your own project that includes both Gnome and KDE. Then you can reap what you sow.

  115. Re:Is "proprietory-friendly license" so important by pirhana · · Score: 1

    >> My point was that license is hugely important for something that the user might link to while w/ application it doesn't matter as long as it's "free enough".

    Let me clarify this point again. The argument that "proprietory-friendly" license alone will attract ISVs is a myth. If that was the case, then GTK should have attracted a lot of ISVs and QT would not have. But what we see at present is GTK has failed in this aspect and QT has indeed attracted a lot of ISVs. So what is important is not just license but other things like technical superiority and better documentation and support. Atleast in this case( GTK vs QT) these factors have beaten license issue. Also when I say "technical merits", I dont mean "look and feel". What I mean is better architecture, APIs , documentation and support.

  116. Troll by Elektroschock · · Score: 1

    Haha, Linux desktop means KDE. Nobody cares about II companys as they are all nuts. QT was not GPL? Well, freeQT creates a true incentive to license your works as GPL while Gnome libs LGPL license tends to spread the license variety. Gecko? KDE wanted to integrate it but then KHTML was backed by Apple and turned out to be better and faster.

    KDE developers never started Gnome bashing as Miguel and other did. It seems to me that this reflects the disadvantages of Gnome. the user does not want Gnome for the desktop. Despite RedHat no mayor distribution used Gnome as default.

    1. Re:Troll by IamTheRealMike · · Score: 1
      Despite RedHat no major distribution used Gnome as default.

      Yet Red Hat is still the most popular distro, by a long way. Even in Europe, I now see lots of people using Red Hat (certainly this was true where I used to work).

      Have you considered that people choose their distro based on what desktop they prefer? I used to use SuSE because they had a nice KDE desktop, but when Red Hat 8 came out I changed and have not looked back. I changed partly because Red Hat have a very nice default desktop (based on gnome2).

  117. Re:What's the big deal by Anonymous Coward · · Score: 0

    Gnome is the better "supported" option because it doesn't require royalties for closed source development.

    I just think it's ironic that the people who want to collect royalties don't want to pay them.

  118. Re:What's the big deal by HiThere · · Score: 3, Insightful

    If you haven't seen this before, then you haven't been watching the distributions. Lots of the smaller distributions have only shipped with their favored window manager. (Possibly because the guy that put them together couldn't be bothered with one he didn't use.)

    UserLinux is making a bigger splash than most of these...but this doesn't really mean that it will go anywhere. Who's going to adopt it? Why?

    Well, nobody who likes KDE will adopt it. Nobody who likes blackbox. Or TWM. Or...

    So it will only be adopted by those individuals who already like Gnome. OK. What's the first step towards getting Linux into a corporation? Somebody puts it on his computer to check it out! So from the start they've limited their initial penetration. Now if they do a good enough job, this may get enough good PR that others will check it out. But if they don't like Gnome, they probably won't like this. So they'll go back to SuSE or Mandrake or Debian or...

    Basically, then, this is intended to take customers from either MSWindows, or from a distribution that normally runs under Gnome. Like Red Hat.

    I'll be surprised if this is a good enough distribution to succeed, but there's nothing wrong with him trying.

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  119. Don't be an idiot... by Karma+Sucks · · Score: 1

    The KDE/Debian effort is already going on and strong. UserLinux on the other hand is a vapourware project. KDE/Debian effort already has code in CVS and is nearing the release of a LiveCD.

    --
    (Please browse at -1 to read this comment.)
  120. You don't understand Bruce's goal. by khasim · · Score: 1

    Yes, KDE has a lot of stuff that GNOME does not.

    But KDE also has ONE ITEM that Bruce will not accept.

    With Qt, you have to pay a one time fee to do commercial development.

    GNOME does not have this restriction.

    Bruce has stated his criteria often enough, but the KDE fans just won't listen to him.

    1. Re:You don't understand Bruce's goal. by DF5JT · · Score: 1

      "With Qt, you have to pay a one time fee to do commercial development."

      Unless I have completely misunderstood Bruce (which may well be the case), the goal for UserLinux is to provide for an enterprise solution based on Linux and coming with a series of features that are specifically addressing the needs of medium to large enterprises.

      That is what I would call a commercial product and it is a product that is completely useless, unless it comes with a package of installation, support, upgrades, scalability and extendability.

      The codebase of such product may well be free (and it should be), but an enterprise that will decide to deploy UserLinux will find large comfort in having a commercial partner for the tiny part of developping applications for their own need.

      Trolltech is such a partner and it is a unique partner that it offers two identical products with different licensing schemes.

      A large company, distributed all over the world has specific needs for its IT-infrastructure. Key factors for the successful migration to Linux are scalability, flexibility and manageability. These things can be achieved by UserLinux and KDE with its enterprise features that will support this kind of deployment by providing a management subsystem designed to do the very job.

      Not only are these key features missing in GNOME, they don't even appear in any paper by the GNOME foundation announcing the stringent development of such features. Without these features, however, what exactly is the point of UserLinux? Right, there is none, it's just one more distribution, not more.

      As to the license: The commercial licensing scheme only becomes relevant when the enterprise hires developpers to write software that will commercially be exploited at one point. The costs for this are negligible and transparent (http://www.trolltech.com/products/qt/pricing.html ).

      Given the target audience (large enterprises with funds large enough to consider a migration to Linux on a large scale), the costs for licensing QT are low, ridiculously low when compared to other development platforms and you know what you are buying, since the codebase is open.

      I can't think of any restriction in connection with this pricing that would outweigh the huge advantages of KDE over GNOME in an enterprise environment.

      As a salesman I sometimes deal with CEOs in large scale enterprises and they could not care less about licensing schemes of this magnitude. In my opinion Bruce's arguments don't hold water for the target audience, which makes UserLinux redundant even before it has been released.

      If you think this is another KDE vs. GNOME flamewar, you are dead wrong. The whole discussion is about a product worth millions of Dollars in planning, supporting, migrating and deploying large, complex infrastructures and for that you want to have the best tools for the job.

      These tools cannot be found in GNOME, not even in a preliminary strategic paper of the GNOME foundation, let alone in workable code.

      This licensing discussion seems like an ideological smokescreen, blinding people's eyes for the reality in large enterprises.

      We will probably end up with UserLinux/GNOME and EnterpriseDebian/KDE at one point, because the KDE core will certainly not burn its vision on enterprise features in KDE.

    2. Re:You don't understand Bruce's goal. by be-fan · · Score: 1

      The problem KDE fans are having is that Bruce is willing to give up all that stuff that KDE does have that GNOME does not in trade for a one-time fee that developers have already indicated (by choosing Qt for commercial products) that they are willing to accept!

      --
      A deep unwavering belief is a sure sign you're missing something...
    3. Re:You don't understand Bruce's goal. by benjamindees · · Score: 1
      This licensing discussion seems like an ideological smokescreen

      It is. He originally had mysql as the default database, even while he was making his "free commercial development" licensing arguments. He didn't change to postgresql until someone pointed out that this was somewhat hypocritical.

      --
      "I assumed blithely that there were no elves out there in the darkness"
  121. Re:why ignore the obvious solution? KDE only! by Anonymous Coward · · Score: 0

    Mod parent up. While it's obvious to everyone who has a penis bigger than 5" that Gnome is for fags and KDE is for real Linuxers, this is a pretty good point. Damn I hate that.

  122. Is Bruce changing his values? by Anonymous Coward · · Score: 0

    As we know, the issue is about licensing. Commercial (read: proprietary) software can be built with GTK without licensing fees. The same cannot be said of QT. Nevermind the hypocrisy of people who want to sell software not being willing to pay for it. The question I have is: why is Bruce Perens pushing for such an initiative? The 'open source' philosophy has always distinguished itself from the 'free software' philosophy by emphasizing pragmatism over ethics. But the preferred licensing was more or less the same. Whether for ethical or pragmatic reasons, both camps preferred licensing that made it possible to run, study, redistribute, and improve the source code.

    The choice of Gnome over KDE represents a real change. The change is that Bruce is now making a choice about what software to use based on his commercial interests, rather than what software/license is 'better' in either a pragmatic or ethical sense. This choice is based on the degree to which it facilitates the production of proprietary software.

    It's certainly his right to do so, and I'm not saying this perspective is any better or worse than any other philosophy. It's just noteworthy, is all.

  123. Do you NOT know what Debian is? by khasim · · Score: 1

    UserLinux will be based on Debian.

    "Why not let the decision-makers at that company make that decision? The company could choose just one UI, but they could choose between KDE and GNOME. Now, Bruce Perens makes that choice for them."

    No. Bruce will be officially supporting GNOME. Bruce will be shipping GNOME.

    But that does NOT mean that any company will be PREVENTED from installing UserLinux and then adding KDE or even adding KDE and removing GNOME.

    apt-get install

    Learn it.
    Live it.
    Love it.

    "Tools to do just that already exist in KDE, but they are not available for GNOME. So KDE has a clear advantage there."

    Fine, now just get Trolltech to remove the fee for commercial developement and I'm sure Bruce will re-evaluate his decision.

    Oh, Trolltech won't do that? Well, that's too bad. I guess Bruce's decision to base it on GNOME was the correct decision then.

  124. Non promoting non-free? by Anonymous Coward · · Score: 0

    So, you think that choosing a LGPL (that allows the creation of non-free software for free) library over a GPL (that forces you to create free software) one is "not promoting non-free software"?
    All libraries should be as QT, you want to use it to get rich and create non-free software? Then PAY for it. You want to create free software? Then get it free.

  125. Can't someone buy out Trolltech and set QT free... by Gnulix · · Score: 1

    ...once and for all, so that we needn't go through this darned discussion every second week!

  126. Read what he as written. by khasim · · Score: 1

    The reason he is against KDE for this project is that QT requires a one time payment for commercial development.

    Yes, as you've pointed out, lots of companies have paid that. So what?

    Bruce is basing this distribution on his personal beliefs and agenda.

    He believes that there is a lot of development that will be done in the future in countries that cannot easily afford the QT fee.

    "What I don't understand is why dump the really good KDE for a not so good (IMHO) Gnome just because of toolkits."

    Because of the licenses involved. Bruce made that very clear in his first paper on this. It is because of the licensing.

    "My answer to the UserLinux proposal is: use KDE as desktop, support Gnome also and improve interoperability (freedesktop is already a common direction for that)."

    Great. Then you can start your own distribution and I wish you well. Bruce has a different goal.

    1. Re:Read what he as written. by afd8856 · · Score: 1

      My understanding of Bruce's goal is that UserLinux will be the one distribution that all comercial software and hardware makers will chose as a point of reference. I fear a future in which all comercial developers will only support UserLinux. I believe this is what the KDE developers fear also. (I am actualy very interested of this problems, I have followed the entire issue very close since it's started as I feel that this will affect me and everybody who loves Linux and/or KDE)

      --
      I'll do the stupid thing first and then you shy people follow...
  127. Mod parent up! by khasim · · Score: 1

    Most of the "why didn't he include KDE" comments I see lack the understanding of WHY he chose not to use KDE.

    If it matters so much to the KDE people, then they can get Trolltech to change the licensing. And don't give me any of that crap about "you should pay if you make a profit". That's the reason Bruce chose GNOME instead of KDE so your argument is circular.

    If the KDE people cannot get the license changed, then they are free to release their OWN distribution and make it even better than UserLinux.

    But if you're not going to get the license changed AND you're not going to release your own version THEN STFU and stop trying to impose YOUR viewpoint on Bruce.

    This is Bruce's time and effort and he is allowed to do whatever he wants with them. Whether it meets with YOUR approval or not.

    1. Re:Mod parent up! by fritmebufstek · · Score: 1
      If the KDE people cannot get the license changed, then they are free to release their OWN distributon and make it even better than UserLinux.
      Great idea, that's what we're doing for some time already. Expect some great stuff to flow out of this somewhen in the future.
  128. Re:why ignore the obvious solution? KDE only! by Hard_Code · · Score: 1

    "For my part, I think GNOME beats KDE by a long shot because it is based on C and not C++. The number of competetent C developers far outweighs the number of competent C++ developers."

    So you immediately position the argument as what is best for programmers? Classic failure which is exactly why we need a USERLinux to begin with. While Gnome has wrestled with exposing widgets in so many APIs it is just a mess of tangled spaghetti, KDE from the beginning has started from the goal of making the end product seamless and intuitive for users, and chosing the single best way to do that instead of suffering death by a million cuts to whatever programming paradigms are required for whatever language has geek chic today.

    The phrase "X beats Y because it is based on Z programming langauge" is a complete red herring when we are talking about end user experience.

    --

    It's 10 PM. Do you know if you're un-American?
  129. A Failure of Open Source? by Anonymous Coward · · Score: 0

    Perhaps we're about to see a real "failure" of the open source community: the inability to make an API that properly abstracts the GUI, etc, so that it doesn't matter -what- DE you're using.

    1. Re:A Failure of Open Source? by Anonymous Coward · · Score: 0

      Sigh. There are several; wxwindows, qt, fox, swing, tk, xlib, lesstif, and so on are not DE dependant. Some are open source. However, they don't match the DE, so run into the same criticism that gnome apps under KDE do, and vice versa.
      What DE you're using really doesn't matter. Any apps you have the appropriate libraries for run.
      The issue is toolkit consistancy; adding more toolkits doesn't really help that, as the dozens of them in existance prove quite nicely.

  130. In other news by elFarto+the+2nd · · Score: 1

    XFCE has just released version 4.0.2

    Regards
    Stephen

  131. apt-get install by khasim · · Score: 3, Interesting

    "My understanding of Bruce's goal is that UserLinux will be the one distribution that all comercial software and hardware makers will chose as a point of reference."

    If hardware makers support it, then, because it is just re-packaged Debian, that support will be available for any Distribution out there.

    If software makers support it, then, because it is just re-packaged Debian, the KDE people can add it to KDE.

    "I fear a future in which all comercial developers will only support UserLinux."

    Why? It's just re-packaged Debian. What are you afraid of?

    "I believe this is what the KDE developers fear also."

    Afraid of what, SPECIFICALLY?

    1. Re:apt-get install by afd8856 · · Score: 1

      KDE loosing popularity, its developers, its support from comercial sponsors.

      --
      I'll do the stupid thing first and then you shy people follow...
    2. Re:apt-get install by twener · · Score: 1

      You would be surprised if you knew how few commercial sponsoring KDE actually gets.

    3. Re:apt-get install by DrSkwid · · Score: 1

      I wasn't aware that KDE had a corral containing popularity, developers and sponsors. To turn them loose seems rather irresponsible; like the ALF releasing a thousand mink into the English countryside, there's bound to be a few casualties.

      ooh, you meant losing.

      Such ignorance is legion.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    4. Re:apt-get install by afd8856 · · Score: 1

      You know, i speak and undestand realy good English, considering that is a foreign language for me.

      --
      I'll do the stupid thing first and then you shy people follow...
    5. Re:apt-get install by DrSkwid · · Score: 1

      Good for you.

      Welcome to the hellmouth :)

      i speak and undestand realy good English

      I speak and understand really good English

      Though one should really use write/comprehend rather than understand when it is written English.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  132. Re:why ignore the obvious solution? KDE only! by TrekCycling · · Score: 1

    I think he meant because of speed and lack of bloat. Let's get real, KDE is a pig. Gnome is much thinner to run. Just my personal experience, but I'd much rather use a desktop programmed in C++ than Java or Python, just like I'd rather use a desktop programmed in C than C++.

  133. Absolutely;-) by Anonymous Coward · · Score: 0

    > The first thing UserLinux needs to fix is its own name.

    I agree. The name is misleading.

    It should learn from other distributions. For instance, RedHat Linux is targetted to people with red hats. SuSE is targetted to girls named SuSiE. Gentoo is targetted to penguins. Mandrake is targetted to people who like May apples. Libranet is targetted to people who are born under the Zodiac Libra sign and want to do networking. Lycoris is targetted to people who enjoy the licorice root.

    UserLinux seems to imply that it actually wants someone to use the Linux distribution. Since according to GNU no-one uses Linux (they use GNU/Linux), this name is clearly misleading. (*tongue placed firmly in check*)

  134. Re: why gnome over kde? by twener · · Score: 1

    > many people find it hard to take seriously a desktop environment with a default girly pastel-colored look

    And I have thought with an one million dollar budget there would be some dollars included to switch the widget style.

  135. Re:What's the big deal by Anonymous Coward · · Score: 0

    I just think its ironic that people who want to make money don't want to give it away.

  136. Nor does KDE... by Natalie's+Hot+Grits · · Score: 1

    ... have this restriction.

    Only QT has it. It is perfectly legal and accepted in the KDE community to produce KDE applications with the GTK+ toolkit.

    Sodipodi already does this, and there is a ongoing project to make it negligable work to write full GTK+ applications that link to KDE libs for DCOP communication, print and file dialogues, KIO Slaves, drag-n-drop, etc..

    This is how they are getting OOo and mozilla looking like KDE, using the same techniques.

    (note: this is not currently possible for GNOME+Qt development)

    In other words, KDE already has compatibility and choice for your toolkit of choice, and it is improving every day. GNOME doesn't.

    --
    Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.
  137. Open source is also excluded by Anonymous Coward · · Score: 1, Interesting

    The GPL is incompatible with several open source licenses including Apache, Helix, and Eclipse. By relying on GPLed *libraries*, you're saying that the only open source worth writing is GPL-compatible open source.

    BTW, at least half the companies you mention also produce products based on Gtk+ (WebSphere from IBM and Realplayer are probably the most prominent of the list). Every company I've been to produces lists like these. If one person in a company buys your product, you can automatically say "This company uses our product". They may just be buying it to test it or they may discover that it doesn't suit their needs. It doesn't matter, as long as they bought it, marketing can get away with saying that they are a customer.

    And let's not forget the small company. Thousands of dollars is *a lot* of money. Money is tight, and I don't see anything particularly amazing in Qt that would cause it to pay for itself. Small companies don't often care about portability (so they stick with one platform), but even when they do, Qt isn't the best choice. WxWindows or Swing or SWT or pyGtk+ or PhpGtk+ are far cheaper than commercial Qt (their free) and they're at least as easy to use.

  138. QT does NOT need licence for commercial products! by no_choice · · Score: 2, Informative

    How many times does this need to be pointed out? QT/KDE does NOT require the purchase of a licence to be used in developing commercial products!!

    Read the QT FAQ. You can freely (free as in speech and as in beer) develop software for whatever purpose you desire using QT, including commercial purposes. Millions of people use software developed with free QT for commercial purposes every day.

    To make this even more clear: QT is released under the GPL. The GPL forbids anyone from restricting the use of QT or products derived from QT under that licence. In other words, you CANNOT develop a product derived from GPL'd code and say "you can only use this for non-commecial purposes."

    The GPL is an excellent licence for commercial software for reasons to numerous to mention, vastly superior to, say, a typical Microsoft licence.

    Lets say a business has to choose between two software products with equal capability but different licences. The first product is free to use, can be used on many machines, comes with its source code, and can be modified and redistributed. The second product needs to be licenced seperately for each machine it runs on, cannot be copied internal let alone redistributed externaly, and does not even reveal its source let alone allow for it to be modified. Which is product is superior for commercial purposes?

    I think this confusion about licencing arises because far too many people confuse COMMERCIAL software development with CLOSED SOURCE software development. COMMERCIAL does not equal CLOSED SOURCE!!! I use Free (open source) Software every day for commercial purposes. Millions of people do.

    Now, for those people who want to write a closed source software product, they can also use QT for this purpose... however in that case they must purchase a commercial licence from TrollTech, instead of licencing it under the GPL. This is only logical... if you want to sell a software product under a closed source, proprietary licence, and not allow your customers to get the source or have the right to freely use it, why the hell should Trolltech (and other developers of Free software) have to give you THEIR source for free?

    This is why I think that QT/KDE has a SUPERIOR licencing scheme to that of GTK/Gnome... QT/KDE allows for closed source development but ENCOURAGES open source.

    I have great respect for Bruce Perens, but he is way off base on this. If there must be only one desktop environment in UserLinux it should be KDE. It is very disapointing to see him get behind the platform that is LESS beneficial to free software.


  139. Re:What's the big deal by be-fan · · Score: 1

    No they can't. Because UserLinux doesn't include Qt or KDE by default! That's the whole issue here. Its not just that they pick GNOME as the default, but that they don't include Qt or KDE at all. You can say "apt-get kde" but in a business environment, that could be a problem.

    --
    A deep unwavering belief is a sure sign you're missing something...
  140. Why GNOME is needed in KDEBIAN.... by Moritz+Moeller+-+Her · · Score: 1
    GNOME is a great motivator for KDE. By insulting the efforts of KDE, people who love KDE get motivated.

    GNOME made Trolltech release the QT under the best of all free software licences: the Great Public Licence (GPL).

    GNOME provides a lower initial cost, lower quality alternative to companies

    • not wanting to code their GUI apps as open source
    • not being profitable enough to afford an initial investment in better tools.
    This keeps the costs of Qt for commercial closed source companies reasonable.

    GNOME provides a way to code GUI applications in the older C language for developers unwilling to adapt newer languages. Did I forget something? Anyways, good that it exists, but KDE/Qt is a lot better. Thanks for chasing KDE to perfection and providing a backup in case KDE moves in the wrong direction.

    --
    Moritz
  141. Re:What's the big deal by oobar · · Score: 1

    Either Qt is GPL or it isn't. If it is, then companies are free to make proprietary in-house modifications and not release them to anyone, as the GPL faq points out. TrollTrech states that "it's our policy that..." or "We do not intend that...", but if Qt is really GPL then that can really be nothing more than an emphatic plea, not a legal proclamation.

  142. Re:why ignore the obvious solution? KDE only! by Hard_Code · · Score: 1

    Performance is fast becoming an obsolete excuse. Most desktop machines are "fast enough". What is more important is usability. Furthermore, if the target is the enterprise, the marginal cost of buying a faster machine is FAR outweighed by productivity gains. That is even if you subscribe to the notion that there are meaningful and non-mitigatable performance differences between programming languages/styles.

    --

    It's 10 PM. Do you know if you're un-American?
  143. Qt dosn't require royalties by autopr0n · · Score: 1

    it requires a single, cheap developer license. It's like $100 or something. And you can still develop in house aps for it, or use GTK with KDE.

    --
    autopr0n is like, down and stuff.
    1. Re:Qt dosn't require royalties by Trejkaz · · Score: 1

      Actually a single developer is $1,550.

      But that's still nothing if you're a company selling software in the US. Maybe if you're selling it somewhere like Australia where everything has to be made to sell cheap thanks to competition from across the ocean.

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
  144. No Perl? by harlows_monkeys · · Score: 2, Insightful
    In the same section about choices where he lists GNOME as the choice over KDE, he also lists Python over Perl.

    If this means that all UserLinux-specific scripts ini the distribution will be written in Python, that's fine. If it means that Perl won't even be in the distribution, he's nuts.

    There are certain things that pretty much everyone assumes are available on Linux systems, and Perl is one of them.

    The business world already was offered Unix systems with one choice for everything (that's how most commercial Unix systems worked), and Linux is kicking their asses, and one of the reasons is that Linux includes all these alternatives.

    Picking one GUI for users is one thing, but for things that are used by programs rather than directly by users, a good Linux-for-business distribution should have them all.

  145. Userlinux won't get popular by autopr0n · · Score: 0

    Business don't give a fuck about needing to buy a $100 developer license to release closed code. Most of them aren't going to release closed source apps, and the GPL allows them to write internal applications and keep them secret.

    and in any event, GTK is still an option for development on KDE based machines!

    What business wants is a nice, consistent GUI, they don't care about GPL vs. LGPL vs. Closed source even. (Lots of them run windows). KDE is a smoother GUI, and better integrated. I honestly don't believe UserLinux will get that much traction if they stick with Gnome over KDE. KDE is much more 'professional' in terms of smoothness, etc. and that's what business care about.

    --
    autopr0n is like, down and stuff.
    1. Re:Userlinux won't get popular by sydb · · Score: 1

      the GPL allows them to write internal applications and keep them secret

      You would think so wouldn't you? But TrollTech don't!

      But TrollTech don't!

      --
      Yours Sincerely, Michael.
  146. Re:Is "proprietory-friendly license" so important by mrroach · · Score: 1

    I think the following should be considered:

    (from http://www.mozilla.org/products/firebird)

    Mozilla Firebird is a Technology Preview.

    While this software may work well enough to be relied upon as your primary browser, we make no guarantees of its performance or stability in its pre-1.0 state and it should not be relied upon for mission- critical tasks

    Seems like a pretty good disincentive for basing your platform on it.

    -Mark

  147. Re:What's the big deal by Arker · · Score: 2, Insightful

    You can see KDE go the same way as netscape if UserLinux ever becomes popular.

    If you can, there's something wrong. You can't kill a free software project like that. It only dies if it no longer serves the developers goals.

    Personally, I'd rather see them adopt GNUStep than either one - and if enough folk agree with me we might see another project taking that route. I'm sure there will continue to be other distros that choose to support KDE. It's not the end of the world, because free software is not the same world as the one where your expectations were formed.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  148. Re:what is the point of ul? all they are doing ... by Anonymous Coward · · Score: 0

    i agree, loosing kde is too much.

    if there were 12 majour desktops of equal meter, sure, pick 1 or 2.

    with two majour really well engineerd desktops there is no confusion. loosing kde is too much.

    our business will be running kde as we move on to a switch to debian destkops, sans UserLinux.

  149. Re:why ignore the obvious solution? KDE only! by TrekCycling · · Score: 1

    And KDE is more usable than Gnome? I would debate this. KDE has more options. It's questionable whether that makes it more usable. I'd say in some ways it makes it more complicated thus less usable.

  150. Re:What's the big deal by autopr0n · · Score: 1

    UserLinux is targeted at the enterprise community. It probably (and hopefuly) be used by non-geeky types who simply use what is installed on their computers. You can see KDE go the same way as netscape if UserLinux ever becomes popular.

    The reason that NS4.x died was because it sucked, plain and simple. Windows came with IE1, 2 and 3 and no one ever used them because they didn't have the features that netscape did. When IE4 came out, it was just better then netscape. The fact that it was installed helped, but NS was based on a bloated, shitty codebase that had been cramed with features without good engenering, and couldn't be fixed (mozilla, for example, is a totaly new codebase).

    Netscape sowed the seeds of their own destruction.

    Right now KDE is better. And it dosn't have the problems netscape did. In all honestly, I don't think userlinux will catch on untill Gnome is as good or better the KDE, or unless they use KDE.

    --
    autopr0n is like, down and stuff.
  151. Re:What's the big deal by krogoth · · Score: 1

    "MCSEs may be cheaper, but it takes 10 of them to do the same job as one Unix server admin" -- slashdot

    --

    They that quote Benjamin Franklin on liberty and safety deserve neither.
  152. Stop doing drugs... by Moritz+Moeller+-+Her · · Score: 2, Informative
    The pisser with the Qt license is that a project must decide before writing the first line of code which license they plan to release under and you can't change your mind later. You can't dual license either. And if you opt for free you can never port to an unfree system.


    Why? YOu can always use a commercial qt license and release your code under any license you wish. It's your code after all. You can even modify the commercial qt and ship the modfified qt with your closed source product. Also you can use GPL code on MacOSX, EMbedded, all Unix/Linux and Windows using X+Cygwin. Which is pretty much 100 % of all relevant OS.

    The KDE camp still refuse to admit they made an unholy alliance with the devil and will forever be damned for it. The GNOME camp saved the Free Software world by realizing the danger and running balls to the wall to quickly organize themselves and catch up close enough to KDE/Qt to prevent it from ever becoming a defacto standard.

    The Gnome camp should be thanked for making TrollTech give us qt under the linux license GPL. Mission accomplished, I'd say. Of course, if Miguel de Icaza had worked on Harmony, the free qt replacement instead of using the gimp motif ripoff toolkit in C with OO latched on top to code a crappy second Desktop environment, we would also have just KDE today, using Qt under GPL as well.

    GNOME has produced some nice software, but without dotcom money, it probably won't be able to keep up with the technically superior QT/KDE system. Basing the so-called "user"-linux on Redhat's and Ximian's GNOME and excluding Qt/KDE is a waste of everyone's time.

    --
    Moritz
    1. Re:Stop doing drugs... by jmorris42 · · Score: 1

      > Why? YOu can always use a commercial qt license and release your
      > code under any license you wish.

      No you can't. Try reading the license before posting again. Sure, in theory, an app developed on the commercial Qt could be converted to Free. One time, and all commercial development would either have to stop or a total code fork take place. Because developers using the Free Qt MAY NOT CONTRIBUTE CODE to a tree that will ever see commercial release.

      They did it that way to prevent the otherwise totally reasonable tactic of developing entirely on the Free toolchain and only having one commercial license to do the final release build on.

      > The Gnome camp should be thanked for making TrollTech give us qt under
      > the linux license GPL. Mission accomplished, I'd say.

      Mission not accomplished. From RMS's viewpoint Qt is now free, because he cares not about cross pollination with the commercial software world. But in the real one, it matters.

      --
      Democrat delenda est
    2. Re:Stop doing drugs... by Moritz+Moeller+-+Her · · Score: 1

      Well, that makes sense. Once you decide to make a free product, you can not go back to commercial. Just like you can't seriously switch linux back to a "commercial" mode from GPL. I admit that a dual license is not possible.

      --
      Moritz
  153. Who the hell cares? by autopr0n · · Score: 2, Insightful

    The license issue is not an issue for any business. I mean come on. We are talking about people who use windows for most of their work. Sure, in theory you can develop on windows without Visual Studio, but how many enterprises actually do? The Qt closed-source license fee is less then the cost of VS.net, and hell It's only about half a days worth of Programmer salary anyway. If you can afford to pay programmers, you can easily afford to buy Qt licenses. Or, you can run GTK apps in KDE. It's not like its difficult.

    the cost of Qt is a complete non-issue for enterprise software.

    Finally, if you are actually developing your own software, for release you're probably not going to need the same kind of 'hand holding' support packages from these companies.

    You really think someone running windows isn't going to avoid KDE because the GPL isn't "free" enough for them, that they need LGPL?

    --
    autopr0n is like, down and stuff.
  154. Gtk==gpl, qt==[gpl|qpl|commercial] by Anonymous Coward · · Score: 0

    If I wanted to legally make commercial linux software, why should I go with the toolset that was created because the other was not polically correct and offers less flexible licencing options?
    The only problem left is that qt is not always kde-aware enough, but that is a small problem.
    Using Gnome is the big problem...

  155. Obligatory by Anonymous Coward · · Score: 0

    But who'd want a desktop whose logo is a smelly foot?

  156. Shower by Anonymous Coward · · Score: 0

    If this is what take to get one /.er to shower... it's all worthy.

  157. Ugh!!! by autopr0n · · Score: 1

    I just want to see UL succeed, and Gtk way is easier to sell to commercial companies. Many companies would cringe if they were told that developing for Linux is more expensive than developing for Windows.

    Dude, developing in house apps will still be free via the GPL. Not many companes actualy sell software, and those that do can either buy the license or use GTK.

    --
    autopr0n is like, down and stuff.
  158. Well ... by Anonymous Coward · · Score: 0

    If he decided to use Gnome - its ok, because its his personal project. And Gnome is not so bad afterall. So where is the problem ? Why to discuss it so much and even flame each other :)

    1. Re:Well ... by be-fan · · Score: 1

      They way he announced it, it did not put it forward as "his personal project." Rather, it was to be a grandiose project that brought Debian to the enterprise.

      What are the chances that UserLinux is wildly successful? Certainly, its within the realm of imagination. Well, if UserLinux is hugely successful, it will create a world without KDE. Not just a world without KDE, but a world in which KDE wasn't even allowed to compete for mindshare, just arbitrarily left out of the game.

      --
      A deep unwavering belief is a sure sign you're missing something...
  159. Score -1, Wrong by jemfinch · · Score: 1

    Go look at the GNU Win CD or The Open CD and count the Qt/KDE apps. Or let me save you the time and do it for you. Zero.

    That's because QT/KDE hasn't been ported to Windows yet. There's nothing stopping someone from taking the Free GPL'ed QT (and KDE) and porting it to Windows. It just hasn't been done yet.

    The pisser with the Qt license is that a project must decide before writing the first line of code which license they plan to release under and you can't change your mind later.

    Are you insane? The copyright holder on a piece of code can decide at any time what license he wishes to use in his code. If he develops against the Free QT, he has to release his source code under a GPL-compatible license. If he later decides to go commercial, then he can relicense all later code (the code he originally released under the GPL will remain GPL for all time) and write against the Professional/Enterprise QT and release it under whatever license he wants.

    You can't dual license either.

    You can do whatever you want as long as it's GPL-compatible.

    And if you opt for free you can never port to an unfree system.

    You can't take your code that you released under the GPL back, no. But that's the case with any code you release under the GPL. You can later choose to go proprietary and close your source, though. All you have to do is purchase a Professional/Enterprise QT license.

    The KDE camp still refuse to admit they made an unholy alliance with the devil and will forever be damned for it.

    If by "forever be damned for it" you mean "must link with GPLed software," then sure, you're right. Although I wouldn't exactly call that an "unholy alliance with the Devil."

    Repeat after me: Free QT is the GPL. There are no further restrictions on your code and there can be no further restrictions on your code. All the same restrictions that normally apply to linking against GPLed code apply here.

    Jeremy

    1. Re:Score -1, Wrong by Anonymous Coward · · Score: 0

      "The pisser with the Qt license is that a project must decide before writing the first line of code which license they plan to release under and you can't change your mind later.
      Are you insane? The copyright holder on a piece of code can decide at any time what license he wishes to use in his code. If he develops against the Free QT, he has to release his source code under a GPL-compatible license. If he later decides to go commercial, then he can relicense all later code (the code he originally released under the GPL will remain GPL for all time) and write against the Professional/Enterprise QT and release it under whatever license he wants."

      Bzzt. Trolltech demands that you develop with the commercial licenses already purchased if you want to use a non-gpl-compatible license for your software. While in general you are correct, you seem to have been unaware of the details of trolltech's commercial license. The copyright holder may indeed choose at any time, but if the copyright holder choses to use commercial QT, the copyright holder must obey the restrictions of that.

  160. Windows != standard by Trejkaz · · Score: 1

    A standard... that doesn't necessarily explain why Windows apps look about three different ways:
    Windows 95 look and feel still exists on some apps;
    Windows XP look and feel is currently predominant;
    Windows .NET look and feel is in Office, Visual Studio, etc.

    Clearly there are at least three different toolkits lurking about for Windows or everything would look exactly the same, right?

    --
    Karma: It's all a bunch of tree-huggin' hippy crap!
    1. Re:Windows != standard by DrSkwid · · Score: 1

      + Delphi
      + Borland C++ (anyone remember OWL?)
      + Qt on Windows
      + GTk on Windows
      + wxWindows
      + Java Swing / AWT

      I probably missed some too

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    2. Re:Windows != standard by Trejkaz · · Score: 1

      Qt delegates to the Windows XP toolkit, Delphi seems to also (witnessed in Exodus), wxWindows when I last used anything which used it delegated to the Windows 95 toolkit but they might have a later one available. Last I used Borland C++ theirs was using Windows 95's toolkit too.

      Gtk+, yes. That does look very different. The horror. Why they can't make a style for Gtk which looks as good as Qt's is beyond my comprehension.

      And the horrors of Java. The new Swing 'tries' to look like Windows XP but fails in many ways. Also there is IBM's SWT, which on Windows seems to use the Windows 95 toolkit, judging solely on its ugliness.

      But of course even on an operating system with an extremely 'standard' toolkit (Mac OSX), you still have occurrences of Gtk, Java, etc.

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
    3. Re:Windows != standard by DrSkwid · · Score: 1

      does Qt use the XP extended open file dialog?
      I'm not sure of it's API name, MS likes to keep the MSDN subscription treadmill rolling with a new file dialog every few weeks so it's hard to tell.

      I have no idea but in my experience this is the usual place that falls foul.

      My experience of Borland C goes back way too far I think, do you remember the awful looking widgets they used to ship?

      wxWindows uses the native controls too but I'd gladly bet a few $ that you can tell a wx app from a VC++ app from a VB app.

      I'm a plan9 user these days, there has been a stab at a few widgets but hardly anyone uses them. One can select text and execute it as a command so we tend to make our interfaces around that concept.

      Want a menu? just type it

      It's an extremely powerful approach and one that I just couldn't let go of.

      Wily is the nearest example on X and 9menu rules hard.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    4. Re:Windows != standard by Trejkaz · · Score: 1

      Wily is short for (Un)wi(e)l(d)y. Or at least that's the way it presents itself. If I wanted to take longer to write a program I would use C.

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
    5. Re:Windows != standard by DrSkwid · · Score: 1

      oh well, shame you didn't persevere, it's not that hard

      mouse chording is a boon

      go back to vi :)

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    6. Re:Windows != standard by Trejkaz · · Score: 1

      I'm sure there aren't too many chords you can get out of three buttons anyway.

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
    7. Re:Windows != standard by DrSkwid · · Score: 1

      1-2 cut
      1-3 paste

      doesn't sound much but it speeds up editing

      plan proper has a free form terminal with a command line at the bottom

      you can edit text that is on screen just like a text editor and then 'send' it to execute as is or 'plumb' it to execute based on your regular expression rules (i.e. select the text 'http://images.slashdot.org/topics/topicslashdot.g if' and plumbing it will download the image and open it in a new window)

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    8. Re:Windows != standard by spitzak · · Score: 1

      No, Qt does not use the Windows Win32 widgets. It uses GDI32 to draw things, which is equivalent to using Xlib on Linux.

      Next time before you post, check your facts, so you won't look like an idiot.

      There are other widget kits that run on Windows: fltk, fox, Xt. And every 3D modelling system (Houdini, Blender, Maya, etc) uses their own toolkit. Also games seem to be quite popular and they don't use the Win32 widgets either.

    9. Re:Windows != standard by Trejkaz · · Score: 1

      If Qt doesn't use Windows' toolkit, then why does my Windows theme apply to Qt applications? Huh?

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
    10. Re:Windows != standard by spitzak · · Score: 1

      Because they are calling things like SystemParametersInfo() and GetSysColor() so they can draw their widgets the same. They may also be calling the "draw a button box" call (I don't know what it is called).

  161. One way to unify... by Trejkaz · · Score: 1

    You know what would be awesome:

    An implementation of Gtk+ in Qt, and an implementation of Qt in Gtk+.

    Then you could claim that it doesn't matter which one you use, it will integrate 'well enough' with whatever desktop it's running on.

    --
    Karma: It's all a bunch of tree-huggin' hippy crap!
    1. Re:One way to unify... by Anonymous Coward · · Score: 0

      >An implementation of Gtk+ in Qt, and an >implementation of Qt in Gtk+.

      Isn't gtk more low-level, so it would be impossible to implement it using qt?

  162. Re:why ignore the obvious solution? KDE only! by Elektroschock · · Score: 1

    So what is wrong with a gpled qt used for the KDe librarys? what could happen?

  163. UserLinux or HackerLinux? KDE or Gnome? by Anonymous Coward · · Score: 0

    Let's pick a name and stick to the premise.. KDE for "USER"Linux, Gnome for "HACKER"Linux. HackerLinux is done btw, pick any distro in existance.

  164. Re:What's the big deal by JanneM · · Score: 1

    And meanhwile, distros like Knoppix and Lindows do not include the Gnome libraries. I don't hear you complain about that...

    --
    Trust the Computer. The Computer is your friend.
  165. Re:What's the big deal by JanneM · · Score: 2

    What is becoming apparent is that a smallish, vocal fanboy group is prepared to tear any project apart if they do not include their favorite project. The people surrounding the KDE project is actually the largest reason I have never considered using it "for real".

    --
    Trust the Computer. The Computer is your friend.
  166. Just use MEPIS by Anonymous Coward · · Score: 1, Informative

    It comes configured the way most would need...uses kde and is debian -- how much better can you get?

    www.mepis.org

  167. Re:What's the big deal by be-fan · · Score: 1

    Knoppix and Lindows do not claim to be enterprise OSs. Knoppix is a LiveCD for god's sake! UserLinux, at least according to the stuff Perens said when announcing it, is supposed to be the banner under which Open Source will fight for the Enterprise market. And KDE is being left out of that fight.

    If the GNOME libraries were being left out of such an important project, you can bet the GNOME folks would be up in arms, as they should be, because that would be a stupid thing for the UserLinux developers to do.

    --
    A deep unwavering belief is a sure sign you're missing something...
  168. Re:What's the big deal by sydb · · Score: 1

    ISVs! UserLinux make the base distro, ISVs can add to it if desired. They can do the apt-get install, and pass that on to their customers.

    --
    Yours Sincerely, Michael.
  169. Qt is NOT a C++ Toolkit by rauhest · · Score: 1

    Although Qt is an excellent toolkit in many aspects, it is not a C++ toolkit.

    Qt sources have to be preprocessed before they can be passed through a standard C++ compiler, and the preprocessor has many limitations.

    However, it can't really serve as an argument in the GNOME vs KDE debate.

  170. Qt seems more expensive in India by tepples · · Score: 1

    Compared to the annual salaries of programmers(i.e. 50K+)

    The figure you quote is accurate only for the United States and possibly Canada and Western Europe. Mr. Perens wants UserLinux to become popular in places such as Vietnam and India where programming labor is cheaper than in the States, and a Qt license for each programmer working on in-house apps represents a much bigger chunk of the bottom line.

  171. No trade secrets in GPL'd programs by tepples · · Score: 1

    If you can't afford Qt, then you probably can't afford to pay programmers

    Labor doesn't cost the same in all countries.

    The vast majority of bussness do their coding in house and don't release it. They can still do this with the GPL'd QT

    Not if a program contains trade secrets. Once an in-house app is GPL'd, every employee has the right to leak it.

    1. Re:No trade secrets in GPL'd programs by Torne · · Score: 1

      Why would this be the case? Installing a piece of software that a company owns the copyright to, that happens to be GPLed, on all the machines owned by the company, is not distribution. The users do NOT own the copies, and thus, have not been granted the rights of the GPL. Nor has the GPL been violated; no distribution has taken place. The copyright holder is the only person with a copy.

      Oh, and hi tepples. =)

  172. Re:What's the big deal by puddpunk · · Score: 1
    Gnome is the better "supported" option because it doesn't require royalties for closed source development.

    In my opinion, GTK/GNOME is _less_ free because of the LGPL. The GPL was created so that the freedom goes where the software does, and it's not true with the LGPL.

    It seems that the Qt/KDE effort cannot win! First they got the rasberry because Qt wasn't licenced under a free licence, now that it is everyone complains when there is a penalty for developing closed source applications!

  173. GNU General Public Leak of trade secrets by Anonymous Coward · · Score: 0
  174. Am I Missing Something? by thelizman · · Score: 1

    Like, isn't KDE better in many respects? Most. Wait. Gnome sucks. Hey, I've got a great idea, why not make as many desktops as available as possible, and just select one default installed desktop.

    1. Re:Am I Missing Something? by BenjyD · · Score: 1

      Perens reasoning seems basically to be that, given limited developer and artist time, and a desire to simplify support issues, having only one possible GUI in a distro is better, even if that GUI isn't everybody's perfect choice.

      Of course, this is only in the special case of UserLinux, which I doubt very many linuxgeeks will use.

  175. Relationship with Canopy: Less than 6% by tepples · · Score: 2, Interesting

    SCO's bosses at Canopy controls Trolltech

    Not according to Trolltech's investor list, which claims that the employees own nearly two-thirds of the stock. Even Borland owns more than Canopy and SCO, which put together control less than 6 percent of Trolltech.

    1. Re:Relationship with Canopy: Less than 6% by FreeUser · · Score: 3, Interesting

      Not according to Trolltech's investor list, which claims that the employees own nearly two-thirds of the stock. Even Borland owns more than Canopy and SCO, which put together control less than 6 percent of Trolltech.

      So, to reiterate the parent poster's question: what the fuck is Darl McBride's boss doing on the board of directors? As one who has defended KDE and spoken rather vehemently against UserLinux's exclusion of arguably the most mature Linux desktop in previous stories on this subject, I'd really like to know. Frankly, any business with a relationship with Canopy is open to serious question, given SCO's recent behavior. Guilt by association may not be popular or politically correct, but in the business world, where almost all backroom deals are run on personal contacts, suspicion by association is very warrented.

      --
      The Future of Human Evolution: Autonomy
  176. IT doesn't want Joe Employee installing viru^Wapps by tepples · · Score: 1

    it's a showstopper when joe user wants to install software

    Tough cookies. The IT department would rather not let employees install any unauthorized program at all. The administrator has disabled execution of binaries in /home/ except for users in the devel group. If an employee wants a Qt app, the usual channels for a New Program Installation proposal to the IT department remain open.

  177. absurd sensationalism by aminorex · · Score: 1

    controversy for the sake of controversy.
    there will be gnome on userlinux, if ever
    there is a userlinux, and there will also
    be kde on userlinux, likewise. i'd like to
    see mr perens try to prevent a fork of a
    distro that intentionally excluded half of
    the highest productivity end=user programs
    available for the platform. heh.

    --
    -I like my women like I like my tea: green-
  178. MySQL vs. PostgreSQL by Markus+Registrada · · Score: 2, Interesting
    The Gnome and KDE toolkits are about equivalent, so the choice amounts to a coin flip, licensing issues aside.

    Of greater moment is the choice of database library. PostgreSQL is enormously more complete and standard-compliant than MySQL, and (for years, now) faster, and is committed to the more liberal license that Bruce has demanded. MySQL (like KDE) is straight GPL in release 4.x, and lacks many important enterprise features.

    Odd, isn't it, that we don't see flame wars over the database? Probably they will switch quietly to PostgreSQL once they get around to the matter, and nobody will make a fuss.

  179. bingo by Anonymous Coward · · Score: 0

    Ralph Yarro thanks you.

  180. News Flash - UserLinux to use MS Windows kernel by conradp · · Score: 2, Funny

    This just in: Bruce Perens has decided that UserLinux will be built on top of Microsoft Windows instead of using the traditional Linux kernel. Perens, famed founder and leader of the Debian project, said yesterday: "Just like Qt, the Linux kernel is released under a GPL license, which requires developers modifying it to release their source code under the GPL. This prevents commercial solution developers from creating closed-source, proprietery kernel modifications, which would inhibit the adoption of UserLinux."

    Perens reportedly approached Linux founder Linus Torvalds to request that he change the Linux kernel license from GPL to LGPL, in order to be more consistent with the GNOME license. Mr. Torvalds apparently refused, at which time Perens managed to negotiate favorable kernel licensing terms from Microsoft.

    Mr. Perens had no comment in response to the claim by a spokesperson for TrollTech, the Norway-based company that develops Qt, that their code was actually "freer than Linux", since unlike the Linux kernel, developers can choose to license thier applications under either the GPL or TrollTech's proprietary license that allows close-source development.

    --
    "To be absolutely certain about something, one must know everything or nothing about it." -- Olin Miller
  181. Please Bruce, only include Emacs!!!! by bbh · · Score: 1

    That would be really impressive. It is the only thing I can think of that would annoy the Linux community even further! Do it!

  182. you don't understand how companies work by penguin7of9 · · Score: 3, Insightful

    Having worked for a bunch of companies, I can tell you that's not the way things work.

    A lot of corporate development is in-house. The Troll Tech license and license fees mattter a great deal for that. They matter not only because of the short-term cost, but they also matter because of the long-term control Troll Tech gets over commercial applications.

    In fact, Troll Tech's control is a problem even for "free software folks", because the design and direction of Qt is ultimately driven by Troll Tech's commercial interests. And you can't weasel your way out of that fact by arguing that if Troll Tech starts going down the wrong path, people can just fork the GPL'ed version of Qt because the very reason for choosing Qt is KDE's assertion that no open source project could deliver a toolkit of comparable quality.

    In fact, another strike against KDE and Qt is the fact that KDE already screwed up big time once. Far from being the result of a careful plan, the current dual-licensing scheme for Qt is the result of Troll Tech averting disaster by changing their license after KDE went on for a couple of years merrily developing software under an open source license incompatible with the QPL. The impression one gets as an outside is that KDE doesn't know what the hell they are doing with licenses. And it doesn't help either that Troll Tech is clearly responsible for killing the Harmony Project, an attempt to develop a more liberally licensed Qt-compatible license, because it would cut into their sales. Neither of those is a big recommendation for KDE or Qt.

    And, in fact, some of those in-house applications later become open source. But the decision to open source is not something companies make at the start of a project--it takes time to deal with lawyers and business people. With Qt, we'd have had to pay Troll Tech for commercial development licenses just so that we could start developing only to have wasted that money later when we get the corporate OK to open source.

    So, why is it that, so far, there are more commercial Qt applications than Gtk+ applications? Well, first of all, I'm not sure that's true--where is the data? Secondly, the Qt applications I have seen are usually from companies like Adobe, whose Linux offerings basically suck.

    But, in any case, until maybe last year, Gtk+ really was behind Qt (after all, it started later as well), but it has now caught up. But before then, there were already plenty of commercial projects in toolkits like Tcl/Tk and wxWindows, both of which have even more liberal licenses than Gtk+.

    In my own experience, Qt's license is deeply harmful to Qt's acceptance for commercial projects: many commercial developers just don't want that sort of dependence on a software vendor, let alone a little company from Norway, even if the money didn't matter. But the money does matter. And Qt's license is also harmful to Qt's use for open source projects.

  183. What's there to debate? Live with your choices. by penguin7of9 · · Score: 1

    If you don't like Perens's choice, just don't use or support UserLinux. Perens doesn't like KDE's choice (of toolkit), so that's why he isn't using it in the project he is putting together.

    KDE made two bets a few years ago: (1) that making a deal with a commercial company was necessary in order to deliver a high quality toolkit, and (2) that a dual-licensed toolkit wouldn't matter to open source developers or commercial acceptance. Looks like KDE is losing both bets: Gtk+ has more than caught up with Qt technically, and choices by open source entities like the FSF and Perens, and choices by companies like Sun, IBM, and HP (of Gnome) indicate that Qt's license does affect its acceptance.

    KDE made its choice and its developers and advocates should accept the consequences.

  184. Re:What's the big deal by pyros · · Score: 1
    In my opinion, GTK/GNOME is _less_ free because of the LGPL. The GPL was created so that the freedom goes where the software does, and it's not true with the LGPL.


    The great irony of UserLinux in this respect is that LGPL gives more freedom to the producer than the consumer (the User). The LGPL gives software producers freedom to use libraries in conjunction with a closed-source application and the GPL does not. The extra freedoms of the LGPL are realised by the companies writing software for UserLinux, not the people using it. This is what Bruce Perens has in mind. He wants to produce a distribution that encourages companies to release software.

  185. "Popularity"? by khasim · · Score: 3, Insightful

    This isn't high school. People will use KDE as long as KDE is the best solution for them.

    Rather than worrying about losing popularity, try focusing on making KDE the best it can be.

    Like I pointed out, installing KDE on UserLinux should be a single command.

    apt-get install kde

    As for the developers, I don't see what you're worried about. They are the ones making KDE into what they want it to be. Why would they abandon their project?

    And the commercial support? Well, only time will tell for that. But the commercial support is usually pretty easy to predict. Give them the best environment for their products and they'll move to it.

    If you cannot make KDE a better choice for end users, developers and commercial interests, then why not let those groups make their OWN CHOICE about what to use, develop and develop for?

    Open Source is not about lock-in.

  186. Bring back the Harmony project by Anonymous Coward · · Score: 0

    Before Qt was dual-licensed, GNU had a project called Harmony to create a GPL clone of Qt.

    Anyone remember that project? How far did it get?

  187. Set my toolkit free! by Anonymous Coward · · Score: 0

    If the KDE group and Trolltech had allowed Harmony to go through. We wouldn't be having this discussion. The plain and simple fact is that the KDE group made a decision to use a nonfree (at the time) toolkit. Pragmatic in one way, but not so when fully thought out, as all the discussions have shown. The Gnome group however chose to be pragmatic (use the GTK toolkit) and thought things through. Now here we are, first the toolkit, then Harmony, next Bluecurve, and presently userlinux. KDE can not shake the consequences of their initial decision even though their edifice is GPL. And here we see KDE fighting tooth and nail defending a bad decision, pragmatic (like binary drivers are pragmatic), but still bad, when one looks at the big picture. Maybe it will finally all work out, but some of the KDE groups antics have generated bad blood, and a poor opinion of them overall, even though a great many don't deserve it. Here's to hoping it all works out.

    1. Re:Set my toolkit free! by Simple-Simmian · · Score: 1

      The only thing it can't shake is the fanboys who would rather use a broken GNOME whining about QT.
      The majority of GUI desktops under Linux use KDE.
      Even under Debain
      Get over it fanboys.
      If UserLinux wants to use GNOME fine.
      It's bound to fail then.

      --
      If you don't like what I write don't be a CS and mod it down. Refute it.
      Yea I can't spell. So what is your point?
    2. Re:Set my toolkit free! by Anonymous Coward · · Score: 0

      The toolkit IS free! Ever heard of Qt/Free? If people are too dumb to read the licence, then they should spend time to learn how to read!

  188. No one understands Bruce's goal by benjamindees · · Score: 1, Interesting

    Because it doesn't make sense. It sounds like he's more interested in proprietary, commercial development than Open Source or Free Software, or even, (god forbid) choosing the best software for the job.

    --
    "I assumed blithely that there were no elves out there in the darkness"
  189. Re:IT doesn't want Joe Employee installing viru^Wa by salesgeek · · Score: 1

    usual channels for a New Program Installation proposal to the IT department remain open.

    Tell that to the CEO or SVP Finance. Some users are more equal than others.

    --
    -- $G
  190. VPs' "channels" by tepples · · Score: 1

    You mean like the following?

    Executive, in instant message to IT: "Would you please install kdinkylittleapp on my machine?"

    IT tech: "I'll get right on it."

    Executive notices activity on her Alienware machine's hard drive as IT tech logs in through SSH and apt-get installs the app.

    IT tech: "Done."

    Though it's rather the "short form," it's still a "request" through a "channel." Or if that isn't enough, and the VPs are knowledgeable enough not to intercourse up their computers, just make the topsuits group a member of the devel group to inherit its privileges.

  191. Re:Is "proprietory-friendly license" so important by benjamindees · · Score: 1

    Yeah, no one is seriously considering Firebird at this point; but, like KDE, it would be folly to completely ignore it.

    *When* Firebird reaches a stable state, it will be a force to be reckoned with. Who knows, UserLinux may even still be vaporware by then. It would be dumb to choose something else now only to have everyone demand Firebird a year from now.

    --
    "I assumed blithely that there were no elves out there in the darkness"
  192. Xwindows should be abandoned by mrnick · · Score: 1

    Who cares? KDE stinks, GNOME stinks. The reason is that XWindows STINKS. The only viable GUI running on a UNIX based system that I have seen is Mac OS X. Thank god they did not build their GUI on top of XWindows. IMHO the only way any GUI has a chance is the project is started from scratch rather than relying on something that I consider inheriently flawed (XWindows). Neither KDE or GNOME are GUIs they are Window managers and like Stephen King said in Christine "You can't polish a turd".

    Nick Powers

    --

    Encryption: I may not agree with what you say, but I will defend your right to encrypt it...
  193. Re:What's there to debate? Live with your choices. by Anonymous Coward · · Score: 0
    Have yopu been smoking that SCO ceack. GTK is still poopy. Gnome is still poopy. GNOME is the main reason RedHat sucks on the desktop.

    GNOME apps rock, the desktop east poop.

  194. Stop wining by Anonymous Coward · · Score: 0

    KDE was a mistake from day one, get over it people.

  195. Only /. thinks this is the case by Ars-Fartsica · · Score: 0, Flamebait
    Maybe people here are just too afraid to admit that GNOME has better apps and is not ugly as shit.

    It is the APPS remember? How much time do you spend fiddling with crap in your UI??? I spend my time in applications, not preferences dialogs.

  196. Whats missing form the picture. by Simple-Simmian · · Score: 1
    I don't care if "business" ever adopts Linux. It would be nice but it's playing well enough for me for 99.9 of all my computing needs.

    UserLinux needs for a single DE for it to be "sold" are fine and dandy. Most people are not going to develop for it. Lots of Linux folks don't give a damm if Linux gets anymore uptake than it has today.

    As for me I am going to continue to run GTK apps on my KDE because Gnome sucks goat balls.

    The bottom line is this effects hardly anyone but a bunch of fanboys and zealots.
    All this agaitation is pissing me off though and my feelings for Bruce Perins have fallen to just above Darl Mcbride's right now because we don't need people sturing up shit.
    Thanks Bruce for seeding a shit storm when you didn't really have to.

    --
    If you don't like what I write don't be a CS and mod it down. Refute it.
    Yea I can't spell. So what is your point?
  197. Re: why gnome over kde? by Anonymous Coward · · Score: 0

    It seems you're reaching for the idea of Buridan's Ass

  198. Re:What's the big deal by fault0 · · Score: 1

    > What is becoming apparent is that a smallish, vocal fanboy group is prepared to tear any project apart if they do not include their favorite project.

    Indeed.. I think Bruce Perens could have avoided a lot of trouble by saying that from the onset that no GUI based on GPL tools like Qt could be used. That would have ruled out KDE from the onset.

    Instead, he announced it and he wanted people's opinions on a GUI for it. I guess now it's pretty obvious what he wanted. :)

  199. Re:What's the big deal by Anonymous Coward · · Score: 0

    > Look how people prefer Firebird over Mozilla.

    Really? are there stats on this?

  200. evilwm rocks by Anonymous Coward · · Score: 0

    Oh yeah. Google for evilwm. I use it exclusively.

  201. No, he would not. by Kjella · · Score: 2, Insightful

    So, let me get this straight - he wants to discourage the use of GPL'd code in UserLinux in order to have businesses create proprietary applications that can not in turn be included into UserLinux because they will not be free?

    Sounds like an interesting one-sided ecosystem.

    If he took this commercial-friendly argument to its logical conclusion he would dump the GPL'd Linux from UserLinux in favour of BSD. But then it would not be much of a UserLinux, would it?


    The basic argument is that a GUI toolkit may be a very unimportant part of the application - applications companies would simply not GPL because their apps do damn smart, trade secret stuff and they'd want it closed. And yet, these programs will need a GUI - even if it's just a bunch of plain objects (buttons, checkboxes, radioboxes, text labels etc.) Don't think of a yet another mp3 player, think projects where 98% of the work is non-GUI.

    As such, they don't have a problem with contributing to Gnome, or to the Linux kernel - that's just improving their toolbox. What they want to keep out and proprietary is their own code, interfacing with the toolkit. If you want a similar example, take OS X. They've been voluntarily contributing back to the underlying system, and those using Gnome (and must do so according to the LGPL) are unlikely to have any problem with doing that either.

    That being said, I don't think the QT licence is that bad and expensive for a large company. As long as those licenced for QT get to develop with it a lot. It's for the small companies where the QT guy is also the "everything else" guy, that it gets real expensive. And I'd really not want to try a start-up of some small-time shareware using QT. Maybe, if there is a proprietary culture, the devs will go to QT because "Why should these companies profit from MY work?" As of yet though, I don't really see many proprietary Gnome-based apps, so no one is getting an itch from it. But it'll come if the big money starts flowing...

    Kjella

    --
    Live today, because you never know what tomorrow brings
  202. just fork it by Anonymous Coward · · Score: 0

    Why waste energy in political issues, just create new "userlinux" project whit focus on KDE and stop wasting your time arguing.

    KDE proposal was excelent and i really really would like to see it happen.

  203. Re:What's there to debate? Live with your choices. by Anonymous Coward · · Score: 0

    I don't know what the technical term "poopy" is supposed to mean. Gnome is fast enough on modern hardware (even unaccelerated), easy to use, robust, and it looks nice. KDE is no better, and some would argue it has already fallen behind.

    But it really doesn't matter whether KDE is still slightly better or worse--it's license is such a huge obstacle that KDE is doomed.

  204. Re:They should go with -XPDE- by Seraphim_72 · · Score: 1


    Hell, if they are going after the M$ crowd, make the thing look exactly like windows.

    Sera

    --
    Slashdot, where armchair scientists get shouted down and armchair theologians get modded up.
  205. Re:What's the big deal by Anonymous Coward · · Score: 1, Insightful

    Gnome is the better "supported" option because it doesn't require royalties for closed source development. This matters in countries where you can buy 3 developer months for single license of Qt (and for 3 developers, you need 3 licenses).

    If that is so, how come there aren't any commercial GTK-apps?

    Having a real company behind Qt that can provide support and such, is actually an advantage for KDE. Qt is also much nicer to program with, is cross-platform, etc. Sure you have to pay for it, but it's only a small fraction of the cost of a whole project, and it saves manpower because it's such a nice tool to work with.

    And then there's the moral issue: because GTK is LGPL, it's practically preventing the use of the GPL for commercial programs. Isn't free software what many have been fighting for? Why not choose a toolkit that has a cost-advantage when used in a GPL-manner then?

  206. Re:What's the big deal by haggar · · Score: 1

    This is our experience with RHEL and KDE: since we plan to use Linux in rollouts of our shrink-wrapped software, for telecoms, we need to have top QA and do lots of testing in the preparation phase.

    One of the many installation tests was to use the default installation procedure in RHEL, and then see what we get. OK, installed Gnome by default. Then we tried to install KDE. Cant do it! Sounds incredible? We thought that, too. Since we forked 1200 Euros for RHEL, we thought we better start using that golden support (I call it "golden" as it costs an arm and a leg). Believe it or not, after two weeks of wrangling with RedHat support engineers, going back and forth, the case was NOT solved!!

    Our dissatisfaction with Redhat support has been quite big, as a consequence of this episode, and RedHat did NOT get into our product solution.

    I work in a large european mobile phone company, and we take our business seriously. RedHat didn't. I guess keeping KDE out must be some sort of strategic goal at RedHat, otherwise I totally don't understand their behaviour.

    Incidently, I even offered to explain to a RedHat employee why they didn't get in, and guess what, he wasnt even curious!

    --
    Sigged!
  207. Re:What's the big deal by luisdom · · Score: 1
    Ok, name me 3 pieces of commercial software more complicated than solitaire made with gtk.

    If anybody can fill these 3 gaps, I'll start considering that argument of "gtk doesn't require royalties for closed source development", despite the fact that you have to use bindings to do OO programming with gtk.
  208. Re:What's the big deal by luisdom · · Score: 1

    Or is it? Look at what TrollTech say here - TT don't want you using Free Qt on inhouse projects, but the GPL says you can. This makes me distrust TrollTech.
    Yeah! they have a record of pissing off the Open Source Community. Come on, be kind. Mail them complaining about that, maybe they correct the FAQ. After all, it's their policy that if you take it for free, you should pay the community back.
    If being the default desktop of UserLinux is so important to KDE, why don't they re-implement their desktop ontop of an LGLP'd toolkit?
    Pleaaaase. Can you spell demagogy?

  209. Re:What's the big deal by Anonymous Coward · · Score: 0

    If you don't like the distribution, don't use it. Simple as that.

    FFS, how many people are going to miss the point? UserLinux is about producing a standard operating system for businesses. To do things like standardise operating system components because it's easier to target a single platform than the constantly moving target that is GNU/Linux.

    Keeping both GNOME and KDE libraries in the system will mean more maintenance work. However, taking KDE out means that application vendors will not be able to rely on KDE, Qt or anything of that nature.

    In essence, UserLinux is shutting Qt and KDE out of the market. It wouldn't be so bad, but for three glaring problems:

    1. UserLinux is backed by a number of large companies, and has a lot of momentum behind it. It could actually succeed in becoming the "standard" GNU/Linux distribution for businesses.
    2. The Qt and KDE libraries are so much better than GTK+ and GNOME it's laughable. If you don't believe me, go ahead and get stuck into developing a GUI application yourself.
    3. The "needs a commercial license" argument is a flimsy excuse. Trolltech's fees for closed-source developers form a ludicrously small part of the cost of bringing a product to market. Qt has far more closed-source users than GTK+ despite the fact that the license is more closed-source unfriendly.

    But hey, as long as the end-users can install their own desktop, everything's okay, right? Oh wait - this is a distribution aimed at corporate users - so the end-users won't be installing their own software.

  210. The hell it doesn't! by TrentC · · Score: 1

    How many times does this need to be pointed out? QT/KDE does NOT require the purchase of a licence to be used in developing commercial products!!

    Then why does their Qt Commercial Licensing page state that you should "[u]se the Qt Commercial License to: 1)Build commercial software. 2)Build software that is not sold, but that advances the business goals of a commercial enterprise"?

    I know as well as you do that "commercial software" does not equal "closed-source software", but that distinction seems to be lost on TrollTech ; either that or they need to choose their wording more carefully, as they seem to use "commercial" and "non-free" interchangably.

    Read the QT FAQ. You can freely (free as in speech and as in beer) develop software for whatever purpose you desire using QT, including commercial purposes.

    Not true; if you do, you're apparently in violation of the Qt Free Edition's license. From that selfsame FAQ:

    Can we use the Free Edition while developing our non-free application and then purchase commercial licenses when we start to sell it?

    No: our commercial license agreements only apply to software that was developed with Qt under the agreement. They do not apply to code that was developed with the Qt Free Edition prior to the agreement. [Emphasis mine] Any software developed with Qt without a commercial license agreement must be released as free/open source software.

    Using the Free Edition, can I make non-free software for internal use in my company/organization?

    No. Software developed with the Free Edition is always free software, i.e. it can only be distributed under a free software license. In particular, all the source code for all the modules your software is based on, regardless of whether they have been written by you or by others, must be free software. This is part of our commitment to the free software community, and enables those who contribute to the free software pool to do so without paying license fees. Although it is possible to write free software for internal use, it is difficult to ensure that such software is used and distributed legally. For example, if your free software requires any modules that impose conditions on you that contradict the conditions of the GNU GPL, including, but not limited to, software patents, commercial license agreements, copyrighted interface definitions or any sort of non-disclosure agreement, then you cannot distribute it at all; hence it cannot be given to consultants, employees for their personal computers, subsidiaries, other divisions, or even to new owners. [Emphasis mine] Consequently we recommend using commercial licenses for all internal software development.

    And this barely touches on the fact that Qt Free Edition is not available for Windows or Mac OS X, so my "freedom" in developing software is limited to X11-based platforms; I'm supposed to pay $1550 for the privilege of developing Qt-based applications for Mac and Windows users, regardless of the license I plan to distribute it under.

    It is certainly TrollTech's right to license their software however they see fit; however, they don't get to charge developers of commercial software for their toolkit and then complain about not being included in a distribution that seeks to avoid those costs.

    Jay (=

  211. Wait for it: by Anonymous Coward · · Score: 0

    KuserLinux