Slashdot Mirror


UserLinux May Go Without KDE

Anonymous BillyGoat writes "For the past few days, there has been considerable debate at the UserLinux mailing list about the (proposed) non-inclusion of KDE in the distro. The KDE developers have written a proposal opposing the decision to go with GNOME as the sole UserLinux GUI, while Bruce Perens has posted a response."

964 comments

  1. KDE is not to be ignored by Erioll · · Score: 5, Insightful

    KDE is still one of the most-used desktop environments around. Ignoring KDE in favor of GNOME would be like only including VI and not Emacs (or Emacs and not VI), and forcing all users to use one.

    This is a mistake if they don't include both.

    Erioll

    1. Re:KDE is not to be ignored by daeley · · Score: 5, Insightful

      Not exactly the same thing, as including both of those doesn't require anywhere near the amount of effort as supporting two development kits...at least, that's the argument Perens seems to be making.

      --
      I watched C-beams glitter in the dark near the Tannhauser gate.
    2. Re:KDE is not to be ignored by mAIsE · · Score: 4, Funny

      Yes but we all know VI is far superior to EMACS !!

      --------------

      There are 10 kinds of people in the world; those who understand binary, and those who don't

    3. Re:KDE is not to be ignored by Prowl · · Score: 5, Insightful

      i disagree

      UserLinux is about a stable, usable business desktop (AFAIK). it is *not* about choice. The are plenty of other distros that cater for choice.

      Including both or more would dilute development efforts, not to mention confuse Harry Homeowner, who is only interested in writing docs, and playing MP3s.

      This definitely a good thing.

      --
      That man tried to kill mah Daddy
    4. Re:KDE is not to be ignored by Coward+the+Anonymous · · Score: 5, Insightful

      UserLinux is for corporate desktops, not home users. Corporate desktop users don't get choice, everything is set up and locked down by the admin. This gives the admin one less choice to make.

      --
      -- Jason
    5. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      UserLinux is about a stable, usable business desktop (AFAIK).

      So why choose Gnome over KDE, which is more stable and more usable?</troll>

      If it's stability we're after, I'd have thought something like Blackbox would be infinitely superior anyway...

      This definitely a good thing.

      Well done, you just identified yourself as a Gnome user.

    6. Re:KDE is not to be ignored by NanoGator · · Score: 1

      "Yes but we all know VI is far superior to EMACS !!"

      Okay guys, I'm really sorry for asking such a dumb question, but I'm not very deep in the Linux world. What is EMACS, and why are jokes like these commonly made about it?

      --
      "Derp de derp."
    7. Re:KDE is not to be ignored by KarmaPolice · · Score: 5, Insightful

      The problem isn't really supporting two platforms. Packages are being created anyway. The problem is that the UserLinux people wants companies to use it and the "selling" argument will be that is't ONE common platform that they can program their own applications for.

      Imagine the resources for programming and testing for both KDE, Gnome and many more platforms. One programmer can only know so many platforms. The world sometimes is easier with fewer choises...

    8. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      everything is set up and locked down by the admin

      In which case KDE should be the only desktop shipped, as it has a framework for doing exactly that - locking down the desktop.
      see http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdelibs/k decore/README.kiosk?rev=HEAD

    9. Re:KDE is not to be ignored by satanami69 · · Score: 4, Funny

      Emacs is an early attempt to mimic yacc. It has evolved, trapper keeper style, to include its own kernel. Far beyond the scope of the GNU/Hello World mail client, Emacs can easily be scripted so common tasks can be repeated.

      Also a simple editor such as ee, or aee, can suffice in most cases, Emacs is able to live in a symbiotic relationship with the user. Using Emacs over Vi has been suggested as the start of the next Great war by future historians. Also, it will be resolved after Emacs opens a connection through the metaverse where Emacs includes :q!

      --
      I really hate Dan Patrick.
    10. Re:KDE is not to be ignored by TrekCycling · · Score: 1, Troll

      Bingo. I may be biased as a Gnome user that appreciates that Gnome just works, doesn't crash (admit it, if you've used KDE or QT apps you've seen the crashes, I have) and is simple. It's a window manager, not a platform. Linux is the platform. The apps are what I use. I just want my desktop to manage files a little, let me organize some folders and otherwise just manage windows. Gnome does this well and keeps getting faster and better at it. Gnome 2.4 rocks. Not everyone wants all the options KDE provides. There are plenty of distros that offer both.

    11. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      EMACS is a text editor that has a built-in LISP interpreter. Most of the functions of EMACS are actualy written in EMACS LISP, and there are many add ons, such as games, debugging environments, email programs and so on that work inside EMACS.

      Its a difference of quick, simple, clean but limited to built-in functions vs unlimited, extensible but complex and somewhat bloated. Its the classic OSS flamewar, going since the early 1980s.

    12. Re:KDE is not to be ignored by rmull · · Score: 1

      Extensible Macros. Duh.

      http://www.google.com

      --
      See you, space cowboy...
    13. Re:KDE is not to be ignored by _fuzz_ · · Score: 4, Insightful

      Windows is still one of the most-used desktop environments around. Ignoring Windows in favor of KDE/GNOME would be like only including VI and not Emacs (or Emacs and not VI), and forcing all users to use one.

      Just because something is popular doesn't mean it meets the goals of every project. If UserLinux is about creating the most usable Linux distro, then it makes sense that they would want to provide a single, consistent interface. That doesn't make KDE bad.

      --
      47% of all statistics are made up on the spot.
    14. Re:KDE is not to be ignored by Apreche · · Score: 3, Insightful

      If it's about a stable usable business desktop then the best option would be something like xfce4. Lite, simple, lacking in crazy features, rock solid. Just put a bunch of big ass icons in the panel.

      Word Processor, Spreadsheet, E-mail, Web, XMMS, etc. etc.

      It would do everything you need to do at work and nothing else.

      --
      The GeekNights podcast is going strong. Listen!
    15. Re:KDE is not to be ignored by NDPTAL85 · · Score: 0

      Your comment shows you just don't get it. Did you even read where the response by Bruce Perense states that its too "expensive" to maintain development of both platforms?

      I am not trying to be condescending for once but in the *real world* just getting open source in the corporate door is hard enough. Trying to convince your bosses that you have to maintain compliance with two functionally identicall GUI environments will not go over very well. One or the other, pick one and choose. Open Source and Free Software has crept out of the programmers basement apartments and into a very accountable environment.

      BTW, chosing Vi or EMACS WOULD be just fine. They're both text editors. They both edit text. If it works you use it and don't use anything else until it stops working. No money or time for further dicking around.

      --
      Mac OS X and Windows XP working side by side to fight back the night.
    16. Re:KDE is not to be ignored by AaronGTurner · · Score: 2, Informative

      KDE and GNOME are now mature enough that they can both do the job very well, and are sufficiently configurable that a company can meld them to their preferred look and feel. At work GNOME is the default, at home I've tended to use KDE. I used to prefer KDE, but now I am pretty agnostic about the desktops. Nothing clunky like CDE, please!

      What is needed is that whichever desktop be robust - e.g. the clipboard always works.

      GNOME does have an advantage in some decent industry backing. That could be converted into extra coding effort, or quality assurance. That final polish could make a lot of difference, and if GNOME is the way to go to get that polish, then go with GNOME.

      Some KDE apps are nice, though - I wouldn't want to lose those - e.g. kdebug, k3b, which I love

    17. Re:KDE is not to be ignored by geekd · · Score: 1, Flamebait

      I use KDE all day, every day, for my job. I see no crashes. Ever.

      Why don't you go make up lies about my mother, while you are at it?

    18. Re:KDE is not to be ignored by cyb97 · · Score: 1

      But could you get that dimwit blonde in reception just as "productive" using XFCE4 as she would be using KDE/Gnome/Windows?

    19. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      First of all, I agree with you, but I don't really give a fuck about Harry Homeowner who doesn't bother to learn shit about what he is doing on the computer. I do prefer GNOME over KDE, but I don't think we need to cater towards grandmothers. If they bother to learn how to use the computer, then too bad.

    20. Re:KDE is not to be ignored by be-fan · · Score: 4, Insightful

      That doesn't make KDE bad.
      >>>>>>>>>>>>&g t;
      No, but along with RedHat and Novell adopting GNOME, it might just mean that GNOME "wins" by virtue of commercial forces rather than technical ones.

      --
      A deep unwavering belief is a sure sign you're missing something...
    21. Re:KDE is not to be ignored by shaitand · · Score: 1

      "usable business desktop"

      stability is not the only qualification.

    22. Re:KDE is not to be ignored by big+tex · · Score: 1

      Then ignore the other options, and go on about your way.
      Very important fact: Having choice does not mean having to choose.

      KDE works out of the box, so if you don't want to change anything, don't. however, if you do you want to change things, you can.

      See, you also just want a window manager. I want an enviroment, something that lets me do more than move some folders.

      --
      I think I need a new sig here.
    23. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      I downloaded Slackware 8.1 in bits and pieces, and decided to include KDE 3.0 and FVWM, but not Gnome, yet. KDE was a little easier to download, and has a lot of stuff. I like KDE, and if I feel that it's too heavy for my box, I have FVWM. It's not too heavy, Slackware does everything right, apparently, and I have no problem at all with KDE. I'd rather have KDE, because I like to show it off, compared to XP's nice interface.

    24. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      The only crashes I've seen with KDE on linux in the past while have been as a result of redhat's recent fucked up butchery of KDE. Get non-redhat "real" KDE before blaming KDE if you are having crash problems on redhat.

    25. Re:KDE is not to be ignored by Obfuscant · · Score: 1
      UserLinux is about a stable, usable business desktop (AFAIK). it is *not* about choice.

      Yes, it is about choice, and UserLinux ought not be making the choice of what desktop a person uses. If we want "no choice", we can use Windows.

      Including both or more would dilute development efforts,

      Nonsense. UserLinux is not about development, it is about users. Users having a choice is a good thing. Putting both in a distribution that is not intended for developers doesn't dilute development.

      The biggest complaint I have about RedHat is BlueCurve. I want to be able to use KDE on all of the systems I have, I don't want to have to deal with a handful of different desktops depending on which system I am using at the moment. I'm already dealing with Sun's CDE, SGI's 4Wmd (or whatever it's called) and KDE. I don't need more, and RedHat sucks for deciding for me that I don't want KDE.

    26. Re:KDE is not to be ignored by cymen · · Score: 1

      I haven't seen crashes using KDE or QT applications.

    27. Re:KDE is not to be ignored by pivo · · Score: 1

      My experience is just the opposite. GNOME seems buggy and not well thought out. KDE seems very polished and stable. Plus, I vastly prefer coding to KDE/Qt's API. GNOME's API strikes me as a kludge.

      I think such an obviously devisive decision to feature one desktop over the other is akin to a distribution that ships ony emacs or only vi. (Though emacs rules :)

    28. Re:KDE is not to be ignored by ziggyboy · · Score: 1

      Everyone is correct in saying that Linux is all about choice and freedom. Well, it was UserLinux's choice not to include KDE. If you really want to use KDE, then don't use UserLinux. It's as simple as that.

    29. Re:KDE is not to be ignored by KewlPC · · Score: 5, Insightful

      The thing is, you don't have to test for KDE and GNOME. If you write a GNOME program, test it with GNOME, and it will always work with KDE since if you run it from KDE it will still use the GNOME libraries. The same is true for the other way around.

      This is really just a, "We don't like KDE, so we've decided that nobody who uses our distro will use it."

      I personally don't like GNOME very much. I think QT is a better toolkit than GTK. GTK has way too many problems and limitations (like the complete inability to do MDI-style interfaces), and its whole API is a quasi-documented mess. And from what I understand, the whole "Well GNOME is for C programmers and KDE is for C++ programmers" isn't true anymore, as there are bindings for both languages for both environments IIRC.

    30. Re:KDE is not to be ignored by damiam · · Score: 5, Informative
      Technically, Emacs is an interpreter for the LISP programming language, whose primary purpose is to implement a scriptable, extensible, flexible text editor. Emacs's ability to run arbitrary LISP scripts results in a kitchen-sink approach. It can do just about everything you'd ever want in a text editor, and a lot of things you wouldn't (like web browsing, Tetris, and psychoanalysis). Its main competetor in the world of arcane UNIX text-editors is vi, which is a much simpler (yet still quite powerful) editor designed to use as little bandwidth as possible (back in the days where you could often type faster than your console connection could keep up with).

      Both editors have been around forever, have a steep learning curve, and are supposed to be extraordinarily productivity-enhancing for those who invest the effort to master them. As with many other sets of competing projects (Linux/BSD, GNOME/KDE, OSX/Windows), they are both probably better classified as religions rather than software products, and are excellent material for flamewars.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    31. Re:KDE is not to be ignored by mangu · · Score: 3, Informative
      including both of those doesn't require anywhere near the amount of effort as supporting two development kits


      What I can't understand is that the development effort is *much* bigger for Gnome than for KDE. GUI toolkits is about the only place where, according to my experience, the OO overhead is justified. For me, the C vs. C++ debate ends when one considers Qt vs. Gtk.

    32. Re:KDE is not to be ignored by KewlPC · · Score: 1

      GNOME is not a window manager. In fact, GNOME seems to switch window managers with every release. Enlightenment, Sawfish, Metacity, etc.

      I use KDE 3.0.3 every day and it never crashes. I also care mostly about the apps: KMail for e-mail, Kate for writing code, KHexEdit, etc.

    33. Re:KDE is not to be ignored by paranerd · · Score: 1

      You got it all wrong. It's:

      VIle.

      :)

    34. Re:KDE is not to be ignored by Billly+Gates · · Score: 1, Flamebait
      Garbage the reason why Debain refused KDE is because RMS and other fanatics claimed QT which KDE is based on is not free enough.... even though it was opensourced and free as in beer.

      Many pharisee's still view KDE as an invitation to legality in the enterprise since Troll tech just might make their toolkit non gpl.

      Everything has been cleared now but there are still some freaks out there.

    35. Re:KDE is not to be ignored by Billly+Gates · · Score: 2, Insightful
      I remember for the 3-4 years Gnome would always freeze up and the apps would core dump. Ever run Linux on init 3 and run gnome by startx? I remember closing X and seeing line after line of gtk+ error messages.

      Many users do not see them today because they use kdm or gdm upon bootup. Gnome is fine today but it had its share of problems when it first came out. It wasn't untill 2.x that it finally became stable.

    36. Re:KDE is not to be ignored by Fancia · · Score: 1

      KDE has only ever crashed for me when I was suffering from DMA issues that often corrupted IDE transfers. Once that was fixed, KDE never crashed; the only reason it did was because it didn't load properly due to hardware issues. I've tried GNOME, but don't like its interface; it strikes me as much clunkier than KDE's.

      --

      Bít, zabít, jen proto, ze su liska!
    37. Re:KDE is not to be ignored by paranerd · · Score: 1
      If you want "no choice", we can use Windows.
      Thank you for saying that.

      In The Moon Is A Harsh Mistress Heinlein wrote,
      Think about it. If a bill is so poor that it cannot command two-thirds of your consents, is it not likely it would make a poor law? And if a law is disliked by as many as one-third is it not likely that you would be better off without it?
      Alienating one third of your market at the outset is NOT "a good thing".
    38. Re:KDE is not to be ignored by paranerd · · Score: 1

      Trying to convince your bosses that you have to maintain compliance with two functionally identicall GUI environments will not go over very well.
      I don't get it. Where I work if we chose Debian (or any other distro) a mandate would come down from on high that the entire shop would be Debian with XXX (insert Gnome or KDE or twm; whichever you think would be the stupidest decision). So, unless I am missing something else, that argument can be disposed of.
    39. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Why don't you go make up lies about my mother, while you are at it?

      Your mother is terrible in bed. I should know.

    40. Re:KDE is not to be ignored by __past__ · · Score: 2, Informative
      Actually, that Trolltech GPLed Qt is a problem in itself. ISVs using KDE would have to open their applications or pay Trolltech for a commercial license, while GNOME-using ones don't have to do either, scince it is all LGPL.

      Not that there are that many ISVs anyway, but I guess that some people want to change it. But all that has been discussed to death already.

    41. Re:KDE is not to be ignored by Prowl · · Score: 4, Insightful

      "Users having a choice is a good thing"

      depends on the user...

      Personally i don't use a desktop per se. i use enlightenment, and spend the majority of my time at a shell prompt. I'm a developer and its the easiest way to get my job done. If i want software installed i tend to grab the sources and install it myself. In this case, choice is a good thing.

      Limited choice can also be a good thing. Look a Mac OS X. You get Aqua. no questions asked. And everyone seems to love it.

      But remember that a user who uses OS X is a completely different person to one who demands choice. A OS X user needs things to "just work", and it is this target user that UserLinux is going after i believe.

      Now this approach is far too restrictive for people like you or I. We're quite happy to poke around, getting things just right. If we were inclined, we could argue that its one of our fundamental human rights...

      But remember harry homeowner. He just wants to turn on and read his email, surf the net and do his work. He's not interested in choosing a desktop or editing his muttrc. Harry doesn't understand the distinction between kernel,OS,windowing system and desktop, and neither *should* he understand it. His computer is simply a productivity tool that just works.

      Think of it like a car.
      I own a car, but understand little about how it works other than the basics. I'm not interested in the finer details of the engine. I just need to get from A to B.

      UserLinux is simply trying to fill the "from A to B" gap in the market.

      Of course, this is all based on my limited (mis-)understanding of the UserLinux manifesto.

      --
      That man tried to kill mah Daddy
    42. Re:KDE is not to be ignored by Jason+Earl · · Score: 5, Insightful

      Actually vi *is* the standard UNIX text editor. In fact, vi is part of the official POSIX specification. In short, the UNIX world actually did standardize on vi. Most UNIXes include vi by default, while Emacs has to be installed separately. So your example is a good one, but it doesn't prove the point you were trying to make.

      UserLinux will default to Gnome, and will include it in the default. However, UserLinux will be based on Debian GNU/Linux and so installing KDE will be as simple as 'apt-get install kde'. The reason that this is an issue is that Bruce has actually raised money for the promotion and development of UserLinux. The KDE folks are cranky because they want the money that is to be spent promoting and developing UserLinux to be spent on their project and not on Gnome.

    43. Re:KDE is not to be ignored by 7-Vodka · · Score: 2, Interesting

      It's too bad the admins can't then take advantage of kde's brilliantKIOSK framework. *shrugs*

      --

      Liberty.

    44. Re:KDE is not to be ignored by Joe+Tie. · · Score: 1

      admit it, if you've used KDE or QT apps you've seen the crashes, I have

      And you've never seen a gtk or gnome program crash? You're either lying, filtering your memories to go along with your bias, or have been very lucky. Neither QT or GTK are magic bullets that are going to suddenly make up for a programmer's errors. I've written with both QT and GTK, and I'm living proof that neither are going to do a thing for hastily written code that hasn't had enough testing.

      --
      Everything will be taken away from you.
    45. Re:KDE is not to be ignored by bubkus_jones · · Score: 1

      Yes, it is about choice. Not everyone cares about what GUI or crap they use. Sometimes what they want is something that works and works well, seamlessly with applications, and doesn't require a PH.D to configure. As far as "if they dont' want to have to choose between every little item they should use Windows", that's crap. KDE and GNOME are both open desktop environments for various Unix systems (in this case Linux). Windows is a completely seperate Operating System, with a very restrictive licence that costs a fortune. If they're given choice, what happenes if x amount of the users want KDE, Y want Gnome and z want something entirely different, each with their own compatability and configuration choices. How is the tech support going to be able to diagnose what the problems are if there isn't a common configuration? Keeping everyone on the same desktop environment helps problem diagnotics, allows tech support to have an easier time configuring the systems (if each system is the same, you can take your time to set up one system close to perfect and then just image it onto the rest of the systems, my school does it with a couple labs). Also, for those new to Linux/KDE/Gnome/whatever, how hard will it be to learn to use it if they have to be taught several different desktop environments at the same time? What about the people doing the teaching? How much should they have to learn just to get people to be able to do their jobs? How much longer would the instruction be? How much more would that instruction cost? Keeping the same desktop on each system is a smart thing, each system will be standardized, each system will be like the others, so that each employee can use whatever computer, even if they're not at "their" system? Some people want choice, a.k.a the people who want to take control of every little portion of their system's configuration. Not everyone cares about that, nor do they want to bother with it. For them, just give them something that works.

    46. Re:KDE is not to be ignored by Afrosheen · · Score: 1

      I'll take that challenge!

      Your momma wears combat boots in the shower! Also, she has a nagging tendency to pick her nose while stopped in traffic!

      Wait, maybe that's my mother...

    47. Re:KDE is not to be ignored by rowanxmas · · Score: 1

      I am sure that I could easily up her "productivity" without the use of electronic aids. Unlike some people around here.....

      that was meant as a general insult, more directed to my roomate than any particular poster

    48. Re:KDE is not to be ignored by DraKKon · · Score: 1

      Ypur mother was with me last night.. I still owe her five bucks. No not htat way.. we were playing darts... and I suck at darts..

      --
      "It's not like your minds are as open as the source you love..." - Me to the majority of Slashdot.
    49. Re:KDE is not to be ignored by cscx · · Score: 1

      Yeah, finally. It's about damn time a Linux distribution tried to set a prescendent of some sort of a standard... one of Linux' biggest problems is internal strife (remember how GNOME started... right?)

    50. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      "like the complete inability to do MDI-style interfaces"

      Not to troll, but I'm thankful for that absence.
      I really, really dislike MDI philosophy and simply
      can't understand why people like it.

      Horses for courses I suppose.

    51. Re:KDE is not to be ignored by RoLi · · Score: 1
      While there were some stability problems in KDE3.0 applications (but KDE itself never crashed on me), those have been ironed out a long time ago.

    52. Re:KDE is not to be ignored by mini+me · · Score: 3, Interesting
      like the complete inability to do MDI-style interfaces


      Why would you ever consider that a bad thing? MDI-style interfaces are the worst thing ever.

      I don't really like GNOME either though. KDE provides a great framework and is structured well. KDE may have a few usabilty problems vs. GNOME at this point for the inexperienced user. But KDE should win out on technical merit, the rest can follow later.
    53. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Gnome isn't for all C programmers. I am a C programmer and I think GTK sucks. It would be nice to have another C lib to choose from.

    54. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      GTK has way too many problems and limitations (like the complete inability to do MDI-style interfaces)

      People can joke about this all they like but it's a slippery slope. First it's no MDI-style interfaces, the next thing you know there's no spam and no viruses. Nothing will ever be the same again :(

    55. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      If TrollTech chose to make Qt non-free, then all previous revisions will still be available under the GPL.

      There's nothing to stop anyone forking KDE now or in the future, except that it would be a bit silly to abandon a commercial developer who is putting considerable effort into constructing a free toolkit, to create an incompatible version with the same licensing terms.

    56. Re:KDE is not to be ignored by KewlPC · · Score: 2, Interesting

      Well, if you want to see things like Photoshop running natively on Linux, Adobe will have to use a toolkit that can do multiple document interfaces, and that rules out GTK.

      The #1 reason people prefer Photoshop over The GIMP is the interface.

    57. Re:KDE is not to be ignored by Afrosheen · · Score: 1

      Well it all started back when Redhat was picking a default desktop. At that time the QT toolkit wasn't open enough for commercial distribution so they went with Gnome which was free beer. Shortly afterwards Troll opened Qt and Mandrake had KDE as it's default (as did SuSE). You're right about people still being scared of it, it's stupid but that's how it is.

    58. Re:KDE is not to be ignored by KewlPC · · Score: 2, Informative
      Yeah, lots of C programmers (myself included) hate GTK.

      What I should've said was

      And from what I understand, the whole "C programmers HAVE to write for GNOME/GTK and C++ programmers HAVE to write for KDE/QT" isn't true anymore, as there are bindings for both languages for both environments IIRC.

      or better yet

      And from what I understand, the whole "Only C programmers can write for GNOME/GTK and only C++ programmers can write for KDE/QT" isn't true anymore, as there are bindings for both languages for both environments IIRC.
    59. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      I hate MDI as well, but tons of Mozilla and Opera users love it, so it does have it's fanbase out there.

      (The only thing worse than MDI is fake-SDI apps like MS Access.)

    60. Re:KDE is not to be ignored by delstar+dotstar · · Score: 1
      Actually vi *is* the standard UNIX text editor.

      ED! ED! ED IS THE STANDARD!!!

    61. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      It started further back than that -- Debian had some licence nitpick with how KDE was doing things, and the response they got back from KDE was "We don't care about licencing issues."

      Which is about the worst possible thing you can say to a GNU/Debian hippie. So, they've held a huge grudge ever since (even though the licence issues are resolved).

    62. Re:KDE is not to be ignored by mhesseltine · · Score: 1

      I'd do something that would make her produce, but you'd have to wait 9 months.

      --
      Overrated / Underrated : Moderation :: Anonymous Coward : Posting
    63. Re:KDE is not to be ignored by Nothinman · · Score: 1

      If we want "no choice", we can use Windows.

      So just don't use UserLinux, who cares what they include and don't include? There's plenty of other, commercially supported distros out there.

      I personally don't like QT or KDE so I couldn't care less if every distro stopped shipping them, but I'm not going to cry if SuSe starts excluding Gnome either.

    64. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      I personally don't like GNOME very much.

      To each his own. I think KDE has great potential to not suck once the people in charge realize that sometimes, less IS more. I think a little cleanup of the Kontrol Panel and the Konqueror file manager would go a long way. You don't have to eliminate options, just move the less frequent things into an "Advanced" drop down menu or something. KDE is just too dirty.

      And screw all you condescending zealots with major God complex issues who like to dehumanize everyone with your childish remarks such as "you are just too stupid to use it." It has nothing to do with being stupid. Personally I prefer NOT to live in a barn yard with garbage laying all over the place. I know most of you die hard super nerds apparently like to live in squalor and are so lazy you would rather smell like a pig than take a shower, but I don't live that way. Gnome has a sense of class and elegance that KDE is badly lacking.

    65. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Why don't you go make up lies about my mother, while you are at it?

      K. Your mother's a fat whore.

      HEY! He DID ask for it!

    66. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Including both or more would dilute development efforts, not to mention confuse Harry Homeowner, who is only interested in writing docs, and playing MP3s.

      Mmm, joe sixpack can use it too?

    67. Re:KDE is not to be ignored by reallocate · · Score: 1

      You're right about the common platfrom, but the availability of new packages is, I think, not important for most businesses. Likewise, most businesses don't pay developers. The real cost for most businesses is in training and support.

      --
      -- Slashdot: When Public Access TV Says "No"
    68. Re:KDE is not to be ignored by Charlotte · · Score: 1

      No, but along with RedHat and Novell adopting GNOME, it might just mean that GNOME "wins" by virtue of commercial forces rather than technical ones.

      I wouldn't count on that, really. Maybe it will just drive KDE to get rid of the more braindead parts of their C++ code by providing good templates etc for people to use. If they win technically then they'll win in Linux. Don't forget that geeks are the Linux motor.

      Personally I think someone will come along with something better real soon. It's just a case of getting colleges and universities to start doing the same good things as they did to Unix in the 70s and 80s (let people write something useful in their software projects). And companies of course.

      More importantly, all this doesn't really matter. Who cares which one wins? Don't we want competion rather than monopoly? In my vision of an open source future there is no single supplier of software... Someone please finish Hurd and make a new X implementation :).

    69. Re:KDE is not to be ignored by mini+me · · Score: 5, Informative

      Well, if you want to see things like Photoshop running natively on Linux, Adobe will have to use a toolkit that can do multiple document interfaces, and that rules out GTK.

      Neither the UNIX or MacOS versions of Photoshop use MDI. Why would a Linux version need it?

    70. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Bah, Emacs is the borg.

    71. Re:KDE is not to be ignored by ZigMonty · · Score: 1
      "Limited choice can also be a good thing. Look a Mac OS X. You get Aqua. no questions asked. And everyone seems to love it."

      Ah, but you *do* get a choice of toolkits: Carbon or Cocoa. It's just that the choice is relatively invisible to the end user. Isn't that what Linux should be aiming for?

    72. Re:KDE is not to be ignored by ak_hepcat · · Score: 1

      Sig humor. hahah.

      Yeah, uptime pr0n.

      --
      Support FSF: Stop thinking with your wallet, and think with your imagination. (cc/non-commercial)
    73. Re:KDE is not to be ignored by Karn · · Score: 3, Insightful


      The thing is, you don't have to test for KDE and GNOME. If you write a GNOME program, test it with GNOME, and it will always work with KDE since if you run it from KDE it will still use the GNOME libraries. The same is true for the other way around.


      The argument is that including two software packages that are themselves as complex as the Linux kernel is not a good idea. I'm not a KDE/GNOME developer, but I can understand this. Why can't you?

      I personally don't like GNOME very much. I think QT is a better toolkit than GTK.


      Yes, just what I thought. You're not considering what is best for open/free software, you are simply thinking of yourself. Well, look at the bright side: KDE is open and free, and you are free to compile it under any Linux distro you want.

      --


      Why do I keep typing pythong?
    74. Re:KDE is not to be ignored by zhenlin · · Score: 2, Interesting

      Is MDI a good thing? I say, no. Each document has its own menu that overrides, no, inexplicably magically merges with the parent's window. It is a poorly designed system, most likely designed to emulate Apple's One Menu system. Apple has never had it. Microsoft is moving away from it. GNOME doesn't want it. (Instead, they have TABBED Multiple Document Interface?! They're better, but by quite a bit: Easy access to most of the documents, as opposed to having multiple windows (anywhere))

    75. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0
      If we want "no choice", we can use Windows.

      Well make a version of windows that is open source and free, and is as stable as UNIX. There are people out there that would use linux if they didn't have to do so much work to use/configure it. This includes making decisions about which version to run, which software to use, etc.

    76. Re:KDE is not to be ignored by be-fan · · Score: 1

      If they win technically then they'll win in Linux. Don't forget that geeks are the Linux motor.
      >>>>>>>>>
      How long will that be true? Its true now, where KDE enjoys a slightly larger user-base because it is slightly better overall (better technology, worse interface), but with Sun pumping out hundreds of thousands of GNOME desktops, how long will geeks have any influence?

      Don't we want competion rather than monopoly?
      >>>>>>>>>>>
      I don't want either to win. I think that the competition is a great thing for both desktops. But I fear that the commercial industry will force the situation. If KDE ceases to be a viable competitor to GNOME, because of the commercial factor, competition in desktops will be a thing of the past.

      --
      A deep unwavering belief is a sure sign you're missing something...
    77. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      how fucking stupid are you guys? no really - how fucking stupid? this distro is an attempt to provide businesses with a linux os that has one of evertything - if its gnome its gnome, if its kde its kde

      if you dont like it then go and roll your own fucking distro - ahh but of course you cant - subscibing cocksuckers like you are too busy using your /. subs to moan at the slightest problem without DOING anything

      you know what the biggest holdup is to linux on the desktop - you whining cunts

    78. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      "Yes but we all know VI is far superior to EMACS !!"

      hey i prefer light blue skys to dark blue ones! look at me I'm an individual - i only agree with 50% of the sad fucking nolifers out there!

      you sir, are an utter fucking cunt

    79. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      You dont give a fuck about harry homeowner? well whoopdefucking doo - it may have passed your attention but thats what this is about - a usable linux distro that suits business and the average comp user. dont like that? well take your Magic:The Gathering cards and get to fuck.....

    80. Re:KDE is not to be ignored by tepples · · Score: 1

      If KDE ceases to be a viable competitor to GNOME, because of the commercial factor

      Then somebody who wants to draw Mac developers to its platform may pour money into GNUstep, whose API is a clone of what became Cocoa.

    81. Re:KDE is not to be ignored by the_2nd_coming · · Score: 0

      why do you need an MDI? you don't need it, and it works better with out one.

      --



      I am the Alpha and the Omega-3
    82. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Maybe the commercial forces chose GNOME for technical reasons. Hmmmmmmm?

    83. Re:KDE is not to be ignored by the_2nd_coming · · Score: 0

      GTKmm is much better than plain old GTK+.
      why no use pyGTK for the interface programming and C for the logic.

      --



      I am the Alpha and the Omega-3
    84. Re:KDE is not to be ignored by steveha · · Score: 5, Informative

      This is really just a, "We don't like KDE, so we've decided that nobody who uses our distro will use it."

      No. You're wrong.

      Bruce Perens said, repeatedly, that he feels that GNOME and KDE are exactly equal in features, and that there is no real technical superiority of either over the other. If the licenses were identical too, he would have had to flip a coin, he said.

      And he took some pains to point out that he has recommended Qt as a solution for some of his clients, and that his publishing company just publised a book on KDE.

      And it isn't even true that "nobody who uses [UserLinux] will use it." Since UserLinux is just Debian with a specific set of packages, there is no reason at all why you couldn't set up a KDE desktop on your UserLinux system. And you know what? If you did that, Bruce Perens wouldn't care.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
    85. Re:KDE is not to be ignored by be-fan · · Score: 1

      Not all MDI is created equal. Check out KDevelop3's IntelliJ-inspired MDI (which has been factored into the KDE MDI widget, so other apps like Kate can use it too!)

      --
      A deep unwavering belief is a sure sign you're missing something...
    86. Re:KDE is not to be ignored by Celerian · · Score: 0

      Thank you. Someone on topic. Personally, I like the KDE Kernal.

    87. Re:KDE is not to be ignored by steveha · · Score: 1

      EMACS is a text editor. So is vi. They are completely different animals, however.

      vi is relatively small and fast compared to EMACS. It is modal: you need to switch between edit mode and text-entry mode a lot. Classic vi didn't have a scripting language (although it did have keystroke macros). vi commands are simple, and you combine them to do powerful things.

      EMACS is built on a LISP interpreter, and over time rather sophisticated stuff has been done in and with EMACS. Some people spend their whole day in EMACS: they edit code, compile it, debug it, read their mail, read USENET news, and even browse the web, all from inside EMACS. (People make jokes comparing EMACS to an operating system.) EMACS isn't modal; you are always in text-entry mode, and there are many different powerful commands.

      Back in the day, EMACS took much longer to start up than vi did, but modern computers render this comparison moot. Either one is pretty lightweight compared to, say, Mozilla. (An old joke is that EMACS takes forever to start up, but you don't care because once it's running you never leave it.)

      I have tried to explain as fairly as I can. Now for the opinion part: I love vi, and hate EMACS. Partly it's an imprinting thing: I learned and used vi for years before trying EMACS. But also I love how you can do powerful things in vi with a few simple commands that combine together, I love how the commands are easy to type if you are a touch typist, and I don't mind the modal-ness. And I have never really taken a shine to LISP, so I don't want to use it for scripting my editor. And I hate remembering and typing commands like or whatever.

      I use vim, an improved version of vi, and vim is available with a Python interface. Perfect.

      I hope it's clear (to all the adults, anyway) that using vi or using EMACS doesn't make you a better person. The whole vi-vs-EMACS war is partly tongue-in-cheek anyway.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
    88. Re:KDE is not to be ignored by AstroDrabb · · Score: 1
      It is a mistake to geeks like us, however in the Corporate World(tm), too much choice is a bad thing. Admins don't want to worry about which desktop the user has, they want ONE standardized desktop. KDE and GNOME are _both_ great programming efforts IMO. Though, eventually the Corporate World(tm) would have to standardize on ONE. The ball fell in the Gnome court. That doesn't mean KDE will or has to die off.

      I use Fedora Core and MS Window XP as development workstaions at work. I use Gnome under Fedora Core. Why, becuase of Evolution and Ximian Connector. I need to get my email from a crappy MS Exchange 2003 server. I have been pushing for the company to switch to a standard IMAP server or even the new SuSe Open Exchange server. Though it is a hard battle in a fortune 500 company with 110,000+ employees. I think many corporations in the USA are tied into MS and their products. There is no groupware solution under KDE. Kontact, which is based on KMail is no where near as polished as Evolution. Kolab Server, the KDE based groupware solution, is not something large corporations are going to swtich to. So KDE not having any native Exchange support is a real killer for KDE. The second thing that hurt KDE is that SUN picked Gnome as its new desktop. That means corporations can get enterprise level support for a Gnome based desktop and not KDE.

      The other thing killing KDE IMO is QT. With QT you either have to develop Open Source software or pay QT to develop commercial/proprietary software. With GTK+ being under the LGPL, you can develop Open Source OR closed proprietary software without having to pay extra to use the toolkit. Developers don't have to pay MS to use the Win32 API, and it would seem silly to have to pay QT to develop a commercial, closed source app under Linux. Look at the latest version of the Linux NVidia drivers. They now include a GUI to tweak the settings for an NVIdia card under Linux similar to the one under MS Windows. The GUI is written in GTK+2.x and NVidia did not have to pay QT just to be able to write a GUI for some OS.

      I am not trying to flame KDE, as I said, it is a great desktop. I just think that for Linux to be more accepted in the Corporate World(tm), a corporate Linux distro needs to REALLY limit the choices of packages, pick what the distro builders feel are the best and focus on making those packages work well together. This way commercial companies can focus on ONE toolkit to build their applications. Many people in the Linux community (myself included) complain about lack of commercial desktop software. The reason is because there are TOO MANY CHOICES. If a commercial company is looking to offer a closed source product under Linux for the desktop user, it would currently be a nightmare to choose what resources to use. KDE/QT, arts, dcop, kdeprint, etc vs. Gnome/GTK+, esd, gconf, gnomevfs, etc. Think about how your "average" home user can walk into a software store and pick up some little app that prints greeting cards. There is no commercial offering like that under Linux. Why, too much choice IMO. I do love the chioces in Linux, though for corporate approval, there needs to be some leader that comes along and picks and choses for the corporate suit and slap a label on it and sell it to them. IMO, I think UserLinux is making the right choice. It may be a little hard to swallow now, though I think in the end it will be best thing that happend to help Linux get on the corporate desktop.

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    89. Re:KDE is not to be ignored by Charlotte · · Score: 1
      with Sun pumping out hundreds of thousands of GNOME desktops, how long will geeks have any influence?

      Until recently we had to compile our own Gnome and KDE versions on Solaris continuously so we'd be up-to-date, so I'm not at all angry with Sun for this move.

      Look at it this way:
      • Sun doesn't sell nearly as many (enterprise) desktops as they used to in the Sparc 5 days. They would really love to change that.

      • For those that they do sell: this move towards using open source software is a real mind shift, Sun is a really closed company and for them to make this move is unprecedented.

      • This is making the visibility of open-source in the enterprise rocket sky high. Sun is a reputable company of Fortune 500 status.

      • The amount home users and small businesses that use Linux will also grow, not just enteprise packaged versions of the same.

      • Add to that a single desktop for companies and others to start using a a springboard onto open-source.

      I truly don't see anything wrong here. Who cares what desktop choice UserLinux, HP or Sun makes as long as it isn't closed?

      But I fear that the commercial industry will force the situation. If KDE ceases to be a viable competitor to GNOME, because of the commercial factor, competition in desktops will be a thing of the past.

      KDE and gnome don't exist for that long, and they weren't designed like you'd design a rocket: clear interfaces that are well-planned from the start, etc like LDAP where implementations don't matter.

      In time someone will come along and set goals for a protocol/interface that is capable of abstracting the implementation of GUIs (IEEE for instance, or a university like MIT which designed Kerberos).

      At that time we'll be in a new world, as unimaginable as Linux being a threat to Microsoft would be in 1992. It's just a matter of time and if open-source gains wider acceptance and the worlds' computer-whiz resources are spent on issues like GUI implementation, then human nature will take over and change will occur - it is the nature of life. VHS supplanted the superior Betamax but won't withstand the computer age...
    90. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      If UserLinux thinks promoting a single desktop solution will improve their profitability, why don't they promote Windows?

    91. Re:KDE is not to be ignored by Natalie's+Hot+Grits · · Score: 2, Interesting

      ISV's who program for windows don't seem to be having any problems paying for the Microsoft Visual C++ License they must purchase in order to program for the windows environment...

      (or borland compiler, or other commercial development environment)

      This is what Proprietary software is ALL ABOUT. Integrating someone else's technology into yours, pay royalties for it, and then sell it at a profit. Have you ALL LOST YOUR MIND???? This is how it has been done for YEARS. Closed source software has ALWAYS worked on this model, and the price of QT licensing is negligable compared to the cost of paying developers to use GTK+, and longer development cycles which exist for non OO based GUI tools. If a closed source software company can't afford a few thousand dollars for QT licenses, they need to seriously reconsider their business model.

      Considering PyQT and PerlQT now, the LARGEST developer and user DE on linux, and the top notch and stable KDE, there is really no reason whatsoever to even imply this measly licensing fee for non GPL apps excuse for this one. Its the most ridiculous excuse I have ever been exposed to. Seriously.

      The main point? Closed source proprietary technology houses HAVE NO PROBLEM paying negligable royalties when the alternative is increased cost due to longer development cycles forced by GNOME/GTK+, and smaller and less helpful community based almost exclusively in the US.

      This does NOT exclude smaller companies from the competition. They always have the option to use GTK+ with themes to match the target DE (this functionality already exists and is being extended every day) if they need gratis GUI libraries for use in proprietary software. It is also not a problem to write GTK+ applications that integrate into KDE's libraries for printing, file browsing, etc.

      In a nutshell, licensing should have NOTHING WHATSOEVER to do with choosing GNOME.

      --
      Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.
    92. Re:KDE is not to be ignored by benjamindees · · Score: 1
      The KDE folks are cranky

      It's not just "KDE folks". There are a lot of users and developers who use KDE because it is technically superior and just want an organized effort to improve the integration of all apps with all desktop environments, so that we can continue to use whichever is technically superior, not whichever Mr. Perens decides fits his narrow view of "acceptable".

      --
      "I assumed blithely that there were no elves out there in the darkness"
    93. Re:KDE is not to be ignored by fault0 · · Score: 2, Informative

      > If TrollTech chose to make Qt non-free, then all previous revisions will still be available under the GPL.

      Additionally, the last free version of Qt would become BSD licensed. As per KDE FreeQt foundation guidelines.

    94. Re:KDE is not to be ignored by fault0 · · Score: 1

      Yup, but what's weird is that UserLinux will include other toolkits _anyways_ besides just GTK. It'll include at least, XUL, used in Mozilla, VCL, used in OpenOffice, and probably wxWindows as well.

      It's fine using GNOME as a default desktop. That's Bruce's decision I guess. But including Qt and KDE _libraries_ and some apps is probably a mistake. You don't need to include the KDE desktop, but don't ignore KDE apps, unless you're willing to ignore non-GTK apps like OpenOffice as well.

    95. Re:KDE is not to be ignored by AstroDrabb · · Score: 1

      You do know that there are C++ bindings for GTK+? As well as bindings for python, and Java and perl and C# and ...

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    96. Re:KDE is not to be ignored by DA-MAN · · Score: 1

      Been done, it's called RedHat Enterprise Linux 3.0WS and it includes KDE.

      Frankly I think choosing the .deb format in the Linux world is pretty much the Kiss of Death. It will never be LSB compliant. APT supports rpm just as well these days, they need to get with the program.

      --
      Can I get an eye poke?
      Dog House Forum
    97. Re:KDE is not to be ignored by be-fan · · Score: 1

      What technical reasons? GNOME was chosen at RedHat early-on because a lot of the GNOME developers worked at RedHatf. GNOME was chosen by Sun because the Sun UI people were more comfortable with C (that was their official reason). GNOME is on the verge of being chosen by Novell because they bought Ximian before SuSE, because SuSE held out for more money. And Perens doesn't even pretend that technical reasons were involved in his choice.

      --
      A deep unwavering belief is a sure sign you're missing something...
    98. Re:KDE is not to be ignored by FCAdcock · · Score: 1

      Excuse me!

      First you ask us not to call you stupid, that's ok. But next you go on to call us lazy, and then tell us that we smell like pigs.

      I'll give you the exact same respect that you give me. You gave me just enough respect for me to realize that you are too dumb to live. Please die now. Not later, but now.

      --
      --Forest C. Adcock--
    99. Re:KDE is not to be ignored by AstroDrabb · · Score: 1

      The could be implemented in Gnome. Also, how many corporate desktops are locked down as much as a standard kiosk is? I built a kiosk system for the company I work for and it is in over 1,600+ locations. The system is *very* locked down. I don't think having a kiosk for a corporte desktop would be that useful. Thought the kiosk feature is nice and could come in handy for some deployments, over all it won't be very useful. What I think give more weight to Gnome is Ximain Evolution and Ximian connector. I use both to get my mail from our MS Exchange 2003 server. I cannot do that under KDE. The other issue is with QT. If you want to develop commercial applications, you have to pay QT. With GTK+, you can develop closed source or Open Source free of charge. Look at MS Windows and Mac OS X. You don't have to pay extra to develop commercial, closed source applications on those platforms, it would be silly to require that under Linux.

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    100. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Don't you get it? Debian fags are just bunch of spoiled kids that have to get it their way. If somebody makes a great program, and they don't praise debian, automaticly that program is evil.
      KDE is just one example...there are others, like mplayer etc.
      Fuck debian. Who wants a homo distribution anyways? Desktop distributions are already out there...like RedHat, Mandrake, Suse, etc.
      And majority of them don't use fag gnome shit (except RedHat, but they are fags anyways).
      Fuck debian. Fuck gnome. Fuck freedom of speech.
      Say "Hell Yeah!" to free beer.

    101. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      "Bruce Perens said, repeatedly, that he feels that GNOME and KDE are exactly equal in features, and that there is no real technical superiority of either over the other."

      That explains how much Bruce Perens actually do not know if he really said that.

    102. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Sure... just check of the main Gnome page or if your using Debian, just apt-get them...

    103. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Okay guys, I'm really sorry for being so obvious, but... what's a troll?

    104. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      I personally don't like GNOME very much. I think QT is a better toolkit than GTK.

      Yes, just what I thought. You're not considering what is best for open/free software, you are simply thinking of yourself.

      And what, may I ask, is wrong with that?

      Look, just because we both use open source does not make you my Free Software Brother(tm). This is not the Great Crusade(tm).

      The only reason for open source/free software in the first place is that it is better for developers and users. Well, this guy just stated what's better for him as developer and user.

      Your mileage may, of course, vary, but the statement was perfectly germane to the topic at hand.

    105. Re:KDE is not to be ignored by be-fan · · Score: 1

      Kiosk is just the name of the system! It lets you lock down the system as much as or as little as you want. And it probably could be implemented in GNOME, but it isn't, is it?

      --
      A deep unwavering belief is a sure sign you're missing something...
    106. Re:KDE is not to be ignored by someonehasmyname · · Score: 1

      Your sig: Thank you! I was starting to think I imagined that. Nobody I know heard that one.

      --
      Common sense is not so common.
    107. Re:KDE is not to be ignored by shoor · · Score: 0, Redundant

      Emacs an early attempt to mimic YACC? I don't think so. The attempt to mimic YACC (and a successful one too, IMHO) is Bison. Emacs started out as some macros for some system that I've never used and don't know much about, but I think, even in its earliest incarnation, its purpose was text editing, whereas YACC is a tool for creating parsers for LALR computer grammers. Of course, emacs has grown to include other functionality as well, but even now, so far as I know, it's not a parser generator.

      --
      In theory, theory and practice are the same; in practice they're different. (Yogi Berra & A. Einstein)
    108. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0
      Also, I fuck goats.


      I applaud you for making full disclosure.

    109. Re:KDE is not to be ignored by JanneM · · Score: 1

      I don't hear you being righteously indignant about Xandros or Linows not including GNOME...

      Hypocrite.

      --
      Trust the Computer. The Computer is your friend.
    110. Re:KDE is not to be ignored by Junkstyle · · Score: 1

      Is Harry Homeowner smarter than Joe Sixpack?

    111. Re:KDE is not to be ignored by Natalie's+Hot+Grits · · Score: 2, Informative

      What grudge? Look at the article, there are many Debian developers who are supporting this effort. Debian has no grudge against KDE. in fact, Debian ships one of the best KDE distros out there. To say that there is a grudge between the 2 projects is just ridiculous.

      The conflicts are coming from Bruce Peren's vision of having a completely gratis operating system that coporations can then add value to and resell.

      The problem is that QT cannot be resold with closed source applications without royalties.

      The answer for Bruce is to use GNOME only and exclude KDE. Never mind that you can still develop KDE applications using the GTK+ gratis toolkit (provided you would want to use a toolkit that is as primitive as GTK+)

      The answer for the rest of us is: "Qt has tons of commercial programs using it because of its cross platform design and top notch API... GTK doesn't. KDE has a larger user base.... GNOME doesn't. KDE uses OO toolkit to achieve its integration... GNOME is stuck in the stone age. KDE had all the problems GNOME is currently working on figured out 2 years ago... GNOME still doesn't. And KDE is a worldwide project... GNOME is a US Centric project."

      The facts are that KDE coporate and enterprise desktops have been deployed and in production usage for years in massive quantities, and GNOME is just barely starting out. GNOME itself was created just because RMS didn't like the QPL license, and he was afraid KDE would take over the Linux desktop and stick us all with Qt royalties. Now that Qt is GPL, bruce perens is complaing that it is "too GPL"... Give me a BREAK!

      --
      Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.
    112. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      He said to make up lies.

    113. Re:KDE is not to be ignored by KewlPC · · Score: 2, Interesting

      The argument is that including two software packages that are themselves as complex as the Linux kernel is not a good idea. I'm not a KDE/GNOME developer, but I can understand this. Why can't you?


      No, see, I do understand it. I just don't agree with it. Especially since other distros can do it just fine.

      By not even including both on the installation CDs they are effectively limiting how useful the distro is to the user. Yes, anybody can go and download KDE or GNOME. How many people can properly build and install them? But how many people will want to, when they can just pick a different distro that includes KDE on the installation CDs (as prebuilt binaries with the dependency problems already sorted out)?

      The whole point of a Linux distribution is to include Linux and essential Linux software on a CD (or 3) in a nice, easy, prepackaged form so that users don't have to download it, build it, and install it by hand. If a distro is intentionally leaving what for some people is a core application (and not even offering it as an option) off of the installation CDs, then that distro is useless to those people.

      To each and every corporate KDE user, UserLinux has become effectively worthless in one fell swoop.


      Yes, just what I thought. You're not considering what is best for open/free software, you are simply thinking of yourself. Well, look at the bright side: KDE is open and free, and you are free to compile it under any Linux distro you want.


      Have you ever tried writing programs for GTK? If not, please kindly shut up. GTK sucks, plain and simple.
    114. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Well, I am not going to work with gtk+ and the others toolkits around Gnome. I think they are a bad kind of patchworks and I will not mess with them so are every serious computer engineers around me.

      It is a question of personnal taste, perhaps, but without KDE, I simply will not work with the UserLinux, or more likely I will _fork_ this new "standard".

      --
      Ant1

    115. Re:KDE is not to be ignored by fucksl4shd0t · · Score: 1

      First off, contrary to its name, UserLInux is supposed to target businesses. :) Enterprise is the buzzword being dropped in relation to UserLinux...

      Now this approach is far too restrictive for people like you or I. We're quite happy to poke around, getting things just right. If we were inclined, we could argue that its one of our fundamental human rights...

      As much as I disagree with Perens's decision here, I think that his decision does command a certain amount of respect. He chose to draw a line in the sand in one of the biggest open-source/Free Software flame wars ever (bigger, even, then RMS vs LInus on GNU/Linux). The one thing everybody uses is the interface, and it's the single-most widely held emotional aspect of any OS. It's the reason Mac users love macs and hate Windows, and it's the reason Windows users love Windows (because they live in a cave and have never seen a decent OS, of course ;) ).

      That said, I felt that Perens's rebuttal came off as sounding more like him trying to justify a bad decision than him trying to explain a good decision. KDE has more penetration in the markets he wants to penetrate. RedHat is the distro that pushes LInux that farthest in the US, but RedHat is a server OS. At least, that's how they're portrayed, and that's how they're branded. Europe and the rest of the world use KDE, and that's where all the KDE penetration occurs. Using GNOME is going to give UserLinux an uphill battle where they could've used KDE to even the playing field. "Look here, my prospect. KDE is used and supported by the German government. The reason our PIM software has gotten so good recently is because the German government paid the KDE boys to do it for us. (more of the same)" Compare that to "Look here, my prospect. I realize that Gnome's user base is largely home users in the US, but it is good. Give it a shot, you'll find it has plenty to offer." What can Gnome show us besides the "Made in America" sticker that we americans are so fanatical about?

      From my point of view, though, UserLinux is pointlessly redundant. If you're running a business and you want a reliable server + desktop combination, you already have three choices, each with commercial support attached. RedHat, Mandrake, and SuSE (now Novell). You used to have Caldera, but we all know where they've gone. RedHat has already determined that pushing for home adoption isn't in their business plan, but that doesn't mean that RedHat isn't pushing the desktop market. THey're focusing on the Enterprise, where Kirk would just love to have a red fedora on his tablet pc that the hot yeoman just brought him. Erm. Anyway...

      If you run a business, and you want strong commercial support for your KDE desktop, you've got Mandrake and SuSE to pick already. If you want branding, strong commercial support, and you don't give a shit about your desktop, you've got RedHat to pick. All three offer server packages that kick the ass out of Microsoft. Additionally, RedHat has IBM and (last time I checked) Sun as partners to give them a boot up for servers. For desktop? Well, normally you want to pick something that doesn't require an awful lot of administrative overhead and also increases user productivity. You'd probably pick the same vendor as your server vendor, right?

      THe other thing Perens has really missed the boat on, here, is the fact that the "Enterprise" market has Humans and Vulcans on board. That means the doctor has to be able to treat them both. In-house developers that have to deal with users in both Windows and UserLinux want something cross-platform, and GTK isn't cross-platform. Ever use the Windows port of GTK? It's maintained by one guy, in his spare time, for fun. Sure, you could pick wxWindows, but wxWindows doesn't have Gnome integration, so there's no huge benefit to picking it for in-house development.

      Qt, anybody? Pay the license and get something that just fucking works. You can sto

      --
      Like what I said? You might like my music
    116. Re:KDE is not to be ignored by 10Ghz · · Score: 1
      Bruce Perens said, repeatedly, that he feels that GNOME and KDE are exactly equal in features, and that there is no real technical superiority of either over the other.


      Many think that KDE is significantly ahead of GNOME when it comes to the infrastructure and the like. For example, Kparts, Kioslaves and DCOP (Hell, DCOP is so good that the new D-BUS was largely based around it!)

      Yes, of course you can istall KDE by yourself of UL. But UL is making a BIG mistake when they limit themselves to just GNOME/GTK+-stuff. For example, Lindos is a KDE-distro. Yet their IM-client is GAIM! Clearly, they just picked the best tools for the job. UL is not doing that. They are limiting themselves by just picking one toolkit. By excluding KDE, they wont get kick-ass stuff like K3B, Kdevelop and Quanta+. Even though Lindows is focudes on KDE, they still support GTK+-apps. And it hasn't hurted them one bit.

      And I dislike the fact that UL seems to be one man show. There was discussion about this topic in the mailing-list, and the KDE-folks made a ver good proposal. Perens simply said (in effect): "talk all you want, but here we do things MY way!". I wouldn't be one bit surprised if Perens chose GNOME because ut happens to be his personal favourite of the two. Whch desktop does he use, anyone know?
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    117. Re:KDE is not to be ignored by fucksl4shd0t · · Score: 1

      Keeping the same desktop on each system is a smart thing, each system will be standardized, each system will be like the others, so that each employee can use whatever computer, even if they're not at "their" system

      Yes, yes, yes. All true. However, is this choice the choice the vendor should be making? Say you run a business, and you need a certain set of features for your users and Gnome doesn't cut it. Does UserLinux penetrate your business? Nope. You'd be a fucking idiot to hire UserLinux when you know it won't do what you need, or that you'd have to install a bunch of extra shit that falls outside of any support contract you might have gotten.

      Who should be making the desktop choice, exactly? Well, I tend to think the IT guys that have to build and support the things should make the choice. Management gives them a spec and they pick the environment that'll give them the easiest setup and support that meets the spec. The biggest problem with Windows is that the vendor has already made all the decisions you face for you, and they haven't made them all the same way you need them to be made. You're stuck with that. How is UserLinux going to distinguish itself, now? By making all those same decisions for you, regardless of how you actually needed them to be made?

      So, yeah. The vendor does need to provide choice, even if the choice they provide isn't so obvious. Choosing to include Gnome and exclude KDE libraries has taken away choices from the businesses, choices they will likely want back. What makes UserLinux better than any of the commercial offerings, then? Lindows already has the draconian Microsoft-like setup where all the decisions have already been made for you, like it or not. Mandrake has the complete opposite approach and tries to give you every choice you could possibly have. They also, coincidentally, have their entire source tree available so you can easily customize the installer itself. Damn. Talk about choice! They give you everything, man. You can let them make all of your decisions for you (default install), or you can make all of the decisions you want to make (default install + tweaks), or you can make all the decisions and still be completely compatible with Mandrake (custom install). If you don't want to screw with the source tree, you can save the list of packages you want installed on every machine and use that same list for every new installation. (Yeah, they could do more in this area to make it easier to install thousands of machines)

      Taking away business decisions from the business is one of the most compelling parts of any LInux-related value proposition, and UserLinux is removing that from their own value proposition. I think Queen said it best when they said "ANother one bites the dust" ;)

      --
      Like what I said? You might like my music
    118. Re:KDE is not to be ignored by 10Ghz · · Score: 1
      The could be implemented in Gnome.


      So let me get this straight: KDE has a feature that is basically required by corporate environments. GNOME lacks that feature. Yet Perens said that the two desktops are equal in features and architecture.

      Yes, I do agree that there generally is no "freeedom of choice" in corporate-environments, so sticking to one desktop is a smart thing to do. But why not let the admin make that choice? Why does Perens get to make that choice?
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    119. Re:KDE is not to be ignored by fucksl4shd0t · · Score: 1

      Look at MS Windows and Mac OS X. You don't have to pay extra to develop commercial, closed source applications on those platforms, it would be silly to require that under Linux.

      Quite the contrary, if you intend to develop for Windows and Mac OS X with GTK you're fucked. Sorry, no go. Doesn't work at all. GTK uses Xlib (or rather, GTK now uses GDK which uses Xlib) and Mac OS X doesn't ship with X. THe windows port of GTK is the suck of all suck. It crashes more often than a drunk driver. It's less reliable than a 3-time loser serving his life sentence. It makes as much sense to use GTK for windows development as installing a periscope on a baby stroller.

      If cross-platform is to be brought in to this "discussion", Qt will beat the living shit out of anything Gnome tries to offer (with the possible exception of wxWindows, but last I heard Gnome and wxWindows weren't getting along).

      --
      Like what I said? You might like my music
    120. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      No, I wish people like you would get a clue. GNOME and KDE are not just about making a desktop, they are about making a large pool of software bits for developers to use to easily write applications.

      GNOME does that least as well as KDE (regardless of the huge numbers of shouting losers in every KDE artile), with the added advantage of being cleaner and not imposing an expensive annual tax on developers not wishing to release their source code i.e the Qt license you need for KDE.

    121. Re:KDE is not to be ignored by fucksl4shd0t · · Score: 1

      They now include a GUI to tweak the settings for an NVIdia card under Linux similar to the one under MS Windows. The GUI is written in GTK+2.x and NVidia did not have to pay QT just to be able to write a GUI for some OS.

      And the new GUI for configuring the kernel is Qt-based. What exactly is your point with this? Is there *any* reason NVidia had to use GTK for their configure app? None that I can think of. For them it was probably a pretty arbitrary choice. "Hey, you who have been writing our LInux driver, make us a GUI for it." "No problem boss, I'll have it ready tomorrow." DO you really think there was a huge board meeting, or big-time IT department meeting or even a large developer meeting for that?

      I just think that for Linux to be more accepted in the Corporate World(tm), a corporate Linux distro needs to REALLY limit the choices of packages, pick what the distro builders feel are the best and focus on making those packages work well together.

      I disagree completely. I may have been responding to you when I said this already, but here goes again.

      Microsoft gets a lot of flak because they have made a number of decisions in their OS that negatively affect businesses. The decisions themselves differ from business to business, but the bottom line is that most businesses are not completely happy with their Windows OS. Give them Linux, where they can now make all of the decisions they want or they can let the vendor make some/all of them. Do you really think that a company is going to install Linux on all their desktops and then tell their employees "You can use Gnome, KDE, IceWM, WindowMaker, Enlightenment...". FUCK NO. A business is going to look carefully at the desktops available and the apps available, pick ONE, and then install that on their machines. If they're big enough and the contract is big enough, they can probably get the vendor to give them a custom installer that ultimately leaves them with a system that they can use the vendor's update service with. And for that they need the vendor to support the desktop they pick, and if UserLinux isn't going to support KDE, they're going to miss out on a lot of their market. They'll lose it to the likes of Mandrake that fully supports Gnome and KDE.

      ANd no. Debian's volunteer-maintained repository is not a good selling point in this market. RedHat and Mandrake both provide repositories with some QA (probably RedHat's QA is better than Mandrake's, although I prefer Mandrake ;) ), and they each have a significant commercial stake in the quality of their repositories. Debian doesn't, and never will. They're a volunteer organization. That's great and all, but a company wants to know that updating their desktops isn't going to cause all of their users to sit on their asses for 2 days because some volunteer didn't double-check his package.

      Choice is good and needs to be preserved for businesses. The #1 selling point of Linux over Windows is choice. Microsoft has a record for reducing/eliminating choice and Linux and KDE both have a record for creating/adding choice.

      --
      Like what I said? You might like my music
    122. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      KDE has more penetration in the markets he wants to penetrate

      So UserLinux is aiming for the "noisy, aggressive and cluess zealot" market? That's where KDE rules. No, UserLinux is aiming at the corporate market, and that's where GNOME is a long, long way ahead (both in design, and user base).

    123. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Yes Gnome had burn big piles of money which KDE doesn't have and still KDE is at least comparable (I personally think KDE is better). Imagine how much better KDE can be with all money invested into Ximian and others. Maybe with all money invested in Ximian somebody could buy TrollTech and release Qt under yet another licence - LGPL, for those which can't use today GPL (and release Win32 Qt under GPL too).

    124. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Debian supports the RPM format through the "alien" program.

    125. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      > Mac OS X doesn't ship with X
      It may not be installed by default, but Mac OS X ships with X. See Apple's web site for details.

    126. Re:KDE is not to be ignored by DF5JT · · Score: 1

      "If it's about a stable usable business desktop"

      Here is some bad news for you: It is NOT about a stable usable business desktop, it is about an enterprise operating system with all the clockwork needed to make an enterprise tick. That includes desktop management for a huge userbase, central administration of storage, software deployment, network control, printer administration, user help desk, seamless integration of data retrieval, processing and development.

      An enterprise Linux has to compete with IBM, Microsoft, Sun or HP, but not with your choice of a desktop Linux distribution.

      KDE provides for a vision that embraces these key requirements, whereas GNOME does not. Bruce made a bad choice and in his reply he sounds rather apologetic, but not very convinced or convincing.

    127. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Basically Bruce Perens said "you have to make a choice between gnome and kde, and since I like gtk's license (lgpl) better than qt's (gpl or commercial) it will be gnome"

      Not only does that cut out a lot of interesting apps and functionality, but it's incredibly shortsighted. A project like userlinux could be the final push towards desktop standardization. What I mean by that is that the freedesktop.org initiative can be taken so far that you write an app once, for gnome or kde, and it will run equally well in both. This doesn't work right now because they lack a common gui framework (a plugin for both themeing engines to directly support the themes of the other engine should fix this), they lack a common object framework (d-bus goes a long way to solving this, but stuff like the printing architecture needs to be unified too), and they use arbitrarily different standards for stuff like adding icons to the desktop menu's (this is getting better and will be standardized soon).

      If Perens goes with just gnome, it won't bring together the gnome and kde camps, instead it will create a divide. In the marketplace you'll still have one distro using kde and another using gnome, and apps not integrating smoothly with both.

      Userlinux is about making a linux for the rest of us. Bridging the gnome and kde divide is imperative for that. And this project could be the proverbial drop in the bucket to get that done. It's quite disappointing that this shortsighted gnome-only policy is being instigated.

    128. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      UserLinux is for corporate desktops, not home users.

      so why isn't it called CorporateLinux then?

    129. Re:KDE is not to be ignored by luisdom · · Score: 1

      The KDE folks are cranky because they want the money that is to be spent promoting and developing UserLinux to be spent on their project and not on Gnome.
      And from where do you get that?
      Maybe they just want a piece of the cake, knowing that they have a just-as-better desktop?

    130. Re:KDE is not to be ignored by sydb · · Score: 1

      Look, RTF Bruce's statement:

      The decision does not prevent anyone from using KDE and Qt components on UserLinux, does not prevent anyone from installing those components from the Debian packages, and does not prevent any of our support providers from formally supporting KDE. It doesn't take any choice away from users, who can get KDE on our platform or elsewhere.

      Bruce has made the right decision, for the long term.

      --
      Yours Sincerely, Michael.
    131. Re:KDE is not to be ignored by luisdom · · Score: 2, Insightful


      Including both or more would dilute development efforts, not to mention confuse Harry Homeowner, who is only interested in writing docs, and playing MP3s.

      And then, why include the worst of the two? ;)
      Seriously, things are not done like that. Trying to push a standard, and starting by pissing everyone who uses one of the most used desktop is not a good way to start.
      Freedesktop is. Instead of "choosing", they try to integrate everyone, take everyone on board. And in order not to dilute development efforts, they work in what is agreed: interoperability. Work in common things. Most "KDE folks" are willing to throw DCOP, their tech, in favor of a common one, D-BUS. That's how things are done.

    132. Re:KDE is not to be ignored by inc_x · · Score: 1
      If Bruce said it, it must be true.

      It seems more likely though that Nat convinced Bruce to use Gnome from the beginning and that everything else is just a facade to hide this backroom deal. "I even published a book on Qt" sounds to me like "I'm not homophobic, I have a friend that is gay!"

      Oh, and there are of course also Bruce's famous fortune 500 companies that are going to sponsor all this, yet don't want to be named. I wonder if these Spineless 500 companies are the same that bought licenses from SCO

    133. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0
      Fuck KDE. Fuck KDE in the ass.

      Oh, and fuck KDE users in the ass.

    134. Re:KDE is not to be ignored by Performer+Guy · · Score: 1

      Oh, and what would they write docs in? .... StarOffice? Which GUI does that use then.... Oh! Well it'll work on a Gnome desktop OK, but if I want to compile it on UserLinux I have to do extra downloada from TrollTech or somewhere and hope it works... Hmm... something's very wrong with this picture.

    135. Re:KDE is not to be ignored by Info+B!tch · · Score: 1

      Coulnd't have said it better myself. Just include the damned libraries at least. No averge joe user it going to go tooling around in /usr/include or /usr/lib/ Give the developers the tools they need. This is quite obviously a slant against KDE, but I wouldn't worry much about it. To make this choice is suicide. I would argue it was suicide if it was the other way around as well, but I firmly belive that if you have to choose one then for god's sake don't chose Gnome.

      --
      If man does find the solution for world peace it will be the most revolutionary reversal of his record we have ever know
    136. Re:KDE is not to be ignored by Info+B!tch · · Score: 1

      Sorry that argument is bullshit. total bullshit. You include the libraries no matter what. because some one some where is going to try and install a program with the source could and go through dependence nightmares....seems to put linux back at square one. I find it hard to believe that someone like Bruce would make this decision without some alterier motives

      --
      If man does find the solution for world peace it will be the most revolutionary reversal of his record we have ever know
    137. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      What Bruce is really saying is that he is choosing GNOME because proprietary developers can write proprietary programs into GNOME and get away with it. Any addition to KDE has to be GPL. So his thinking is that the business people will want to support GNOME for profit in the traditional (closed source) model.

      He may be right. But, instead of "User Linux", he should call it "Bussines Linux".

      For us, the users, KDE is just fine, or better than GNOME (at least this far). I say this in spite that, at the beginning of the "Desktop Wars" I was firmly in the GNOME side (I think they were right on the lincense issue). When trolltech changed the Qt license, I sat at the fence for a long time. Lately, I am slowly leaning to the KDE side. Why? Because the desktop is, in practice, part of the OS. It should be free. Proprietary applications can be built on top of it, but should not be allowed to become part of it. KDE allows that.

    138. Re:KDE is not to be ignored by Lumpy · · Score: 1

      what about your installer? you need to place icons and menu entries. so now you either need to detect for what is on the machine or shotgun guess and try to force installing the links in both places HOPING that the distro packagers weren't stupid and moved them.

      and YES this is a VERY important thing. when I install a GNOME or KDE program it had damned well come with an installer of a type (rpm is OK) and it is REQUIRED to place it's links in the menu.

      A game MUST put a link in games with an icon.

      Too many linux apps are half assed this way. no installation is even attempted and the user is left to fend for themselves.

      remember this is USER linux... designed for users. not uber-eliete linux that insults you every day when you start X and moves your libs around for some Leet-hacker action every hour.

      user-linus NEEDS to be braindeadish.

      --
      Do not look at laser with remaining good eye.
    139. Re:KDE is not to be ignored by Prowl · · Score: 1
      --
      That man tried to kill mah Daddy
    140. Re:KDE is not to be ignored by sjvn · · Score: 1

      You're missing Perens' point. It's deliberately meant to include only a subset of all possible Linux programs, including desktops, to make it more usable to business people who don't want to make choices. His target audience just wants a working Linux distribution that's already has the important default decisions already made.

      Now, you can disagree with this approach, but it's the approach He decided to take. I think the KDE people involved in this would be far better served by setting up their own KDE-Debian distribution rather than trying to horn in on Perens' project.

      I mean, get real, it's just a distribution, it's not an attempt to create the one true Linux.

      For more info, see my:

      Linux Developers Spar Over Enterprise Desktop Plans
      http://www.eweek.com/article2/0,4149,141590 0,00.as p

      Steven

    141. Re:KDE is not to be ignored by Prowl · · Score: 1

      definitely. he has a job to do and needs to do it as efficiently as possible. joe sixpack just eats peanuts and watches bowling.

      --
      That man tried to kill mah Daddy
    142. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      And can't you already run PS in Wine(x) via crossover, anyway!?

    143. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Yes, Harry Homeowner just wants to do stuff and he doesn't necessarily want to choose between ten applications which all basically do the same. But what he expects is to get the best available application for a certain task. There are Gnome applications which are much better than their KDE equivalents and vice versa. If all KDE applications are excluded then Harry will get some good Gnome apps and some inferior Gnome apps. And that's exactly why Bruce decision to exclude all KDE applications is just plain stupid.

    144. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Can you please post figures that support your statement?

    145. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Yeh, or ulterior motives, even.

    146. Re:KDE is not to be ignored by chundo · · Score: 1

      To each and every corporate KDE user, UserLinux has become effectively worthless in one fell swoop.

      Completely innaccurate. Read the white paper linked in the article. The thing is Debian-based, and there are KDE packages for Debian. Perens explicitly states that there is NOTHING preventing ISVs from providing distributions that are identical to UserLinux, except favoring KDE instead of GNOME.

      That's the beauty of open source. You don't like it? Start your own company to include the stuff that you like, if you think it will be more widely accepted.

      What it boils down to is that this is Perens' idea, Perens' opinion, and consequently Perens' prerogative to choose.

      -j

    147. Re:KDE is not to be ignored by chundo · · Score: 1

      Priceless... laughed my ass off at the "typical novice user session"...

      -j

    148. Re:KDE is not to be ignored by inc_x · · Score: 1

      In fact ISV's who program for windows are already happily paying for Qt.

    149. Re:KDE is not to be ignored by inc_x · · Score: 2, Informative

      You do not need to pay royalties. This has been pointed out to Bruce already but Bruce seems to continue to deliberately confuse a one-time license fee with royalties.

      Another small hint that Bruce might not be completely forthcoming about his real interests wrt. UserLinux. Ask Bruce about the companies that sponsor his plan.

    150. Re:KDE is not to be ignored by LizardKing · · Score: 1

      Having choice does not mean having to choose ... KDE works out of the box.

      GNOME also works "out of the box", but more thought has gone into the default settings than with KDE. The gconf-editor still allows so called power users to tweak the more obscure settings, while the applications configuration dialog can limit itself to providing the more frequently changed options.

      Chris

    151. Re:KDE is not to be ignored by bamstead · · Score: 1

      What I don't understand is how Bruce can make the statment; " It's not only desktop. It must be desktop and server." One of his comments from the artical UserLinux Proposal (And Analysis). I thought userlinux was about the desktop, and Linux is about choices.

    152. Re:KDE is not to be ignored by AstroDrabb · · Score: 1
      For them it was probably a pretty arbitrary choice. "Hey, you who have been writing our LInux driver, make us a GUI for it." "No problem boss, I'll have it ready tomorrow." DO you really think there was a huge board meeting, or big-time IT department meeting or even a large developer meeting for that?
      Your not a corporate developer are you? Or not for one of any significant size? I am a senior developer for a fortune 500 company with 110,000+ employees. Thre are meetings for EVERYTHIHG in corporate American. End of story. Do you really think that NVidia just throws together some code and releases it the next day? Hell no, they test it and test it. They have meetings about the features to go into the next release. Often, the major decisions in a corporations are NOT made by the IT staff, but the management staff. We just had a big series of meetings over our standard Java Servlet/JSP server. Us developers wanted Tomcat for technical reasons and management wanted Oracle9iAS for business reasons. Guess what, management won out. Management does not care about KDE vs Gnome. They don't want choice. They don't want to not be able to purchase some commercial Linux applications because it was developed with QT and they standardized on Gnome. Although you can run GTK apps under KDE and QT apps under Gnome, they do not work well together. Especially with simple things like drag-n-drop or copy-n-paste.

      Most of the IT world is sick of MS not because they limit choice. It is because their products are over priced, they lock you in and their licensing contracts are a death trap. Corporations don't care what browsers their user can use. They just want one that works. That is why MS only has IE and most of the corporate world uses IE and most of all PC users in fact. IE was NOT picked for technical merits. It was picked because that is what MS put in their OS.

      UserLinux will limit choice by picking the default applications. That is it. UserLinux will not stop you or your company from using KDE or QT. If you want it, just type apt-get install kde and your done. IMO Linux is great as a server and ready for a corporate desktop. Why has Linux not had a larger growth in the corportate desktop? I think there are a few reason.

      Over priced commercial distros like Red Hat make Linux actaully MORE expensive then MS Windows. UserLinux wants to address this by having the IT industry split the cost of the process and making it very affordable/free to all.

      Linux distros have too much choice in packages that is just too much information for a corporate manager to assimilate and make a chioce. It is the managers, directors, VP and CTO's that make the final choice to use Linux and NOT the it workers like myself. With MS Windows and Mac OS X, the corporate guys do not have to worry about trivail things like what window manager to use, or what desktop or what web brosers or what ftp server or what ... With current Linux distros the corporate suits have to face all those choice and it is too much for them.

      For geeks like us, give us chioce and DO NOT take it away. For the corporate world, make the chioce for them and sell them an END PRODUCT.

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    153. Re:KDE is not to be ignored by 56ker · · Score: 1

      The question "Who cares really?" springs to mind.

    154. Re:KDE is not to be ignored by AstroDrabb · · Score: 1
      But why not let the admin make that choice? Why does Perens get to make that choice?

      It is almost NEVER the admin who makes the choice. The choice are made by managers, directors, VP's and CTO's. The admin and programmers like myself only get to IMPLEMENT the choices of the managers, directors, VP's and CTO's. Do admins get to choose what desktop is used in the corporate world with MS Windows or Mac OS X? No. And I bet that is one less decision that the corporate world will not miss having to make. Imagine company A standardizes on KDE and then some very important commercial applications comes out for Linux that could really help them save money. However, that aplications was written in GTK+ or using the GNOME API. Sure they could run it under KDE. Though it would not fit in with KDE and there would be interoperabilty problmes like drag-n-drop, cut-n-paste, RPC and others. So now that company will either have to not use that applications that could help their busines or do a costly and time comsuming switch to the other desktop.
      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    155. Re:KDE is not to be ignored by AstroDrabb · · Score: 1

      With wxWindows, there is no need for a commercial license fee to QT. wxWindows would be the perfect toolkit for UserLinux. One of the main points of UserLinux it to be FREE as in cost. Large IT industry corporations will all help fund the development efforts of UserLinux. Out of that funding they will get a FREE as in cost, Linux distro that they can develop their applicaitons for and offer their services on. QT takes away that whole FREE as in cost, situation. So those IT corporations that will be funding UserLinux will pay for UserLinux development and then have to turn around and have to pay to be able to develop on the platform that they funded. That doesn't make sense to me.

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    156. Re:KDE is not to be ignored by Coventry · · Score: 1

      The KDE folks are cranky because they want the money that is to be spent promoting and developing UserLinux to be spent on their project and not on Gnome.

      No... I bet the KDE folks are 'cranky' because they've spent years writing a HUGE and free desktop and application system, much larger than the kernel, and now are seeing a competiting project being standardized as the single default for a high profile attempt at a standard distro...

      Saying that the choice is there - like you and Bruce are both saying - doesn't work in this scenario as a way to say 'its ok' to the KDE developers. They've spent years working on this, emotions are going to be high, especially when this is a high profile standardization effort.

      Did anyone else read KDE's counterproposal? I meqan, here these guys had just been told they would be put out of the project - and their response is basicaly 'We'll Dive In and make KDE do things you never expected and integrate it in such ways that it's super attractive - we'll add features, etc!' Frankly, I found Bruce's response rather rude - even though he may not of meant it that way - he basically told them 'You can do all that work if you want, in fact, please do! But we won't use it.' Which is actually less painful than if he'd responded with 'No thanks, we'll do that sort of thing with Gnome.' - The latter, while curt, at least is clear cut; meanwhile by encouraging the KDE team to develop everything they offered and yet refuse to use it, Bruce has publicly thrown down a kind of guantlet - he's Asked them to do the work - but the gain could be very small, and if they don't do it, everyone gets to point and say 'see, they couldn't live upto their proposal anyway'.

      I know, I know, I'm probably reading too much into that sort of thing - and it's not like the KDE people have to do what he says - it's all open source software, and it's all about freedom!

      Two things, and then I'll shut up:

      - This debate, and the heated arguments and such, have been forseen for years - everyone who looked at the competing projects from the outside, objectively, knew that the 'competition' that was spuring them both forward, was also going to bite them in the arse.

      - The burgening market Bruce references, for priorietary software for linux desktops, is already out there - and some companies write for Gnome, others write for KDE. By making this descision Bruce has either A) put the KDE companies in a bad position, or B) relegated UserLinux to mediocrity by alienating a large, existing user base. Neither outcome is good.

      --
      man is machine
    157. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      > The thing is, you don't have to test for KDE and GNOME. If you write a GNOME program, test it with GNOME, and it will always work with KDE since if you run it from KDE it will still use the GNOME libraries. The same is true for the other way around.

      That is not so simple. The user still has to setup the interface "Look and Feel" (color and fonts for example) in two places, for example.

      This kind of thing will be true for every common facility used by programs. A Gnome program will use an Gnome address book. The KDE program will use the KDE address book, and both will store and read the data from diferente place and so on. Even for a "smart user" this is a nigthmare".

      Some argue Windows programs are bloated software. But having two frameworks (thousands of lines) installed in the same machine and doing the same things is what makes me feel Linux userland is a bloated platform.

      By the way, I prefer KDE.

    158. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      You consider yourself a Zealot? Sad...

      If you don't think of yourself as a Zealot, I wasn't talking about you.

    159. Re:KDE is not to be ignored by Jason+Earl · · Score: 1

      Yes, I read the KDE response to Bruce's choice of Gnome for UserLinux, and I also saw how it neatly dodged the primary problem with KDE. The problem with KDE is not technical in nature. Indeed, although Gnome/GTK probably has the edge when it comes to actual applications (especially if you include OpenOffice which Sun has closely allied with Gnome), KDE probably has the more elegant desktop and framework for creating applications.

      Unfortunately, the problem with KDE is, and always has been, licensing related. For example, if TrollTech would have switched to the GPL for their QT library before Gnome really got a foothold then the issue would be completely moot. There would be no Gnome, and KDE would reign supreme. However, TrollTech waited too long to make their switch, and by the time they had made the change Gnome was available under the more liberal LGPL. Now, when corporations like Sun, Novell, and the rest go fishing for a viable desktop they are faced with two choices. The first is the slightly more polished KDE that requires that you pay licensing fees for commercial development, or you could go with Gnome and create either Free Software or commercial software without any fees.

      Not that Bruce's choice is solely a matter of licensing. The fact that you can create commercial software without paying licensing fees is a huge selling point for Gnome, but that's hardly the only Gnome advantage. For whatever reason Gnome/GTK also has the edge when it comes to actual applications.

      The fact of the matter is that the KDE folks are especially mad about UserLinux because it represented a last slim chance to reverse their current fortunes. KDE is in a bad way. Sun is pushing Gnome like there is no tomorrow. And Novell has purchased SuSE, the one Linux distributor that was willing to pour money into KDE. That leaves SuSE's KDE developers under the direction of Nat Friedman formerly of Ximian.

      The money is all flowing towards Gnome, and now it appears that Bruce Perens is going to raise a fairly substantial chunk of change and it is going to end up supporting Gnome development as well. If you are a KDE developer that has got to hurt. Instead of railing on Bruce what the KDE folks need to do is address some of the issues that he raised. Most importantly they need to keep in mind that his decision was not based solely on technical issues (although those exist as well), but that the licensing issues matter as well.

      KDE has the lead on the Linux desktop now, but the tiny KDE marketshare isn't going to mean squat going forward. There is so little Linux being used on the desktop that any difference between Gnome marketshare and KDE marketshare is statistically insignificant. The folks pushing for Linux on the desktop have goals of several orders of magnitude more Linux use than there is now.

    160. Re:KDE is not to be ignored by Jason+Earl · · Score: 1

      The good news is that with the Novell/SuSE merger a good portion of the KDE hackers are going to be working for Nat Friedman (formerly of Ximian). My guess is that the former SuSE KDE hackers will soon find themselves spending a good deal of time making KDE compatible with Gnome.

      And it's not just Bruce that is making this same hard decision. Pretty much the entire Linux industry is lining up behind Gnome.

    161. Re:KDE is not to be ignored by spacecowboy420 · · Score: 1

      seriously....

      --
      ymmv
    162. Re:KDE is not to be ignored by KewlPC · · Score: 1

      I realize that UserLinux is based off of Debian. My question is, why would corporate KDE users want to get a Debian-based distro that doesn't include KDE on the installation CDs when they can just go with regular Debian (which I'm assuming puts KDE on the installation CDs)?

      People are forgetting that corporate users of KDE will have many systems that need KDE installed on them. By not having KDE on the installation CD, they're creating more work for the sysadmins, who now, instead of merely selecting an "Install KDE" option when installing the OS, have more steps to go through, which makes them more inclined to go with something besides UserLinux.

    163. Re:KDE is not to be ignored by Tukla · · Score: 1
      I think QT is a better toolkit than GTK.

      From what I've been seeing, UserLinux is being developed by the Pointy Haired Bosses for the Pointy Haired Bosses. Technical superiority isn't a consideration.

    164. Re:KDE is not to be ignored by cout · · Score: 1

      I love it when a post gets modded down for being a troll when someone does little more than point out a flaw in logic.

    165. Re:KDE is not to be ignored by nathanm · · Score: 1
      To each and every corporate KDE user, UserLinux has become effectively worthless in one fell swoop.
      If a corporation is already using Linux and KDE, UserLinux isn't intended for them. It's being developed to attract corporations who aren't using Linux on the desktop yet.
    166. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      If true, this means GNOME wants to kill all gays.

      Therefore GNOME is Hitler.

    167. Re:KDE is not to be ignored by Anonymous Coward · · Score: 0

      Great. Finally I know why I love KDE.
      (Well, but I don't like goats ...)

    168. Re:KDE is not to be ignored by Scudsucker · · Score: 1

      I don't hear you being righteously indignant about Xandros or Linows not including GNOME...

      Huh, maybe because the topic is about KDE and UserLinux, not those other two?

      Hypocrite.

      Dumbass.

    169. Re:KDE is not to be ignored by fm6 · · Score: 1

      Not to mention that MDI is the stupidest GUI concept since Bob. Why does anybody need a window inside another window?????!!!!! Navigating MDI applications is a pain, unless the developer took the trouble to provide a set of tabs or icons or something -- which they have to program themselves, since MS forgot to provide anything.

  2. UserLinux == Great Idea by Anonymous Coward · · Score: 5, Funny

    Except the User part because there won't be any.

    1. Re:UserLinux == Great Idea by Anonymous Coward · · Score: 0

      I really think Peren's needs to replace python with C#, and MySQL with Mono. Yeah then I might be the trick giving this distro commercial viability. Yeah... that's the triick... make linux commercially viable... Yeah.. Mono... yeah... C#..

    2. Re:UserLinux == Great Idea by Unregistered · · Score: 1

      NoUserLinux? UserlessLinux?

  3. Why Gnome? by autopr0n · · Score: 4, Insightful

    Isn't KDE a lot smoother and more consistent over all then Gnome? I mean Linus uses it. Especially for business apps, KDE seems like a more natural choice.

    --
    autopr0n is like, down and stuff.
    1. Re:Why Gnome? by Anonymous Coward · · Score: 0

      KDE is clunky and slow, even compared to the Windows XP interface (on my P3-500). Gnome too. GTK apps are always nice and quick though.

    2. Re:Why Gnome? by Anonymous Coward · · Score: 0

      And, as the KDE advocates note, KDE is a far more common default - among all distros, not only those aimed at new users.

    3. Re:Why Gnome? by Hard_Code · · Score: 2, Insightful

      Exactly...KDE seems much more seamless and integrated end to end which is exactly what you want the user experience to be for business users who don't care about flavors of their toolkit or how many bindings for sparklers you can hang off it. KDE seem leagues ahead of GNOME.

      --

      It's 10 PM. Do you know if you're un-American?
    4. Re:Why Gnome? by Enucite · · Score: 2, Insightful

      KDE is a common default for most distros...
      Except among those targetting enterprise customers.

      Which is the same group UserLinux is going for.
      There's a reason Gnome is more popular for business-focused distros.

    5. Re:Why Gnome? by Anonymous Coward · · Score: 0

      1. Why does the fact that "Linus uses it" prove that it's smoother and more consistent?

      2. I find the dependency on third party qt quite annoying.

      3. (but this is merely personal) It just doesn't fit with me. If I had to choose between Gnome and KDE, I'd choose the first, but I use neither. But there's probably hundreds of pages on /. alone that are filled with the "I use xxx because it's the best" stuff. That's useless and pointless.

    6. Re:Why Gnome? by Anonymous Coward · · Score: 0

      Note that if you are using Redhat, they screwed up KDE - you have to use a non-redhat-origin KDE to get decent KDE performance.

    7. Re:Why Gnome? by damiam · · Score: 1
      Isn't KDE a lot smoother and more consistent over all then Gnome?

      No. I may be biased as a GNOME user, but just about everyone I know thinks that GNOME is much more visually consistant (thanks to the HIG) and good-looking (thanks to tigert, jimmac, and the lack of Keramik) than KDE. Practically all of the best-of-breed business apps (Mozilla Firebird, OpenOffice, Gnumeric, Evolution, Planner, Gnucash, etc.) are GNOME apps or GNOME-integrated. KOffice is a nice effort, and I hope it does well, but it's currently not quite ready for prime time corparate use.

      A lot of people feel that KDE is technically superior, and they prefer the power and configurability that KDE offers. KDE is much more of a hacker's desktop, and that's probably why Linus uses it. That said, UserLinux doesn't want a hacker's desktop, they want a corparate desktop. GNOME probably fits that bill better. GNOME probably fits that bill better.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    8. Re:Why Gnome? by merlin262 · · Score: 1
      I'd have to argue that GNOME/GTK has some of the more major applications:

      Mozilla
      Gaim
      Evolution
      XChat2
      Gimp
      GnuCash
      XMMS

      There are of course some other major Linux applications out there, but most, from what I can tell, are GTK apps. The other major apps either use their own toolkits(OpenOffice), or don't use a toolkit at all. Before I hear the flames, I know there are KDE replacements for all of those applications, but the GTK versions are arguably the more popular.

    9. Re:Why Gnome? by Captain+Rotundo · · Score: 1

      I don't use KDE at all so take this with a huge grain of salt. But GNOME is so consistant that usability and consistancy seem to be the driving force for the entire desktop.

      Bruce choose GNOME for one reason, the LGPL.
      This makes it far more palatable for proprietary developers (they get the entire UserLinux platform and don't have to worry about licencing Qt down the road if the want to sell an app).

      Also I think GNOMEs unified vision of simplicity and usability gives it more corporate credibility. From what I hear KDE seems to strive to make Konqueror into the next emacs, making sure you can do anything with it that you could possibly want (or in many cases NOT want :)

      I am sure KDE is fine, but I use GNOME full time of several machines and it is very friendly and usable, so I can't see the complaints that KDE is "better" I don't claim GNOME is "better" I just happen to like it more

    10. Re:Why Gnome? by Anonymous Coward · · Score: 0

      "Exactly...KDE seems much more seamless and integrated end to end which is exactly what you want the user experience to be for business users who don't care about flavors of their toolkit or how many bindings for sparklers you can hang off it. KDE seem leagues ahead of GNOME."

      I appreciate that this is what a lot of users want, but I hate "integrated" desktops. Every time I'm forced to use KDE, Gnome or Windows I'm left wondering what the system is doing behind my back; "Why was this application started when I didn't want it to". "This is a web browser isn't it? Not a file manipulator". "Why isn't the email program and usenet program integrated? Everything else is, this would actually make sense."

      No. Give me a no-frills GUI any day. No wonder mom-and-pop users are confused. I've owned, programmed and used computers all my life and I'm confused.

    11. Re:Why Gnome? by steeviant · · Score: 1

      How is GTK+ not "third party"? Did you write it entirely by yourself?

    12. Re:Why Gnome? by RPoet · · Score: 1
      From what I hear KDE seems to strive to make Konqueror into the next emacs, making sure you can do anything with it that you could possibly want (or in many cases NOT want :)

      You heard wrong. Konqueror is three things:
      • A web browser -- standards compliant and getting close to matching the features of Mozilla, but with a fracture of the lines of code.
      • A file manager -- move and copy files, change names, make directories, standard stuff, but it's network transparent, so you could be working on your harddrive or a remove SSH or WEBDAV server, konqueror doesn't care. All done with components, no bloat at all.
      • A document viewer -- It can of course view many kinds of documents (through plugin components, so there's no bloat), but it's all read-only, nothing like Emacs at all.
      So as you can see, there's no comparison with Emacs at all (ok, emacs can do all that konqueror can, but that is true for ANY application ;).
      --
      "Oppression and harassment is a small price to pay to live in the land of the free." -- Montgomery Burns.
    13. Re:Why Gnome? by Anonymous Coward · · Score: 0
      Isn't KDE a lot smoother and more consistent over all then Gnome? I mean Linus uses it. Especially for business apps, KDE seems like a more natural choice.

      If Linus jumped over a cliff would you follow him? KDE == old and busted. Gnome == New Hotness.

    14. Re:Why Gnome? by benjamindees · · Score: 1
      There's a reason Gnome is more popular for business-focused distros.

      Yeah, and it's called 'vendor lock-in'.

      Gnome is notorious for 1) never being completely *done* and 2) changing radically every couple of years.

      Does this sound like anyone else we know? 'Standardising' on Gnome just causes Unix Balkanism all over again. Hell, now even some of the players are the same.

      --
      "I assumed blithely that there were no elves out there in the darkness"
    15. Re:Why Gnome? by 0x0d0a · · Score: 1

      Bizarre. I feel almost the opposite.

      I may be biased as a GNOME user,

      I've used GNOME more in the past, and use GTK+ based apps, but I'm not a huge fan of using GNOME. If I *just* had the GNOME gaim applet for gkrellm, I'd drop the GNOME panel as well.

      good-looking (thanks to tigert, jimmac, and the lack of Keramik) than KDE.

      Mmf. I also prefer the GNOME-style slightly organic icons, but I think more people I know prefer the more Windows-like KDE icons.

      Practically all of the best-of-breed business apps (Mozilla Firebird, OpenOffice, Gnumeric, Evolution, Planner, Gnucash, etc.) are GNOME apps or GNOME-integrated.

      Yes. Although it's depressing that Firebird and OO don't use GTK+.

      and they prefer the power and configurability that KDE offers.

      I think that GNOME 2 made a lot of functionality invisible. GNOME 1 had emacs-style keybindings and user-rebindable accelerators right in your face, and in GNOME 2 you need to flip a config file option to enable these. Doesn't mean that it went away, though.

      KDE is much more of a hacker's desktop, and that's probably why Linus uses it.

      I dunno -- I'd say it's an even split. Alan Cox uses GNOME. Probably neither uses either if they're testing kernels to avoid reboot time.

    16. Re:Why Gnome? by 0x0d0a · · Score: 1

      And, as the KDE advocates note, KDE is a far more common default - among all distros, not only those aimed at new users.

      Okay, this is going based on memory of the major distros:

      KDE:
      SuSE
      Mandrake

      GNOME:
      Debian
      Red Hat

    17. Re:Why Gnome? by Natalie's+Hot+Grits · · Score: 1

      There is no more RedHat as a major distro. They got rid of their standard desktop OS... So redhat is no longer a major player in the linux desktop market.

      So there is: SuSe, Mandrake, Debian, Gentoo, Slackware for desktop Linux OS's. Maybe you can claim Fedora is, but that project is already as good as dead. I know SuSe and makdrake uses KDE, Debian uses either, and both integrate extremely well, and gentoo and slackware I don't know their default, but they both ship with the latest KDE...

      So.. really there aren't any big named GNOME desktop Linux vendors left... (unless you count Sun and Novell, which have yet to ship a GNOME desktop linux distro in any significant volume)

      In other words, you are talking like GNOME is deployed on the two largest distributions as default, when in fact, it isn't.

      --
      Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.
    18. Re:Why Gnome? by SoTuA · · Score: 1
      gentoo and slackware I don't know their default, but they both ship with the latest KDE...

      And the latest gnome too. What does this have to do with your argument?

      And what's this about "no redhat desktop"? The distros that target corporate environments (except for SuSE) use Gnome. Wich is where UserLinux wants to fit in.

  4. Probably a good call by SoIosoft · · Score: 4, Insightful

    The inclusion of two desktop environments, no matter how good they might be, will be confusing to ordinary end users. There might be some argument for including KDE and leaving GNOME out, but I feel that GNOME is less CPU-intensive and the included applications are a little better. The best argument for KDE would be that it would make the transition from Windows easier because it is so similar. That shouldn't be an issue, though. Nobody worries about users switching from Windows to the Mac being confused. It's a good call.

    --
    Help me. I've been modbombed by a few people with entirely too much time on their hands.
    1. Re:Probably a good call by Anonymous Coward · · Score: 0

      Why include *any* desktop environment at all in the initial UserLinux installation? UserLinux could distribute a GUI-less base distribution disk that would be ideal for server installations, or form the base for a GUI installation. On another disk(s) could be distributed one or more GUI installations. The base install need only have some standardized means to work with whatever GUI the user or industry wants to use.

      UserLinux (if I read correctly) is supposed to be configurable for different industries, so it should be made easy to install whichever GUI best fits that industry's purpose. The IT industry may prefer to use GNOME, but a business that does mostly word processing might prefer KDE.

      The developers of each GUI would be made responsible for integrating their projects into UserLinux, based on a UserLinux standard.

      If UserLinux is meant to be used by business, there shouldn't be any irrelevant, miscellaneous apps included (as are now in most Linux distros), so maintaining a different GUI for UserLinux probably would not be as difficult as it may at first seem.

    2. Re:Probably a good call by TechnoWeeniePas · · Score: 1

      I must disagree...I mean look at something like XP. It is widely used and you have your choice between XP mode or 9x mode. There hasnt, as far as Im aware, been a huge amount of trouble cause by this at all to the end user.

    3. Re:Probably a good call by leandrod · · Score: 1
      > The inclusion of two desktop environments [...] will be confusing to ordinary end users.

      Not necessarily so. We have 300K users in the Sao Paulo Telecentros, and even if we do install KDE we know only the tech people who already knew KDE actually use it. All the end users have been presented with Gnome only, and they simply don't care about exploring an alternative. We will probably even exclude KDE from the CD we are preparing, in order to open the way to apps.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    4. Re:Probably a good call by AssClown2520 · · Score: 2
      I must disagree...I mean look at something like XP. It is widely used and you have your choice between XP mode or 9x mode.

      That is a pretty large over simplification. That is a graphical eye candy change for XP. This is more like a choice between XP & 98 all together. I have to agree with the original post and Bruce Perens letter. It is probably a good idea. Not so much from the enduser stand point but from a distrubution management standpoint.

      Personally, I like KDE better, but I am not the target user of UserLinux

    5. Re:Probably a good call by Jad+LaFields · · Score: 1

      While I'm not going to agree or disagree with your assessment of the two desktops, I have to say that you are quite correct about how having two different desktops is confusing to ordinary users.

      Just a couple of months ago I made my first plunge into the world of Linux with Mandrake 9.1, which I downloaded because I heard it was "newbie-friendly". When I got to the point in the installation when I was asked which user interface I would like to default to, I realized I had no idea what they were talking about. I literally chose KDE because I liked the sound of its name better (gnomes make me think of stupid lawn ornaments). After using KDE for awhile I gave Gnome a spin, but since I couldn't find any major improvements in it from KDE, and I had already gotten used to KDE, I stuck with my first choice. Maybe I'll go back and give Gnome a more serious look someday, but I'm too busy at the moment.

      So anyway, I think the point I'd like to make is that for most users, getting more than one choice only make sense if the choices are significantly different. If some magical OS included both the Windows 2k UI and the MAC OSX UI, the user would be able to notice the differences between the two pretty quickly (flashy vs. non-flashy for example) and make a choice. But while there may be significant difference in KDE's and Gnome's toolkit thingy, on the surface there's not enough difference. So while I may disagree with UserLinux's specific choice (and mostly out of ignorance), I think they have the right idea overall.

      --
      [SIG] It's like putting a moose in the blender -- a recipe for disaster!
    6. Re:Probably a good call by demachina · · Score: 4, Insightful

      This decision has NOTHING to do with "confusing ordinary end users". In the enterprise the IT department would pick the desktop they prefer then install, configure and customize it. The user is unlikely to ever encounter the choice.

      This is an unfortunate decision on the part of Bruce and UserLinux if they follow through with it. It will most probably halve the number of developers and users that will even consider this distro. They might argue they don't have the resources to support both desktops but since they are halving the number of contributors they have they aren't coming out ahead on the available resources equation by making this silly choice.

      It really conveys that, rather than maintaining an open mind, and supporting both desktops like just about every other distro that some people decided to play favorites for their favorite desktop and ended up telling everyone who disagrees to go to hell.

      One compelling argument for Qt that I'm not sure has been made on the UserLinux list is its going like gangbusters in the smartphone space and if you are targeting the enterprise you really desktop apps and phone apps with common heritage. Microsoft does.

      The community really needs to find a replacement for Red Hat/Fedorea that is not entangled with the whims of a corporation more concerned with its stock price than its users. We also need a distro that has the kind of critical mass and corprate support Red Hat has. UserLinux sounded like it might be the ticket but at this point it appears to be yet another fracture inducing distro.

      I spend a lot of days wishing the whole open source community would learn to work together, like the Linux kernel developers manage to do for the most part, but it seems to be a lot more fun to fork everytime there is a decision point so every big ego can have a project of its own to be the boss of.

      --
      @de_machina
    7. Re:Probably a good call by Anonymous Coward · · Score: 0

      Indeed its a good call. There are already three widget sets, OO, Mozilla and Gnome. Why would we want a fourth. And there is a good selling point. All your software can be proprietary. You don't have to give anything back to the community. The downside is you won't be able to use an OO spreadsheet part, not yet anyways. Give us a couple of years.

      Derek

    8. Re:Probably a good call by Dalcius · · Score: 1

      This is pretty damn simple.

      What Linux needs is not a new selection of packages.
      This is what distros are for.

      Linux is all about choice. What companies need, instead of being told what desktop to use to comply with everyone else, is a standards base that *everyone* can comply with if they wish.

      Maybe that isn't what UnitedLi^WLinuxStanda^WUserLinux is aiming for, but that's what we need. Going about cutting off an entire desktop isn't the way to make the Linux world friendly.

      Let me say this again.

      Forced standards are better than no standards [Microsoft], but Open and free and non-excluding standards are best.

      For example, Red Hat is pretty gnome centric. Is excluding the biggest Linux distributor in the US really a smart idea if we want Linux to compete against the big dogs like Microsoft?

      Let's not make this the land of one desktop or one browser or one this or that. Have we not learned our lesson from taking this shit from Microsoft?

      Let's make a standard that helps applications/desktops/etc. interoperate. Drag-n-drop, clipboard, installer/package manager interoperation, etc.

      This pick-a-favorite won't work. You folks haven't learned. Homogenizing Linux will never be the answer.

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    9. Re:Probably a good call by furballphat · · Score: 1

      My story of choosing a desktop enviornment is just as trivial. When I installed my Redhat 9 system, Gnome was the default. I thought it was ok, but nothing special. A few days later I got adventurous and decided to fire up KDE. I switched to KDE soley because there is an option to turn num lock on at startup. I've looked at Gnome a few times since then, but the file manager is just terrible.

    10. Re:Probably a good call by 10Ghz · · Score: 1

      Lindows is a newbie-oriented distro that uses KDE. They also use GNOME-apps where appropriate (GAIM for example) and it doesn't seem to "confuse" their users one bit.

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    11. Re:Probably a good call by anarxia · · Score: 1

      The problem is not the look&feel it's the programming API. QT and GTK are completely different to program and they are trying to avoid that (and the qt licence issue for commercial applications). You might disagree with their choice but at least try to understand their reasoning first.

    12. Re:Probably a good call by Elektroschock · · Score: 1

      Nonsense, the default configuration may look similar, but you can configure the KDE desktop to look what you want it. Gnome is great but not for the desktop. Bruce simply ignores the market. RedHat made the same mistake but outside RedHats market only few users prefer Gnome.

    13. Re:Probably a good call by Net_Wakker · · Score: 1
      We also need a distro that has the kind of critical mass and corprate support Red Hat has.

      SuSE. Very big in Europe, both in corporations and governments. Really nice support, very complete, they are for KDE what RedHat is for Gnome (are they still, now that they've dropped the desktop?), they're longtime partners with the likes of IBM and now that they've been acquired by Novell they have a worldwide presence and sales-apparatus that I don't think RedHat can beat. As far as critical mass and support is concerned, I really think SuSE's got RedHat cornered. I only hope (to stay semi on-topic) that the Novell/SuSE/Ximian-combination will not kill-off KDE development.
  5. Re:wtf? by drinkypoo · · Score: 4, Informative

    user mode linux != userlinux. HTH, HAND.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  6. I am reminded of the PERL mantra by cluge · · Score: 3, Insightful

    There is more than one way. Anyone that insists that there is only one way, and that is their way, is probably wrong. KDE has advatages over GNOME, and vice versa. Let the flame wars begin - err continue.

    AngryPeopleRule

    --
    "Science is about ego as much as it is about discovery and truth " - I said it, so sue me.
    1. Re:I am reminded of the PERL mantra by frantzdb · · Score: 2, Insightful

      I agree. There is more than one way to make a Linux distro. One such way is to include only one desktop environment.

    2. Re:I am reminded of the PERL mantra by Our+Man+In+Redmond · · Score: 3, Funny

      Anyone that insists that there is only one way, and that is their way, is probably wrong.

      Or named Guido.

      (Don't shoot me! Don't shoot me! I use Python too!)

      --
      Someone you trust is one of us.
    3. Re:I am reminded of the PERL mantra by bfields · · Score: 4, Insightful
      There is more than one way. Anyone that insists that there is only one way, and that is their way, is probably wrong.

      Oh, yes, I do so enjoy the diversity of choices taken by application writers. It's wonderful, isn't it, that some may choose to allow me to exit their application with ctrl-Q, some with alt-Q, some with just q, some with :q, and some with Ctrl-X Ctrl-C?

      And who couldn't appreciate the joy of searching for documentation in help menus, man pages, info pages, and in text, html, and xml files under /usr/share/doc/?

      It's wonderful, isn't it, having the opportunity to learn a new scripting language and interface when it comes time to extend a new application? And who but the most small-minded panderer to the lowest common denominator could not appreciate the flowering in diversity of configuration methods? (How dull my life would be if I lacked the intellectual stimulation provided to me by the opportunity to puzzle through which of gconf, .Xresources, .cshrc, or .xsession is responsible for the fonts in my terminal windows!)

      Ignore those so-called user-interface specialists and their petty concerns about "consistency" and "usability". It's All About Choice, after all!

      --Bruce Fields

    4. Re:I am reminded of the PERL mantra by ultrabot · · Score: 1

      There is more than one way. Anyone that insists that there is only one way, and that is their way, is probably wrong.

      And you think that Perl is succesfull that it proves the ideal of one way wrong?

      Depends on how you measure success, I guess...

      --
      Save your wrists today - switch to Dvorak
    5. Re:I am reminded of the PERL mantra by Linux_ho · · Score: 2, Insightful

      There is more than one way. Anyone that insists that there is only one way, and that is their way, is probably wrong. KDE has advatages over GNOME, and vice versa.

      Which is why Python will be the supported scripting environment for Userlinux. Not perl, not Ruby, not TCL/TK. Welcome to the philosophy that made Apple computers the number-one choice for user friendliness: There will be only one way to do things, and it will be as intuitive and uncomplicated as possible. Not that I'm saying it's the right way to go, I'm just pointing out that it's a valid way of building a system that has worked in the past.

      --
      include $sig;
      1;
    6. Re:I am reminded of the PERL mantra by Pseudonym · · Score: 2, Funny
      Oh, yes, I do so enjoy the diversity of choices taken by application writers. It's wonderful, isn't it, that some may choose to allow me to exit their application with ctrl-Q, some with alt-Q, some with just q, some with :q, and some with Ctrl-X Ctrl-C?

      I don't know what you're talking about. Ctrl-Z-kill works fine for me no matter what editor I use.

      I do tend to lose data sometimes, though.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    7. Re:I am reminded of the PERL mantra by Anonymous Coward · · Score: 0

      There is more than one way.

      Yes, there are two ways: Right and Wrong.

    8. Re:I am reminded of the PERL mantra by Dalcius · · Score: 1

      Hrm...

      Well, it doesn't take a genius to figure this out, but let me help apply the parent of your post to the subject at hand:

      He's trying to say that going KDE is not the answer.

      Making a specification that says quit is "CTRL+Q" is. Making a specification that says "this is how you handle a clipboard" is. Making a specification that says "this is how to handle drag-n-drop" is. Making a specification that says "program installations should be supported through RPM, .deb, .ebuild, etc." files is.

      Homogenizing Linux will never be the solution. If you wankers want a single browser, go back to Microsoft. I'll be here in the Linux world where we've figured out that there are no "best" applications. Everyone likes it their own way, and I'll be damned if our "community" standardizes on a single desktop.

      Sorry for the flame, I honestly am.

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    9. Re:I am reminded of the PERL mantra by Osty · · Score: 2, Informative

      Making a specification that says quit is "CTRL+Q" is. Making a specification that says "this is how you handle a clipboard" is. Making a specification that says "this is how to handle drag-n-drop" is. Making a specification that says "program installations should be supported through RPM, .deb, .ebuild, etc." files is.

      Specifications don't mean anything if they're not enforced. I can make a specification that says I get to have root on your system, but unless everybody gives me root, it doesn't mean anything. Given the distributed nature of open source development, and that anybody can start their own project to reinvent the wheel any time they want, just writing a specification isn't enough. You have to write the specification, get people to support it (or do it yourself), and then choose to only distribute those applications that support the specifications in your distribution. Choosing KDE over GNOME is implicitly saying that the specification is to use KDE's guidelines and development practices rather than GNOME's. That doesn't mean that KDE does have a coherent style guide, but if they don't now they really should.


      I'm sure they're going to go a step further than just choosing KDE over GNOME, and only ship one office suite, one gui text editor, one calculator, etc. If you want a different desktop environment, office suite, text editor, etc, then go ahead and install something else. However, you're no longer the target demographic for UserLinux. Use a more appropriate distribution like Debian, Gentoo, Mandrake, SuSE, etc.

    10. Re:I am reminded of the PERL mantra by disntrstd · · Score: 1

      Are you being sarcastic?

    11. Re:I am reminded of the PERL mantra by Dalcius · · Score: 1

      Right, but this is about bringing enterprise to Linux, not about creating a new distro -- or at least that was my impression.

      Getting enterprise behind one "distro" (a collection of packages) will effectively hijack a lot of the effort that goes into Linux to favor a single distro. This will work, don't get me wrong. All of my apps will still be there, stronger than ever, due to more users in general.

      But instead of picking favorites and letting enterprise run with it by developing only for certain environments, etc., and effectively putting another desktop in a small minority, we can standardize on basic things: general interface concepts, configuration and installation methods, navigating the hard disk and using the clipboard, etc. We can KEEP KDE and GNOME and all the major browsers and all the major mail clients and all the major Xs and Os going -- as long as they play well with eachother and don't confuse the hell out of users.

      To word it in a sentence: Linux needs to be predictable and it needs to interoperate. Linux doesn't need a flagship desktop environment.

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    12. Re:I am reminded of the PERL mantra by Osty · · Score: 1

      But instead of picking favorites and letting enterprise run with it by developing only for certain environments, etc., and effectively putting another desktop in a small minority, we can standardize on basic things: general interface concepts, configuration and installation methods, navigating the hard disk and using the clipboard, etc. We can KEEP KDE and GNOME and all the major browsers and all the major mail clients and all the major Xs and Os going -- as long as they play well with eachother and don't confuse the hell out of users.

      Two issues here. First, enterprises don't like to develop for an infinite number of platforms. The test matrix is impossible. That's why you see stuff like Oracle supporting Redhat and SuSE (?), but not Slackware or Debian. If you can get Oracle running on the latter, great, but you're not supported. Second, the key phrase you said is "don't confuse the hell out of users". That's exactly the problem right now. A secretary doesn't care if she's using GNOME or KDE, but she's going to be confused if you tell her, "Now pick your desktop environment, and then you can get to work". The IT guys will standardize on one environment, one office suite, etc. Why not have a distro that does all of that work for the IT guys out of the box?


      The problem of enterprise standardizing on one distro happened years ago, when many businesses started supporting Redhat rather than Linux in general, and guess what? Linux is still around and kicking, and Redhat isn't the only option.


      Linux doesn't need a flagship desktop environment.

      I completely disagree.

    13. Re:I am reminded of the PERL mantra by fmaxwell · · Score: 1

      Homogenizing Linux will never be the solution. If you wankers want a single browser, go back to Microsoft. I'll be here in the Linux world where we've figured out that there are no "best" applications. Everyone likes it their own way, and I'll be damned if our "community" standardizes on a single desktop.

      And it's attitudes like yours that have done so much to keep Linux from being the OS choice for homes and businesses all over the world. Right now, out of the box, Windows is a far superior choice for most users because it doesn't include four browsers, six e-mail clients, two completely different desktops, two SMTP servers, six text editors, three FTP clients, etc. That means that it can be supported -- whether by an IT department in a business or by a computer-savvy family member. It means that a user can go from one system in an office to another relatively easily. It means that a business can deploy a timekeeping web app and not have to test it on four different browsers. It means that IT doesn't have to roll out patches for four browsers, six e-mail clients, two completely different desktops, two SMTP servers, six text editors, three FTP clients, etc.

      With Windows, everyone starts off with the same tools. More computer-savvy users can replace the browser, editor, FTP client, etc. when they are ready to. That's the way that it should be. If you don't know how to find, download, and install software, then you aren't ready to make choices about it.

      The real world is people using computers to get their jobs done. It's not turning the question of which GUI to use into a religious discussion.

    14. Re:I am reminded of the PERL mantra by 0x0d0a · · Score: 1

      Which is why Python will be the supported scripting environment for Userlinux. Not perl, not Ruby, not TCL/TK.

      Facinating.

      I'd actually say that this is a good choice (and this is coming from someone who's much more familiar with perl than python).

      Perl is, frankly, unmaintainable. It's just so damn useful for text processing that it's easy to shove in places, but I think that in the long run, folks are better off using a different language. Ruby isn't used that much, and TCL has been going a long slow fall from grace for a long time.

      Python really is a good choice.

      Of course, I'm sure that there will be a few crucial systems that rely on perl that will be a pain to replace.

    15. Re:I am reminded of the PERL mantra by Dalcius · · Score: 1

      And it's attitudes like yours that have done so much to keep Linux from being the OS choice for homes and businesses all over the world. Right now, out of the box, Windows is a far superior choice for most users because it doesn't include four browsers, six e-mail clients, two completely different desktops, two SMTP servers, six text editors, three FTP clients, etc.

      Congratulations for reading more into my post than I said.

      Listen to me again, maybe you'll understand where I'm coming from. Good defaults (read: GNOME) are wonderful. Keep them. Any good commercial distro will present a unified system so as to avoid user confusion. Doing otherwise is retarded.
      Understand now that we're on the same side on this one?

      The problem, however, is that some folks think that Linux, at the community level -- as opposed to the distro level -- need to select a unified front, and this is simply not true. What we need is for our current systems to interoperate, to breed choice with cooperation. Provide methods for GNOME applications to work feasibly on KDE without much effort on the side of the application developer.

      It's quite possible to load a QT based program while running GNOME. It's quite possible for KDE folks to set up a wrapper layer to import GNOME applets into KDE. It's quite possible to create a wrapper for clipboard and drag-n-drop functionality.

      It's even easier to present a unified front as far as interfaces go. Application menus, shortcuts, installations, all of these things can be streamlined.

      Let a company pick their own distro -- IT departments exist for a reason. Let the distro makers pick a unified front of apps. But don't try to steer a community to one environment and one browser and one email client -- it's not necessary. Keeping choice in Linux isn't the stupid whim of a zealot, it's a very realitic goal. Companies aren't going to do this -- they make more money by owning the entire market. The Linux community isn't driven by a company, however, and we don't have to be to attract corporations.

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    16. Re:I am reminded of the PERL mantra by Dalcius · · Score: 1

      First, enterprises don't like to develop for an infinite number of platforms. The test matrix is impossible.
      Agreed.

      ---
      A secretary doesn't care if she's using GNOME or KDE, but she's going to be confused if you tell her, "Now pick your desktop environment, and then you can get to work".

      Your problem is that you're confusing what I said with what a distro does. I'm talking about the community level, not the distro level -- sorry if I wasn't clear.

      A distribution chooses defaults to present a unified front. Doing otherwise is foolish as you confuse the hell out of users.

      But to try to steer the Linux community to embrace and develop for GNOME and drop KDE is equally foolish. I think the more intelligent solution would be to further integrate the two (wrappers, abstraction layers, etc.). Enable an application written for GNOME to work within KDE with a respectable degree of integration. Take the applications that are heavily integrated into a given desktop (nautilus, for example) and standardize them so that GNOME and KDE core apps work/feel the same.

      ---
      The problem of enterprise standardizing on one distro happened years ago, when many businesses started supporting Redhat rather than Linux in general, and guess what? Linux is still around and kicking, and Redhat isn't the only option.

      First I'll remind you that companies such as IBM and many many many countries are going with SuSE. Red Hat is US centric.

      Second, Linux hasn't hit its prime, especially on the desktop, which, as you'll recall, is the entire point of this article: desktop Linux, or more accurately, environments. Now I'm not suggesting that KDE will lose any developers if enterprise moves in and really pushes GNOME (of which I'm a user and huge fan). What I am suggesting is that we can put effort behind both desktop environments without sacrificing simplicity and integration.

      --
      ~Dalcius
      Rome wasn't burnt in a day.
  7. Options are good. by ActionPlant · · Score: 1, Interesting

    I don't primarily use KDE, but I still like the idea that should I want it, I can have it. I do use Gnome, but I like just knowing it's not my only option, even if I never get around to using KDE. Although it's not the end-all be-all (in my opinion), it would still be a mistake to not include it.

    Damon,

    --
    http://actionPlant.com
    1. Re:Options are good. by D-Cypell · · Score: 2, Insightful

      Sometimes options are not good. Particually if you want to reach out to slightly less technical users.

      Lets not forget that anyone that wants to use this distro with KDE should be able to compile and install it.

      There are als many other distros that come with both.

    2. Re:Options are good. by ActionPlant · · Score: 1

      However, in a future distro I see no reason a person can't have the option to switch between them, much like logging out and then back in with Windows, which will load completely different settings for a different user. Yes, our two major shells in Linux do the same thing, but I feel doing a recompile on the fly via an option from within the gui isn't a far stretch. Could be interesting.

      --
      http://actionPlant.com
    3. Re:Options are good. by cant_get_a_good_nick · · Score: 1

      Options are good if you have specific needs that are served by the differentiation and you can make a careful analysis and pick the right one. But if you can't do this, you just sit there, try to make an educated guess, realize you have no clue, make a decision anyway, and then wonder whether you made the right decision.

      For most users, they don't have any reason to choose one or the other.. They'll ask their friends, who'll tell them about licenses and C++ vs. C and programming models... none of which make any difference to end users. It will just confuse them and distract them from getting their work done.

      This is just the desktop, not the apps. I'm sure they'll shit Qt libs. And I'm sure you could install KDE if you wanted too. THis is just the default.

    4. Re:Options are good. by ActionPlant · · Score: 1

      I wish there were another way, though. Perhaps just include it and (like we can do currently) have the user select during the install based on a couple of dumbed-down little write-ups on the pros and cons of each?

      Reason why, KDE DOES rock, and it's friendly competition between programmers for the different shells that continues to promote improvement. If this releases without KDE that's a big incentive for GNOME programmers to rest a bit on their laurels (no offence to them whatsoever...I realize this is open-source and pretty much all volunteer anyway).

      Damon,

      --
      http://actionPlant.com
    5. Re:Options are good. by damiam · · Score: 1
      I'm sure they'll shit Qt libs

      Freudian slip?

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
  8. Does that mean they worked for nothing? by Anonymous Coward · · Score: 0

    Well things like OS/2 and all the stuff I wrote in 6502 assembly is pretty much useless now. As a small consolation, maybe there's a graveyard for these things in an alternate dimension.

  9. Here's an honest question. by i_am_syco · · Score: 0

    What's with all this talk lately about linux distros and KDEs and such?

    1. Re:Here's an honest question. by Mr.+Sketch · · Score: 1

      What's with all this talk lately about linux distros and KDEs and such?

      Probably just because there hasn't been any good SCO news lately.

  10. Misspelling in Peren's Letter by Saint+Stephen · · Score: 1

    I can't believe it: Perens left the "e" out of userlinux.com in the link to his own whitepaper on his own site!

    1. Re:Misspelling in Peren's Letter by Saganaga · · Score: 1

      And I can't believe you misspelled his name (it's Perens, not Peren, so the possesive should be Perens'.)

      There. I'm done.

    2. Re:Misspelling in Peren's Letter by Anonymous Coward · · Score: 0

      you cant? well maybe thats cause perens is a productive member of society while our a no-life loser with way to much fucking time on their hands who can spend their friday nights worrying about incorrect links?

      people like you make me want to use xp.....

    3. Re:Misspelling in Peren's Letter by Graspee_Leemoor · · Score: 1

      He didn't misspell his name. There should not be an apostrophe in "Perens" as he used it as the subject of the sentence.

      graspee

    4. Re:Misspelling in Peren's Letter by Net_Wakker · · Score: 1

      Like in the subject you mean?

    5. Re:Misspelling in Peren's Letter by Graspee_Leemoor · · Score: 1

      Ok, i consider myself brought to justice. ;)

      graspee

  11. Ah yes, great. by Anonymous Coward · · Score: 0

    I thought linux was about choice. Guess some people have different ideas.

  12. KDE is based on Qt by jotaeleemeese · · Score: 1, Flamebait

    And Qt is made by Trolltech.

    And Trolltech is part of the Canopy Group.

    Which pulls SCO strings.

    Do we need the threat of more lawsuits in the future?

    --
    IANAL but write like a drunk one.
    1. Re:KDE is based on Qt by Mr.Ned · · Score: 1

      The Canopy Group is a minor investor in Trolltech. Trolltech is not a part of the Canopy Group anymore than Microsoft would be part of Mr.NedCorp if I were to invest in it.

    2. Re:KDE is based on Qt by Our+Man+In+Redmond · · Score: 1

      Someone commented on Groklaw not too long ago that Canopy's stake in Trolltech was pretty small (<10%) and opined as how it would be really cool if Trolltech could buy that stake back as sort of an "up yours" to Canopy.

      No, I don't know how much that is in real money.

      If you really, truly think SCO is more evil than whatever they put in buttered popcorn to give it that addictive smell, you'll probably eschew Trolltech and Qt anyway. But I think the extent of Canopy's participation in Trolltech is a non-issue.

      --
      Someone you trust is one of us.
    3. Re:KDE is based on Qt by be-fan · · Score: 1

      You dumb SOB! Just because Canopy puts them on their website does not mean that that they're somehow a part of Canopy group. The only mention of Canopy on the Trolltech website is a page showing that Canopy owns only 5.7% of the company! Canopy also lists Linux Networx as a portfolio company, which is the same company that built a Top-5 Linux supercomputer for LLNL. I'm sure they'd love a $700 per-CPU Linux tax!

      --
      A deep unwavering belief is a sure sign you're missing something...
    4. Re:KDE is based on Qt by Anonymous Coward · · Score: 0

      And Trolltech is part of the Canopy Group.

      The Canopy Group owns 6% of Trolltech, while more than 60% of it is owned by its employees. So I think this is just FUD.

      Do we need the threat of more lawsuits in the future?

      Perhaps you explain what kind of lawsuit you fear - in order to turn this random attack against Qt into a coherent thought. Why do you think that GTK (which is owned by Canopy to the same degree as the Linux kernel) is less vulnerable to a future lawsuit?

    5. Re:KDE is based on Qt by Odin's+Raven · · Score: 4, Informative
      And Qt is made by Trolltech.
      And Trolltech is part of the Canopy Group.
      Which pulls SCO strings.

      Gee, trolling about Trolltech. How novel. Okay, before any more people swallow this bait:

      Two seconds of googling would show that this is not the case. Look at Trolltech's investors. For crying out loud, Borland owns a bigger stake in Trolltech than Canopy Group, and nearly 2/3 of the stock is owned by employees:

      • 64.7% Employees
      • 8.3% Borland
      • 5.2% Trolltech Foundation
      • 4.3% Orkla ASA
      • 4.3% Northzone Ventures
      • 4.3% Teknoinvest
      • 4.1% Canopy Group
      • 3.4% Previous employees
      • 1.6% SCO Group

      Even if every outside investor (including Borland :-) were merely a shell corporation controlled by Canopy, they'd still have nowhere near the votes to influency anything at Trolltech.

      --
      A marriage is always made up of two people who are prepared to swear that only the other one snores.
    6. Re:KDE is based on Qt by Anonymous Coward · · Score: 0

      1.6% SCO Group

      SCO Group?!
      Shit. Does that mean I owe sco $699 for ever QT based app on my machine now, too?

    7. Re:KDE is based on Qt by supun · · Score: 1

      Nope, you owe $11.18. :)

      --
      :w!
    8. Re:KDE is based on Qt by frank_adrian314159 · · Score: 1
      Even if every outside investor were merely a shell corporation controlled by Canopy, they'd still have nowhere near the votes to influency anything at Trolltech.

      It doesn't matter about control. Every time you give a quarter to Trolltech, letting the stock price rise, you give a penny to Canopy and its blood-sucking weasels. That's a really good reason to support Gnome. Since it's not controlled by a public corporation, you don't have to convince yourself that you're isolated from the antics of its major stockholders.

      --
      That is all.
    9. Re:KDE is based on Qt by 10Ghz · · Score: 1
      It doesn't matter about control. Every time you give a quarter to Trolltech, letting the stock price rise, you give a penny to Canopy and its blood-sucking weasels. That's a really good reason to support Gnome. Since it's not controlled by a public corporation, you don't have to convince yourself that you're isolated from the antics of its major stockholders.


      HELLO?!?!? anyone home?? Trolltech is NOT a public company! it's NOT listed in stock-exchange! It's a privately owned company!

      If you want to look at who controls GNOME, we will see that it's basically controlled by three companies: Sun, Red Hat and Novell (via Ximian). All three are pulic companies whose shares are listed in a stock-exchange. Since GNOME is more or less controlled by public companies, whereas KDE is not, I expect that you will switch from GNOME to KDE. I mean, that WAS the reason you supported GNOME, right? Now that you have been proven to be in error, I expect you to rectify the situation.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    10. Re:KDE is based on Qt by Anonymous Coward · · Score: 0

      There was a project a while back called OpenQT (or something like that) that aimed to reverse engineer QT. It was a daunting task that didn't get very far.

      Once KDE/QT became open source there really was no need anymore.

      As a software engineer with something like 26 years experience behind me, I'd like to include some comments on this whole issue (including a small dabbling in the massively flamish KDE/Canopy controversy).

      1. Choice is good, but choices don't have to be held in stasis like some sort of quantum wave equations always waiting to be collapsed. Perens has made his choice. Because Bruce made his choice it certainly does not diminish our choices. I don't know why human beings act this way. It definitley qualifies as religion. If it makes you feel good, come up with KuserLinux that uses KDE.
      Go make your choice. Just like the cypherpunks say, "cypherpunks code." Contribute or shut up.

      2. I believe Bruce when he says that KDE is a very nice technical acheivement, however I think that he's being a little disingenous about what made him decide on Gnome. I'm sure the real reason is that, even though Trolltech is not controlled by Canopy, that which benefits Trolltech also pours money into Canopy's coffers. Granted, their licensing is very reasonable. No royalties if you do go commercial. All you pay is $1500 for the development software and that includes one year of support and maintenance. Hell, if you don't care about support just use the free version until you're done with development and then pay the $1500. As a developer I'd use it long enough to be confident with it as a tool and then register. As a bonus you can port to Windows or Mac OS/X by simply paying for the tool and recompiling.

      I know that pumping money into Trolltech pumps money into Canopy and SCO Group. That is bad for Linux. For this reason alone Trolltech should have dumped Canopy/SCO Group like the paraiahs that they are. In the end that won't matter because very soon IBM will own their shares. IBM, btw, is very positive on KDE and has promoted it often in the past.

      3. If Bruce is worried about software developers flocking to UserLinux, then KDE is the obvious choice. The vastly superior object structure and documentation of KDE simply outclasses (no pun intended) anything Gnome has to offer. Especiallay disturbing are all the blind alleys that the GTK/Gnome people have stumbled down. (a) I'm not the biggest proponent of C++, but object-oriented programming in a GUI is so naturally superior to a straight procedural model that choosing C as the implementation language of your GUI core is nearly unforgiveable. I would have been much more impressed had they designed it in Objective-C. (b) The way Miguel fell for Gates .NET bait hook, line and sinker by promoting Mono is shocking. Gates must have been laughing his head off. MS has been locking developers into it's share-cropping API ever since the Altair and BASIC-80. They create the APIs and promote them. Some of them are damn good. Their development tools aren't bad either. MS leads the developers which lead the apps which lead the users. Once you have poured huge amount of labor and debugging into that proprietary API you are forever trapped by it. Quod erat demonstrandum, baby.

      So there it is. Who cares what UserLinux does? Promote KDE instead if you like it. I'm running it right now and maybe I'll be running Gnome and FluxBox tomorrow.

      If there is anything KDE could really use it's a damn graphic artist and human factors engineer to do QA on their major releases. KDE core developers should spend some time reading the freely available Apple Human Interface Guidelines. Skins are a very subjective piece of eye candy, but the default 'keramic' theme in their last major release was so unspeakably horrid that I almost didnt waste my time looking at it.

      And that would have been too bad because I downloaded the gorgeous 'plastic' theme along with a cool icon theme and X11 mou

    11. Re:KDE is based on Qt by Anonymous Coward · · Score: 0

      HELLO? Do you think Canopy invests in Trolltech out of the kindness of its collected hearts? INVEST-ment. Get it?

      That argument is so feeble. You're trying (unsuccessfully) to use subtleties of language to hide the fact that regardless of whether GNOME is "basically controlled by three companies" (which is highly inaccurate), should any of them decided to opt out, the project continues without interrupton. No one person or corporation can derail Gtk/GNOME. However, should KDE use ever reach a tipping point and Trolltech (or its investors) decide that there's more money to be made off the backs of KDE users and developers, Trolltech might be persuaded to change licensing. While this would not completely incapacitate development, it certainly could throw a serious spanner into the works, forcing - at the very least - a fork in the toolkit and creating a general nuisance. The bottom line is that Gtk/GNOME provides a lot less risk than Qt/KDE and this is something that corporations will welcome.

      Think a company can't turn it's back on the GPL and attack it? Look no further than Linden, Utah for the answer.

      Oh, and on a personal note: I almost never use the GNOME desktop (Gaim beats the crap out of Kopete, though) and almost exclusively use KDE. Thanks for helping to making KDE users look like spoiled, whiny little brats, throwing a tantrum when they don't get their way. The fact that Perens doesn't endorse resurrecting icewm out of spite shows that he's a lot more mature than the Qt-Trolltech clique.

    12. Re:KDE is based on Qt by 10Ghz · · Score: 1
      HELLO? Do you think Canopy invests in Trolltech out of the kindness of its collected hearts? INVEST-ment. Get it?


      And Canopy/SCO still control a measly 5.7% on TT-stock! Get it? 94.3% of TT is in no shape or for controlled by Canopy/SCO. Any brain-cells still operating in your head?

      SCO's investment in TT was made back when SCO was still Caldera. Caldera used KDE and made an investment to TT. Now those shares are owned by SCO. TT Just can't byu those shares back if SCO is unwilling to sell.

      However, should KDE use ever reach a tipping point and Trolltech (or its investors) decide that there's more money to be made off the backs of KDE users and developers, Trolltech might be persuaded to change licensing.


      It seems to me you don't know a thing about GPL. HAve you ever even READ it? If TT tomorrow announced that they will close Qt and that there will be no free version of it available, KDE-folks would simply use the current GPL'ed version of Qt and go on from there. There would in essence then be two Qt-toolkits: the free Qt maintained by the community, and the proprietary Qt maintained by TT. TT can't retroactively change the licensing of the software they have already lisenced under the GPL

      And should TT try to screw KDE over, Qt would be re-licensed under the BSD-license, as mandated by the Free Qt foundation.

      Plase, at least TRY to check your facts, OK?

      The bottom line is that Gtk/GNOME provides a lot less risk than Qt/KDE and this is something that corporations will welcome.


      How exactly? Both toolkits are free and open source. Just because TT is the primary developer of Qt does not mean that Qt or KDE is somehow "vulnerable". You are just spreading FUD, and you are not very good at it.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    13. Re:KDE is based on Qt by Anonymous Coward · · Score: 0

      Neither I nor the parent mentioned "control." The fact that Canopy invests in TT means that they have rights and influence as investors. Again, you might want to review that Economics 101 text to discover why one company might invest in another.

      As far as the rest of my commentary, I am reasonably well versed in the GPL and understand that GPLed Qt doesn't end if TT makes it proprietary. I never said it did. However, you confirmed that if TT pulls the plug on GPLed Qt, KDE would have to forge ahead with the existing toolkit, meaning Qt is frozen in its tracks while Qt/KDE developers scramble to bring a new (or GNU) Qt project online. Not the end of the world, but a potentially serious disruption. That's not FUD, that's a genuine risk. Apparently, you can't work through the logic on that one, though.

      The bottom line is this -- KDE users/developers getting their panties in a bunch about UserLinux only makes their project and other KDE users look childish. Grow up. KDE will do just fine with or without UserLinux. And, as far as Perens' project is concerned, all KDE has to do is release an easy to install add-on or variant and call it UserLinux Plus or something equally "clever."

      What a waste of electrons...

    14. Re:KDE is based on Qt by 10Ghz · · Score: 1
      Neither I nor the parent mentioned "control." The fact that Canopy invests in TT means that they have rights and influence as investors. Again, you might want to review that Economics 101 text to discover why one company might invest in another.


      They have very limited influence. TT-employees have ALOT more control over TT than Canopy/SCO does. Canpoy/SCO has exactly 5.7% stake in TT. 5.7% is peanuts. Borland alone could outvote them. SCO/Canopy could NOT do anything to TT that the other investors did not agree upon. That is a fact.

      BTW, did you know that Sun, one of GNOME's primary backers, is funding SCO's assault on Linux?

      KDE would have to forge ahead with the existing toolkit, meaning Qt is frozen in its tracks while Qt/KDE developers scramble to bring a new (or GNU) Qt project online. Not the end of the world, but a potentially serious disruption.


      Not really. KDE-hackers know Qt inside and out. Many of them are Qt-hackers as well. It wouldn't take that long for them to carry on with their version of Qt.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  13. If one must be chosen by gid13 · · Score: 2, Insightful

    Hasn't anyone proposed removing Gnome?

    It seems to me (subjective experience, yadda yadda yadda) that KDE is less buggy, more feature-laden, more configurable, and with the new 3.2 betas even slightly faster than Gnome.

    Does this have something to do with the QT developer license cost I've heard about? Is GTK devoid of such a cost?

    1. Re:If one must be chosen by happyfrogcow · · Score: 2, Informative

      as far as i know, the QT developer license is only if you want to use QT in non open sourced, commercial ways. however, i havn't read the actual licensing, only read "reviews" of it so you might want to read it yourself.

    2. Re:If one must be chosen by Anonymous Coward · · Score: 1, Informative

      Qt's got two licences - the first being the GPL, which most people use, is the good old make-it-GPL-and-you're-fine route. You can't distribute a closed-source program that uses Qt, however, unless you use the QPL, whereby you pay money to TrollTech and they give you the right to use Qt in your closed-source app, plus loads of documentation, developer support, etc.

      If anything, it's a better situation than the GPL-only Linux kernel - if you want to write a binary-only driver for Linux, you can be on really shaky ground, and there's no option of a second, proprietary-friendly licence to go to.

      I gather MySQL is dual-licensed in a similar way to Qt, and I haven't seen huge flame-wars about its licensing...

    3. Re:If one must be chosen by Richard_at_work · · Score: 1

      For all the people who have replied to this story with "Why not KDE? Why not include KDE? KDE is better! KDE has much over Gnome!" my reply is thus:

      Its opensource, fork the bastard if you are so inclined.

      This choice was made by people who were looking at a unified and distinct desktop for corporate usage. If they want to concentrate one one single desktop, making it consistant and better, then that is their porogative, as much as forking it is yours. Call your fork 'ReallyUserLinux' if you so want, but stop deriding this choice.

    4. Re:If one must be chosen by gid13 · · Score: 1

      Uh, hello?

      As far as I know, nobody (least of all me) is saying they don't have the right to do what they're doing.

      I'm not deriding the choice. I'm not even complaining. I just don't understand why someone would want Gnome and GTK over KDE, and given that this is a geek news discussion site, I figured someone may be able to enlighten me.

      So please stop shitting in my cereal.

  14. Ground level comparison. by Murmer · · Score: 5, Interesting

    Having used both, I have likes and dislikes about both of them - Gnome does look better, and "feels", whatever that means, like a more complete and professional product.

    That said, KDE is faster. Much, much faster; On older hardware, this is a pronounced difference. Every time my old P2/233 goes bobbing for objects in the Corba barrel, it takes an awfully long time to come up for air.

    If the UserLinux project is only meant to run on hardware made from this day forward, that's cool, I'd go with Gnome. But if not, I'd definitely include KDE - It's cruel to say so, but the choice between Gnome and KDE is, in my house, very much dependent on the choice between new or old hardware.

    --
    Mike Hoye
    1. Re:Ground level comparison. by SyntheticTruth · · Score: 3, Insightful

      Not a flame, but are you kidding? I've used Gnome 2.4 for quite some time on my home machine, and KDE 3.1.* on my work machine for quite some time now. I have decided to go with KDE at home too. Gnome, to me at least, does *not* seem polished or "finished" whatever that means exactly. (OSS never seems to be finished.)

      KDE, for all the claims of bloat, has applications that *work together* in ways that I can not seem to get most Gnome based apps to do. The KDE desktop is more than just the kicker and wm, but a whole suite of OSS software built around that framework that every other DE I have uses lacks. And Konqueror after two years is still my browser of choice -- Mozilla, for all it's geekiness, still seems clunky. (I have no used the *birds yet, as I've had no need.)

      That said, there are things about Gnome I do miss. The MacOS-like bar at the top of the screen. I prefer that, and putting the KDE kicker up there is a poor comparison. It does have desktop menus, but then you can't put applets to that, but I hear that is to change in 3.2. I sure hope so.

      There are things I like about Nautilus file-manager as well, both in appearance in and how it works, but Konqueror as a file-manager is not bad at all, and it does exactly what I think a fm would do.

      In the end, I feel that KDE is the more professional feeling of both popular desktops. It has a unified look-n-feel, simple customization (widgets and window decs) of colors that *I* find pleasing, and the group of apps are just great and always tend to fit whatever need I have at the moment. My only real beef with it is the Trolltech licence. Having gotten into PyQT developing lately, I'm frustrated I can't easily move my apps to Win32 for my friends to use.

      Again, not a flame, but I always hear that Gnome always appears more professional, but I gave it a test of damn near a year, and in the end, the DE felt disconnected from all the elements and apps.

    2. Re:Ground level comparison. by Trogre · · Score: 1

      That said, KDE is faster. Much, much faster;

      Perhaps KDE is faster than GNOME, but if that's true, we're in a lot of trouble.

      Try opening kcalc, a basic scientific calculator. On my Athlon 2000XP it takes 6 (six!) seconds for the window to appear. On my old Windows 95 machine (pentium 133), launching the calculator applet took approximately half a second.

      Sure, both KDE and GNOME are nice, but they still have a long way to go before they're what I would consider usable.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    3. Re:Ground level comparison. by Anonymous Coward · · Score: 0

      There is something wrong with your computer, or you are using the seriously fucked up redhat-massacred-kde. kcalc takes far less than a second to launch on my computer (an athlon xp 2000, as it happens, running mandrake-linux, a distro that is so far ahead of redhat for business desktop use it's not funny anymore that americans refuse to use it. Sure it's french. It's also better than anything the yanks have put out in years.), even when run from outside KDE.

    4. Re:Ground level comparison. by Anonymous Coward · · Score: 0

      Try opening kcalc, a basic scientific calculator. On my Athlon 2000XP it takes 6 (six!) seconds for the window to appear.

      Which KDE and which distribution are you using?

      I just started kcalc on my own system, and it took just under three seconds to start. This is with a 1.1GHz Athlon, KDE 3.1.4, SuSE 9.0, and it's the first time I've started kcalc since switching on my machine.

      Still not ideal by any means, but potentially a big improvement. I just hope they can get it down to fractions of a second...

    5. Re:Ground level comparison. by Trogre · · Score: 1

      I am using KDE 3.1 on RH9, and going by other anecdotes, I now believe this is more of a RH problem than a KDE one.

      My apologies for blaming KDE entirely.

      Having said that, even three seconds is a terribly long time for something as trivial as a calculator applet to launch.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    6. Re:Ground level comparison. by Anonymous Coward · · Score: 0

      Three seconds for a damn calculator??? ...thanks but I'll stick with xcalc, or even bc!

    7. Re:Ground level comparison. by Anonymous Coward · · Score: 0

      Heh heh heh. L0ser

    8. Re:Ground level comparison. by FyRE666 · · Score: 1

      This is one of my pet peevs with the Linux desktops; the start-up times of apps are almost inexcusable. I 've used bothe KDE and Gnome on various distros, and often have to apologise to collegues for making them wait 10 seconds for MozillaFirebird to crank into life, or 15 seconds for OpenOffice to show a small spreadsheet. Even using KDE, launching the Konqueror browser takes 5 or 6 seconds. Considering it's almost as tightly integrated as IE is to Windows it really should be there as soon as your finger lifts off of the mouse button! I don't think it's acceptable for a 2.6ghz machine with 512MB RAM and a fast HD to start apps slower than my old P2 400 with Win'98 from 5 years ago!

      I administer a fair number of Linux servers, which I wouldn't swap for any flavour of Windows (or any other UNIX variant), and I'll carry on using Linux on my desktop at work, but I just wish this issue was addressed. I don't need more toys, tickers and "Aqua like" themes; I want a bit of responsiveness!

    9. Re:Ground level comparison. by be-fan · · Score: 1

      First, kcalc (on my 2Ghz P4) takes less than 2s to start once its in the VM cache. Second, startup speed is problematically slow on KDE due to problems with the linker. That doesn't affect the speed of other parts of KDE. In other respects, KDE is easily as fast as XP, even faster on a heavily loaded machine.

      --
      A deep unwavering belief is a sure sign you're missing something...
    10. Re:Ground level comparison. by skaffen+antisma · · Score: 1

      I have no such Problems.
      kcalc <1 sec
      kate <1 sec
      konqueror <2 sec
      openoffice <6 sec

      I think it is a problem of your Distribution.

      Here a little bit about my Hardware:
      Athlon 2000XP on a K7S5A
      1G Memory
      80G 7200 RPM Maxtor
      Debian Sarge with kernel 2.6.0-test11

      Boris

    11. Re:Ground level comparison. by 0x0d0a · · Score: 1

      That said, KDE is faster. Much, much faster;

      That's...odd. Really odd.

      I've generally found Qt to be noticeably (and last time I was using it, which was on an older computer, irritatingly) slower than GTK+.

      What things were you doing that were particularly slow?

    12. Re:Ground level comparison. by EMN13 · · Score: 1

      This is probably slightly off-topic; but I'm curious about this too. On my machine Qt is much much faster than gtk in window-resizing; this is both in cpu-time user in X-server, and is cpu-time used in the program. This despite the fact that Qt actually shows many many more frames while resizing with content.

      Of course I do have an athlon XP 2000+ as well. Using prelink means startup times are generally great; konq starts up and displays home-dir in about 1/2 a second; mozilla and firebird take around 1 second to start up and display a simple home page. I'm using an nvidia card with XRender acceleration on, and normal widget interactions are slightly less smooth (say about twice as slow) as win2k (which is completely smooth resizing simple windows at 85Hz) when using Qt, but when using Gtk+ is around a further 10 times slower than qt (really).

      Mozilla (or even more clearly firebird) is a great example for this; it resizes with content quite smoothly in windows as long as the HTML page is simple enough, while even with a blank page it'll never get much beyond 5 fps with GTK+ under linux.

      Am I missing some obviously GTK+ configuration step?

      (I realize that window resizing isn't the only measure of worth; but it's a noticable, simple and irritating one)

      So seriously - could you compare this to your experience with GTK+? Basically I just want to get GTK+ programs to run as smoothly as possible but I was under the impression that GTK simply is much worse at relayouting than Qt.

      --Eamon

    13. Re:Ground level comparison. by Anonymous Coward · · Score: 0

      Now if only we all left kcalc open all day.

    14. Re:Ground level comparison. by 0x0d0a · · Score: 1

      Using prelink means startup times are generally great; konq starts up and displays home-dir in about 1/2 a second; mozilla and firebird take around 1 second to start up and display a simple home page.

      Mozilla and Firebird both use XUL, not GTK+.

      If you want to compare resize times in a GTK+ browser, open up the same page in Konq and dillo.

    15. Re:Ground level comparison. by Anonymous Coward · · Score: 0

      Mozilla uses gtk to render the xul. Don't talk from your ass.

    16. Re:Ground level comparison. by iantri · · Score: 1
      Have you tried kernel 2.6.0? It supposedly improves Linux's responsiveness by quite a bit.

      DISCLAIMER: 2.6 is still young. If it breaks, you get to keep both pieces.

    17. Re:Ground level comparison. by Tack · · Score: 1
      Have you tried kernel 2.6.0? It supposedly improves Linux's responsiveness by quite a bit.

      My understanding is that 2.6 improves responsiveness (latency) and, quite inevitably, sacrifices raw throughput. Application load time is all about throughput, so it's probably not going to be the case that dropping in a 2.6 kernel makes applications start faster. It seems to me that this will need to be addressed at higher layers.

      Jason.

    18. Re:Ground level comparison. by Net_Wakker · · Score: 1
      Try opening kcalc, a basic scientific calculator. On my Athlon 2000XP it takes 6 (six!) seconds for the window to appear.
      Excuse me? I run an AthlonXP 1800+/256MB ram and if kcalc takes longer than half a second to launch I'll cut off some fingers.
      There's only two times I have to actually wait for things to start in KDE, and that's when starting a GTK-application (OpenOffice comes to mind), or initiating the first network access with a given app. Checking mail right after starting kmail takes a few seconds untill initial contact with the mailserver, all subsequent checks fly by. Same with accessing webpages. The first after logging in takes a few seconds, all others either go fast, or are dead links or slashdotted or something. In howfar this networkbehaviour is KDE-specific I don't know, since I haven't used Gnome since the pre-2.x days and olwm on an Ultra5 w/ 192 MB running Solaris 8 just doesn't compare anyways.
    19. Re:Ground level comparison. by juhaz · · Score: 1

      Who cares how fast it is at the second time, nobody is shutting down programs and starting them within few minutes, the first time is what counts. And it won't be in the VM cache then.

    20. Re:Ground level comparison. by be-fan · · Score: 1

      It depends on how much RAM you have. I've got 640MB, and I tend to find my apps in the VM cache when I need it. But app startup time definately is less of an issue in KDE than in the 2.x days. Apps take maybe 3 seconds for a cold start, and I'm on a slow laptop hard-drive.

      --
      A deep unwavering belief is a sure sign you're missing something...
    21. Re:Ground level comparison. by juhaz · · Score: 1

      I don't have quite as much (512MB), plenty anyway, but I'll almost never find software cached when I start it up. Probably it's just different usage pattern or something like that.

      Anyway, startup times are worst when starting up a KDE software in GNOME, since they'll need to load all the libraries that aren't in memory and fire up the gigantic kdeinit stuff. I'll assume it's much the same other way.

      3-4 seconds isn't a long time but somehow it still feels like it is. Double that for starting apps from different DE and it feels like an eternity already, some kind of near-instaneous splash screen and "progress meter" might help even if it actually made the time longer, since you'd have something to look at.

  15. Bruce Perens' original response by Anonymous Coward · · Score: 5, Informative

    Newsforge still has a copy of the response that Bruce Perens posted before replacing it with is on www.userlinux.com/GUI.html now..

    Get it here

  16. Don't dodge the issue by div_2n · · Score: 5, Informative

    GNOME was chosen because it allows the development and distribution of proprietary applications WITHOUT purchasing a license from Trolltech.

    It isn't about if one is better than the other. He doesn't touch that argument with a 10 foot pole.

    Read BP's white paper for his wording on it.

    1. Re:Don't dodge the issue by Jeff+DeMaagd · · Score: 1

      You can distribute proprietary apps developed on a computer with KDE, it just can't be a Qt- or KDE-based app.

      I think it would be good to stay away from an effectively proprietary development system though, particularly for a distribution where they hope will be for mainstream/non-techie users.

    2. Re:Don't dodge the issue by RPoet · · Score: 3, Informative

      In fact, I seem to remember Bruce pointing out, in an earlier version of the paper, that the license is the sole reason for the choice. Today's is a new version which is much shorter and to the point. For reference, see this blog entry.

      --
      "Oppression and harassment is a small price to pay to live in the land of the free." -- Montgomery Burns.
    3. Re:Don't dodge the issue by Sabalon · · Score: 1

      I don't care either way...I use aalib :)

      Seriously, isn't this UserLinux, not developers,developers,developersLinux.

    4. Re:Don't dodge the issue by Anonymous Coward · · Score: 0

      The "gtk allows proprietary dev without buying a license" argument is so bogus it's not even funny. If someone is not intending to profit from an app, why can't they release it under the gpl? And if someone IS planning on profiting from an app, $1500 / developer is peanuts, it's not even worth arguing about.

      Besides, what userlinux should aim to do is merge kde and gnome to the point that it doesn't matter whether you design for gtk or qt, your apps will run and integrate just fine in both environments. Going the gnome-only route is a poor choice from a community standpoint, as well as from a technological standpoint (since, let's face it, the kde framework is years ahead of the gnome framework).

    5. Re:Don't dodge the issue by Anonymous Coward · · Score: 0

      There's irony for you. GNOME was chosen because the GNU General Public License of Qt was too restrictive on developers.

  17. One reason may be the cost. by DAldredge · · Score: 1

    Not the cost of KDE, but what it costs to developed closed apps with QT. Selling companies on paying an additional 1300 USD for a dev license per dev can be a difficult thing to do.

    You may not like it, but that is how things are sometimes done in the 'real' world.

    1. Re:One reason may be the cost. by Haeleth · · Score: 1

      Selling companies on paying an additional 1300 USD for a dev license per dev can be a difficult thing to do.

      But - if we're talking about companies not currently using Linux - they're probably already paying at least that much for the proprietary development tools and libraries they use on Windows, Solaris, or whatever. On Linux they get a totally free compiler, choice of free IDEs, free libraries. They can afford commercial QT.

      Besides, aren't these the same companies who are over-suspicious of the "free lunch" deal that Linux currently provides? I'd have thought that a $1300 license fee would be just the thing to convince them it's a serious product, and I'd rather it were Trolltech getting the money than SCO!

  18. I agree with Bruce by BigBuckHunter · · Score: 2, Interesting

    I have never fully understood why distros come with both GUI environments. I realize that there is a lot of great software that one will miss out on either way, but users want simplicity.
    I view Bruce's approach as being better than what Redhat has historically delivered (Gnome with half-assed KDE support). I would rather have KDE left out than finding broken features and diminished functionality after the install.

  19. It's the license by ultrabot · · Score: 3, Insightful

    Especially for business apps, KDE seems like a more natural choice.

    On the contrary, KDE is worse for the business apps. It's all about the license difference b/w GTK+ and QT. Choosing KDE would practically have forced the companies that want to ship closed source software to buy a expen$ive license for Qt (if they want to have the uniform "look", of course).

    Personally, I use KDE. That's because I'm not a business, and I use what works (and KDE works better than Gnome ATM). But I wouldn't build my future on it.

    --
    Save your wrists today - switch to Dvorak
    1. Re:It's the license by Anonymous Coward · · Score: 1, Interesting

      Choosing KDE would practically have forced the companies that want to ship closed source software to buy a expen$ive license for Qt (if they want to have the uniform "look", of course).

      These would be the companies which currently buy expensive licenses for Windows and Microsoft's developer tools? The same companies that were scorning Linux completely until Red Hat started charging enterprise-level prices?

      Free-as-in-beer doesn't impress big business. I don't think it's as critical an issue as you make out.

    2. Re:It's the license by rsidd · · Score: 2, Insightful
      On the contrary, KDE is worse for the business apps. It's all about the license difference b/w GTK+ and QT. Choosing KDE would practically have forced the companies that want to ship closed source software to buy a expen$ive license for Qt (if they want to have the uniform "look", of course).

      I'd have said just the opposite actually. Qt is not that expensive, and it makes money for TrollTech. If you want to prove to the business world that there's money to be made writing GPL software, Qt is a great example, so why not thrust it in front of the corporate types? And from all accounts I've seen, it really is the better, more cleanly designed toolkit. Ask the Opera people, who weren't embarrassed to pay for it.

    3. Re:It's the license by ultrabot · · Score: 3, Interesting

      Free-as-in-beer doesn't impress big business. I don't think it's as critical an issue as you make out.

      Yes it is. It may not matter for 1-4 licenses, but free scales a lot better for hundreds of licenses.

      Plus, there is no license management. With free beer, there is no hassle.

      --
      Save your wrists today - switch to Dvorak
    4. Re:It's the license by ultrabot · · Score: 2, Interesting

      If you want to prove to the business world that there's money to be made writing GPL software, Qt is a great example, so why not thrust it in front of the corporate types?

      Being a good example of a business model doesn't make an argument for choosing it as a foundation of a distro. It's Trolltech's business model, and a good one I admit (it's a great thing they abandoned their old Evil license), but why should UserLinux give Trolltech a free gift of larger userbase?

      I tend to think that Trolltech could "let go" of their desktop toolkit, and rake in the cash from Embedded/Mobile stuff. That could send the popularity of Qt and KDE booming through the roof in corporate circles.

      --
      Save your wrists today - switch to Dvorak
    5. Re:It's the license by Anonymous Coward · · Score: 0

      Free-as-in-beer doesn't impress big business.

      Yeah, they grow big by throwing money down the drain.

      In any event, focussing purely on BIG business would be about the most stupid thing they could do.

    6. Re:It's the license by NDPTAL85 · · Score: 1

      Free also implies the support for your product is either non-existent or soon will be. Whats going on in the average manager's mind when you mention open source as an option is what are the open source programmers going to do and where are they going to be for you when their savings run dry and they have to leave their mom's basement to go forth into the real world and find themselves a full time job. A job that won't leave much time for OSS programming.

      A company thats charging you money on the other hand is much easier to accept and understand. They use the money you (and others) pay them to stay in business and continue to support you.

      --
      Mac OS X and Windows XP working side by side to fight back the night.
    7. Re:It's the license by fucksl4shd0t · · Score: 5, Insightful

      Being a good example of a business model doesn't make an argument for choosing it as a foundation of a distro. It's Trolltech's business model, and a good one I admit (it's a great thing they abandoned their old Evil license), but why should UserLinux give Trolltech a free gift of larger userbase?

      Quite the contrary. The fact that there is a commerical company with a successful business model based on Qt and the fact that there are so many commercial apps that use Qt make it a particularly nice selling point for UserLinux. Have you read GTK docs? Have you read Qt docs? There's a world of difference between the two.

      Imagine, if you will :) , telling your prospect this about your os:

      We bundled the popular GTK+ widget set so you can use this free tool to do all the things you want to do. Sure, we made the choice that you won't have commercial support for the toolkit and that you'll have to depend on us for that kind of support, but you're better for it! There's plenty of email lists and web resources devoted to GTK. Granted, there is very little consistency between GTK applications, so you can expect your users to spend twice as long learning how to use them as anything else...

      Qt + KDE is another matter entirely. There is commercial support for Qt, and there are well-defined standards for how to build a UI in KDE. Sure, some people still ignore them, but most Qt developers follow them. That's why almost every Qt app you use on Linux has a predictable and discoverable interface. GTK apps are a world apart (and behind) from KDE-based apps. Gnome has their own initiative to deal with this in the Gnome environment, but GTK predates Gnome by so long and is used by other desktops (Ice?) that gtk developers don't give a shit about UI conventions.

      Granted, I prefer KDE over Gnome, but I also think that KDE is a better choice for a business desktop than Gnome. Gnome might one day catch up, but I doubt that. :)

      Personally, I think the way to address the toolkit issue in the long-term is for someone to port wxWindows to KDE and build a Gnome port based on the GTK port. In doing so, it might be entirely possible to make a wxWindows app that behaves on KDE and Gnome the way you'd expect native apps to do so. Then you have the greatest benefits of all to offer developers with wxWindows. Not only will your apps run natively in KDE and Gnome, but they'll also run natively on Mac and Windows. All you have to do is compile them for each platform. (Yeah, theoretically, but wxWindows gets closer to that goal than anybody else)

      --
      Like what I said? You might like my music
    8. Re:It's the license by be-fan · · Score: 1

      why should UserLinux give Trolltech a free gift of larger userbase?
      >>>>>>>>>>>
      Why should they give GNOME the free gift of a larger userbase? KDE is no less a community project than GNOME. Indeed, KDE is much *more* of a community project, because the community determines the direction of the project. In comparison, GNOME is designed by fiat, and the extreme oversimplifications in the 2.x series alienated a lot of users.

      --
      A deep unwavering belief is a sure sign you're missing something...
    9. Re:It's the license by Tim+C · · Score: 1

      I'm a programmer. At my company, we use CVS for our source control system.

      Over the years, we've tried to get other parts of the company (eg design, UI development) to use CVS. In the past, we've had problems with this, people have been pretty resistant - it's difficult to understand, they don't see why they should have to learn a new tool, etc.

      A couple of times, when we finally managed to convince some incarnation of a department or other that source control was a good thing, but they still hated CVS, one of the arguments used against it is that there's no support.

      So here we have an adequate tool (it's not without it's little - and not so little - irritations, but it works), widely used, that's been around for years and is practically a de facto standard, and they're bitching about support.

      That's the way a lot of people think - if it's a pay-for product, that means the company is making money, and can employ full-time employees. Full-time employees and paying customers means support. Freely downloadable means its someone's hobby, which means that there won't be any support, unless you're lucky enough to be able to get them to reply to an email, but don't count on it.

    10. Re:It's the license by Billly+Gates · · Score: 1
      That argument is soo old and people still buy it to this day. First off its now GPLed. At least the free version. Yes you can use it for commercial use as well.

      You just can't make commerical apps and link to QT without their permission.

      RMS and other fanatics convinced the world that gnome and not kde was needed.

      Its all been cleared now and even Debian now includes.

    11. Re:It's the license by ultrabot · · Score: 1

      KDE is no less a community project than GNOME.

      QT, unlike GTK, is not a community project. It (well, Trolltech) is a commercial entity, with all the associated attached strings. I believe that trying to bring Gnome and GTK up to par with KDE and QT will be worth it in the long run.

      --
      Save your wrists today - switch to Dvorak
    12. Re:It's the license by be-fan · · Score: 1

      Can GNOME be brought up to par with KDE? Would the current dogma of "features are bad!" prevailing at the GNOME camp allow it? I could live with GNOME being the standard DE if they'd let *some* power user features in (c'mon, even Windows or Mac aren't so ridiculously sparse!). But we still don't have "keep on top" in metacity. Would the GNOME camp accept stuff like configurable toolbars, or dismiss them as too complex?

      GNOME and KDE have a nice duality. GNOME is going the minimalist/sparse direction, while KDE is a little more willing to cater to power users. As long as both DEs are more or less equal, that duality works fine. If the commercial world just arbitrarily decides in favor of GNOME, that duality ceases to exist.

      --
      A deep unwavering belief is a sure sign you're missing something...
    13. Re:It's the license by damiam · · Score: 1
      there is very little consistency between GTK applications

      What have you been smoking? Practically all modern GTK apps follow the GNOME HIG to the letter. There are occasional exceptions (GIMP and Mozilla, notably), but 99% of GTK/GNOME apps are extremely consistant. That can't really be said for QT apps.

      Granted, QT docs are better than GTK docs (although the GTK docs are quite usable). On the flip side, GTK has many more language bindings, so programmers can be much more flexible in how they want to code (C, C++, Java, C#, Python, Perl, etc.).

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    14. Re:It's the license by kfg · · Score: 3, Insightful

      Believe it or not, business is not about shipping apps. Most businesses never develop an app in their entire business lives. They ship chairs, oranges, clean kitchen floors, music lessons, entertainment, green lawns laden with chemicals but free of dandelions, katana, baskets, candles, etc.

      The world is not a world of commercial software development. Even in the software world most apps are not for commercial release.

      To most of these businesses the toolkit is completely irrelevant. Hell, most businesses hardly have more than a handful of custom shell scripts they can call their own and rely entirely on off the shelf solutions. That's one of the things that slows Linux adoption on the desktop in the first place, the lack of certain off the shelf "business oriented" apps.

      I'm a business. I've tried both Gnome and KDE. I used to use Gnome. I've standardized on KDE.

      Why? Because it's a better business desktop at the moment.

      Maybe I should put together The Other User Linux distro for people who like KDE.

      Which is why there will never be a "standard" Linux. Which, contrary to the opinions of many, is a Good Thing.

      There's more than one breed of dog, and if you don't like dogs there are cats. There's no "need" for this. Wouldn't it be easier for everybody if we just had a "User Pet"? Then we wouldn't have to "support" parrots and the like.

      There's also the idea of the strength of genetic diversity. Did you know that geneticists now tend to believe that Cheetahs are the walking extinct? Simply not enough genes left in the pool for viability. That's what makes Microsoft so vulnerable to Linux as well. Too rigid a niche. One good idea away from oblivion.

      This is why User Linux is a doomed idea from the start. Businesses, like my own, can already make a choice of a standard distro and desktop. That's what most already do. User Linux offers nothing here. The core to the idea of User Linux is that the majority have to adopt the distro as their standard to create a shared pool of development against that one distro's choice of packages.

      Not. . .gonna. . . happen.

      KFG

    15. Re:It's the license by abigor · · Score: 1

      I guess that's why Opera, Adobe, and so forth all chose GTK for their apps. Oh, wait, no they didn't. They chose Qt. Name a single commercial GTK app.

      The licenses for a development kit are a fraction of the overall development cost. In fact, they are a fraction of the average developer's salary.

    16. Re:It's the license by treke · · Score: 1

      vmware.

    17. Re:It's the license by abigor · · Score: 1

      Really? OK, you got me.

    18. Re:It's the license by treke · · Score: 1

      Yup. They finally switched to GTK from Motif.

    19. Re:It's the license by Anonymous Coward · · Score: 0

      This is the best reply to the license argument I have ever seen.

    20. Re:It's the license by steeviant · · Score: 1

      You forgot Kylix. Oh wait, so did Borland.

    21. Re:It's the license by RoLi · · Score: 4, Interesting
      want to ship closed source software to buy a expen$ive license for Qt

      Obviously, you don't get it.

      From a software maker's point of view, choosing Qt, you get:

      • An application that runs pretty much everywhere (Linux, Windows AND MacOSX)
      • A modern C++ based toolkit
      • Included RAD-tools

      With GTK, you save a week's salary but:

      • You have only a tiny fraction of potential customers
      • You have moronic decisions that change every month (Now do we want a registry in Gnome or not? Do we want to push everything to Mono or not? Which window manager do we want to use this time?)
      • You have to confront the pains of GTK+ which are lack of tools, documentation and an modern API

      Sorry to break your believes, but for a commercial software vendor to choose GTK over Qt is just plain stupid.

      Choosing KDE for UserLinux would have been smart: You could tell corporations: "See, you can develop your in-house apps with Qt and so you can have a slow painless transition - and you can also go back if it doesn't work out."

    22. Re:It's the license by Anonymous Coward · · Score: 0

      Choosing KDE would practically have forced the companies that want to ship closed source software to buy a expen$ive license for Qt

      Ooh, when you spell expensive with a $, it seems even BADDER! At the end of the day, a commercial Qt license costs a few thousand. Look around you. A few thousand, in a commercical setting, is peanuts. Put it in context, and it really isn't a big deal to anybody without a stake in GNOME.

    23. Re:It's the license by javahacker · · Score: 1

      Hold on a minute. It's the developers who want to write commercial applications that have to pay for licenses. End users do not have a license fee! Why would you as an end user care about it.

      If you are buying a commercial application you are paying for developer hours, developer training, management, marketing, support, and distribution. I'll bet that the tool set the developers use is barely detectable in that mix. Let's say an application takes 1 man year to develop. That's 2000 hours, at $50 per hour (a rediculously low number, especially when you consider employee benefits - more like $75 to $100/hr), doesn't that add up to $100,000. Most real commercial applications are much larger than that (3+ man years). The advertising costs for a product are probably a bigger part of the budget than than the tools.

      Having a good, well supported, well documented, easy to use tool set is far more important, given the hourly development costs, than the costs of tools (like Qt) could ever be.

      That is why more commercial applications are being developed in Qt/KDE than Gnome, except by companies that have a vested interest in Gnome.

    24. Re:It's the license by Anonymous Coward · · Score: 0

      Choosing KDE would practically have forced the companies that want to ship closed source software to buy a expen$ive license for Qt

      Soo... businesses that want to sell software licenses shouldn't themselves have to pay for software licenses? Kind of hypocritical, don't you think?

    25. Re:It's the license by Anonymous Coward · · Score: 0

      Applixware Office suite

    26. Re:It's the license by Brandybuck · · Score: 1

      There are occasional exceptions (GIMP and Mozilla, notably)

      Funny, those also happen to be the two most popular GTK+ applications. If the poster boys for the toolkit can't follow Havoc's HIG, what incentive is there for other non-GNOME apps?

      but 99% of GTK/GNOME apps are extremely consistant.

      The key word here is "GNOME". Non-GNOME GTK+ applications are not very consistant.

      --
      Don't blame me, I didn't vote for either of them!
    27. Re:It's the license by furballphat · · Score: 1

      On the flip side, GTK has many more language bindings, so programmers can be much more flexible in how they want to code (C, C++, Java, C#, Python, Perl, etc.).

      Au contraire

    28. Re:It's the license by Brandybuck · · Score: 1

      VMWare has a GUI? Maybe I'm missing the whole point of what VMWare is.

      --
      Don't blame me, I didn't vote for either of them!
    29. Re:It's the license by damiam · · Score: 1
      GIMP is not a popular business app (although it is working towards HIG compliance and is doing a nice job, especially in the 1.3 series). Mozilla is not a GTK poster boy, it simply uses GTK as a drawing layer.

      There isn't really such a thing as a GNOME app. GNOME provides a framework of libraries (glib, gtk, pango, glade, libart, bonobo, gconf, etc.) and it's possible for an app to depend on any combination of these - you could use gconf in a KDE or command-line app, for example. There are very few "pure" GTK apps these days. Those that do exist (GAIM, Abiword, XFCE, and GIMP, for example) almost always attempt to comply with the GNOME HIG. In fact, I can't think of any major apps that don't comply.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    30. Re:It's the license by Brandybuck · · Score: 1

      I'll bet that the tool set the developers use is barely detectable in that mix.

      Bingo. Give the man a prize. In the last six months my company paid for $3500 of classes for me. They'll pay an additional $2000 in the next six months. They don't even blink at this cost. That's just the expected continuous education.

      Recently I spent three weeks writing a configuration dialog in Motif. With Qt I could have had it done in one. Heck, I prototyped it in Qt!

      One of our embedded products is based on Windows. The developers of that product require $2000 of tools on TOP of the workstation and OS. The company doesn't even blink at this cost. But that's not all! That doesn't include the training in those tools. Or their support.

      If that still doesn't convince you, we spent $60,000 last year for GNUPro support. Support for Free Software! Imagining that companies aren't going to choose UserLinux because they might have to pay for a Qt license if they write proprietary applications is just plain silly. For the price of the proprietary Qt license they get the support.

      --
      Don't blame me, I didn't vote for either of them!
    31. Re:It's the license by Brandybuck · · Score: 1

      In fact, I can't think of any major apps that don't comply.

      Xmms off the top of my head. It doesn't even have a main application menu, only a popup menu. TAB doesn't traverse all the controls in the options dialog. Etc, etc, etc.

      --
      Don't blame me, I didn't vote for either of them!
    32. Re:It's the license by damiam · · Score: 1
      Good point, but XMMS was designed before the HIG existed and is pretty much unmaintained right now (it's not even using GTK2, and has no plans to). A next-generation XMMS is currently being developed (in secret) and will hopefully be better in that regard. There's also the beep fork of XMMS, which is advancing more rapidly. The problem is that XMMS aims to emulate the Winamp interface, and it's not really possible to make that HIG-compliant (unless they aim for Winamp 5, which is probably not going to be duplicated by OSS for a while).

      Note also that we're talking about a corporate desktop here. If a corparate user needs music playback at all, they should probably be using Rhythmbox. It has a much better interface and is completely HIG-ified.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    33. Re:It's the license by alienw · · Score: 1

      What are you smoking? Qt is sold on a per-developer basis, on a sliding cost scale. There are no royalties involved. It's very cheap as it is -- only about a grand or two per developer. That's about 1-2% of a programmer's annual salary. Thus, if he/she is 2% more productive, it pays for itself.

    34. Re:It's the license by Anonymous Coward · · Score: 0

      the idea of the strength of genetic diversity.

      Yes. Image if you can be 1% more productive programming QT/KDE as you can be programming GTK/Gnome. Now what happens when you compound that by hundreds of programmers working thousands of hours for several years?

      Of course, unless UserLinux takes over the world, which I doubt, this scenario will play out regardless of UserLinux's desktop choices.

    35. Re:It's the license by SEE · · Score: 1

      It's not an old argument, it's a new, different argument.

      GTK+ is LGPL. Therefore one can make closed-source apps that link to it for free, without releasing the source. One cannot do that with Qt, which is GPL unless you buy another license.

      Therefore, a GTK+ environment is more welcoming for closed developers to build applications for, as they don't have to pay Troll Tech a fee or open their source. This is especially important if the developer is using additional, licensed third-party components (like DRM, or many pateneted encoders, and the like) which they cannot release under the terms of the GPL.

      Since the goal of the distribution is adoption on corporate desktops, the platform needs to be as friendly to the closed-source developers that provide software to the companies as possible. Which means LGPLed GTK+, not (GPL|Fee) Qt.

    36. Re:It's the license by SteveOU · · Score: 1

      This was about the most insightful post in this flame war. Let's remember three things

      • Most developers work on in-house projects.
      • For in-house applications, written for a single company and not to be distributed, the GPL'd QT seems perfectly acceptable. Since you don't intend to ever distribute the product, you are never hurt by the redistribution clause of the GPL.
      • Final decisions about important things are usually made my accountants, who measure everything in $.

      So if the goal of UserLinux is to produce a Linux desktop suitable for businesses to build their critical software on, QT/KDE seems to be the better choice. The accountants will get nervous at the thought of spending a lot of man-hours on a project relying on GTK as a base, precisely because there is no single company (like TrollTech) they can write a big check to. Whether the company really needs the 'features' of the proprietary QT license, they will buy the license anyhow....it almost seems like an insurance policy to them.

      Lest you think I'm being overly cynical: I've had a manager (an accountant) nearly cancel a nearly complete project, because it was built on PHP. She believed it should be developed in ColdFusion because that would cost money and hence be 'safer.' She had no clue about the underlying technology, but she had seen ColdFusion advertised in a magazine as the ideal platform for web development.

    37. Re:It's the license by AstroDrabb · · Score: 2, Insightful
      You just can't make commerical apps and link to QT without their permission.
      And an expensive PER DEVELOPER license fee.

      $2,330 per developer to compile for one OS
      $3,495 per developer to compile for two OSes
      $4,660 per developer to compile for Windows, Linux and Mac

      Plus Maintenance and Support PER DEVELOPER
      $720 for one OS
      $1,080 for two OSes
      $1,450 for Three OSes

      You don't have to pay any extra to develop with the Win32 API under MS Windows, nor do you have to pay any extra to develop with Cocco/Carbon under Mac OS X. Why in the world should you have to pay extra to do commercial development under Linux?
      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    38. Re:It's the license by beakburke · · Score: 1

      Your comments about GTK are confusing GTK with Gnome, with regards to the registry. Gtk apps run just fine on windows, just like Qt apps do. I can't address you developer complaints, but those end user remarks were not correct at all. If UserLinux wants to standardize on Gnome there are plenty of other distros that still carry KDE. Even assuming that both Redhat and SuSE/Novell Standardize on Gnome for businesses I'm sure Mandrake will still be a KDE centric Distro. And Slack and Debian will still let you pick which ever you choose. Personally I'm curious to see what E17 (Enlightenment) produces.

      --
      ----- Question authority, but not ours. Hate the man, but we're not him.
    39. Re:It's the license by AvantLegion · · Score: 1
      >> These would be the companies which currently buy expensive licenses for Windows and Microsoft's developer tools?

      Yes. You see, the idea is to make switching give them something to gain, not just maintain the same old hinderance.

    40. Re:It's the license by prockcore · · Score: 1

      Well everything you said is a lie.

      GTK runs on Windows and OSX as well.. I'm using PAN and The Gimp under XP just fine. GTK is by no means lacking in tools and several GUI IDE's support it.

      Hell, you can write PHP GTK apps.. I can't think of anything more RAD.

      Finally, Mono and gConf have nothing to do with GTK... Mono is a separate project altogether, and gConf is part of GNOME.

      But hey, if you want to lie your ass off and get modded up for it.. be my guest.

    41. Re:It's the license by Anonymous Coward · · Score: 0


      import org.kde.qt.*;

      public class Main extends QObject {
      public static void main(String[] args) {
      QApplication a = new QApplication (args);
      ApplicationWindow mw = new ApplicationWindow();
      mw.setCaption("Document 1");
      mw.show();
      a.connect(a, SIGNAL("lastWindowClosed()"), a, SLOT("quit()"));
      a.exec();
      return;
      }

      static {
      qtjava.initialize();
      }
      }

      ROFL YOU LOSE, KDE

    42. Re:It's the license by d_i_r_t_y · · Score: 1

      yes you do -- it's built into the pricing of VS...

    43. Re:It's the license by Anonymous Coward · · Score: 0

      Don't forget to add that Qt costs _per_ developer, and that Qt is by and large what one would consider a "legacy C++ API." not "modern."

    44. Re:It's the license by d_i_r_t_y · · Score: 1

      not to mention that qt apps run unmodified on win32, osx or linux/x11...

    45. Re:It's the license by dvdeug · · Score: 1

      With GTK, you save a week's salary but:[...]
      Now do we want a registry in Gnome or not? Do we want to push everything to Mono or not? Which window manager do we want to use this time?


      No one's pushing anyone to Mono; it's being developed as an option. Whether or not Gnome has a registery or a window manager is clearly irrelevant to GTK, just like KDE's (which has switched window managers before too) choices are irrelevant to QT.

      You have only a tiny fraction of potential customers

      Why, because you don't like GTK? It runs on Windows and Unixes, and MacOS X users who won't run X are hardly the vast majority of most people's potential customers.

    46. Re:It's the license by Anonymous Coward · · Score: 1, Funny

      So if the goal of UserLinux is to produce a Linux desktop suitable for businesses to build their critical software on, QT/KDE seems to be the better choice. The accountants will get nervous at the thought of spending a lot of man-hours on a project relying on GTK as a base, precisely because there is no single company (like TrollTech) they can write a big check to. Whether the company really needs the 'features' of the proprietary QT license, they will buy the license anyhow....it almost seems like an insurance policy to them.

      Congratulations fuckwit, you've just justified developing for Microsoft Windows.

    47. Re:It's the license by Anonymous Coward · · Score: 0

      what's legacy about it? What do you define as modern?

    48. Re:It's the license by inc_x · · Score: 1

      If the license is so bad for business apps then GTK must be a really bad piece of software, because a lot of closed source commercial business apps have stil chosen to use Qt despite this bad license. There are virtually no commercial closed source GTK applications.

    49. Re:it's the license by DF5JT · · Score: 1

      "KDE has no plan or vision for the license, except it's proprietary."

      I have no idea what you are talking about. The Trolltech license gives you all the freedom of the Free Software world, as long as you are staying within this world. Once you are in the commercial world, a proprietary license gives you all the possibilities of proprietary software development and marketing of such.

      Pray tell, what is wrong with the Trolltech license? It sure works for QCad, Opera and others.

      However, what the Trolltech license definitely avoids is a total vendor lock in, due to its Open Source pendant.

      That IS visionary.

    50. Re:It's the license by Info+B!tch · · Score: 1

      Amen brother man...Amen. couldn't have said it better myself.

      --
      If man does find the solution for world peace it will be the most revolutionary reversal of his record we have ever know
    51. Re:It's the license by Lumpy · · Score: 1

      Free-as-in-beer doesn't impress big business. I don't think it's as critical an issue as you make out.

      Funny... if your "big business" has to shell out around $90.00 per desktop for license fees for the OS and Office suite. (that's close to what we pay for 20,000 desktops from Microsoft) and that is only for the license. NO SUPPORT INCLUDED! that's a different contract that you pay. and some smartass kid from IT comes up with a plan that CAN sucessfully deploy this "free as in beer" setup...

      Ignoring 1.8 Million Dollars in total savings (Yes kiddies TOTAL savings... your roll out of XP will take the same effort time and manpower and trainging as the roll out of a linux +OO.o solution.. Support is the same... Oh the cost to certify a MSCE to XP is more than a linux certification) means either the CTO is a complete moron or has personal financial reasons to stay with microsoft.

      In today's financial environment businesses ned to lean out operating costs. Linux certianly can do that. and unfortunately a linux solution will also save on IT staff as 1/2 the staff can maintain the same amount of desktops+server.

      --
      Do not look at laser with remaining good eye.
    52. Re:It's the license by lussmu · · Score: 1
      An application that runs pretty much everywhere (Linux, Windows AND MacOSX)
      GTK also run natively, without any fuss, on OSX and Windows.
      A modern C++ based toolkit
      What's not "modern" about GTK? You know, in most cases, programming in plain C is also the better solution, being more simple and effective.
      You have only a tiny fraction of potential customers
      Why? GTK runs just as easily on any OS and in any environment - besides, who even uses Gtk/QT on Windows or OSX?
      You have to confront the pains of GTK+ which are lack of tools, documentation and an modern API
      Well, I simply disagree on that. There are so many different helping libraries that are part of GTK/GNOME and tools like Guile that I've never felt the need for anything more. I have found the documentation, from man pages to the GTK tutorial, to be right on the spot. It seems to me you're just a C++ programmer that likes Qt more than GTK - the points you are making aren't factual or analytic - they're just your sore feelings on the issue.
    53. Re:It's the license by AstroDrabb · · Score: 1

      You don't have to buy VS to develop with the Win32 API. With VS, you are paying for the IDE/tools, not to code with the Win32 API. In fact, you can use gcc under MS Windows to write Win32 apps without paying a dime for VS.

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    54. Re:It's the license by chundo · · Score: 1

      Free also implies the support for your product is either non-existent or soon will be

      You haven't read the white paper, have you? The centerpiece of this entire idea is to have a stable, industry-funded organization that provides long-term support for this distro.

      I don't want to say RTFA... but, RTFA.

      -j

    55. Re:It's the license by AstroDrabb · · Score: 1

      So does wxWindows and it can be used to develop commercial or Open Source.

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    56. Re:It's the license by Charles+Kerr · · Score: 2, Informative
      I'm not going to debate the relative merits of Qt to Gtk+, but I do want to correct some misconceptions you have about Gtk+.
      • When you write in Gtk+, you can get an application that runs on all the platforms you listed. My gtk+ newsreader Pan runs on Linux, Windows, and Mac OSX.

      • The window manager is orthogonal to the topic of what's important from the software maker's point of view: ICCCM compliance is the only feature any application writer cares about. No application requires a specific WM. To do so would needlessly limit their audience.

      • Likewise, you're misinformed about Mono: nobody is telling anyone that they have to port anything to Mono. C# is just another language that Gnome supports. Never in the 4+ years I've worked on Pan has anyone mentioned porting Pan to C#.

      • gtk doesn't lack documentation. In fact the documentation team has made leaps and bounds over the last year.

      • If you prefer RAD tools, Anjuta and Glade are available.

      • Discussing Qt as a `modern C++ based toolkit' and disparaging Gtk+ as lacking a `modern API' is just language bias (and ignores moc's pre-STL cruftiness). If you want to use gtk+ in an OO language, many language bindings are available.

      Again, this isn't to take anything away from Qt -- its tools are pretty good, and its documentation is excellent. However, Gtk+ is very good too.

    57. Re:It's the license by NDPTAL85 · · Score: 1

      I DID RTFA. Sometimes you have to be able to extrapolate what isn't EXACTLY in the articles to get to the deeper meaning.

      Its very clear that to get your foot in the corporate door you have to have a product that is supported from day ONE. Not someday far away down the road.

      --
      Mac OS X and Windows XP working side by side to fight back the night.
    58. Re:It's the license by chundo · · Score: 1

      It will be. Remember, UserLinux is still "someday far away down the road" as well. They won't release without a stable support organization in place. And he already has money from corporate investors to ensure that becomes a reality.

      -j

    59. Re:it's the license by mattyp · · Score: 1
      The GPL is widely known and understood. People like it. The Trolltech license is incompatible with it.

      People want the freedom to do whatever they want: GPL allows this, Trolltech does not.

    60. Re:it's the license by DF5JT · · Score: 1

      "People want the freedom to do whatever they want: GPL allows this, Trolltech does not."

      "I am very pleased to see that Qt is now available under the GPL," said Richard Stallman, President of the Free Software Foundation. "This is a big win for free software and a great gift from Trolltech to the community."

      What was your point again?

    61. Re:It's the license by Anonymous Coward · · Score: 0
      Free also implies the support for your product is either non-existent or soon will be.


      What utter tosh. It implies that you can seek competitive bids for support of the software you use, even if the original company which produced it a) shrivels up and dies or b) decides to charge a firstborn child for upgrades.

    62. Re:It's the license by Anonymous Coward · · Score: 0

      From a software maker's point of view

      I am a software maker. My point of view is that Linux blows goats because the Linux camp can't stop bickering and mindless infighting, KDE doubly so.

      Until there are no negatives to making the switch, Linux will continue to be ignored and I'll continue writing apps for Windows. I might even use wxWindows (on Windows) and the Linux port might even be absolutely trivial (since GTK runs on Windows, Linux and OS X). But I won't give a damn about Linux so long as zealots like yourself refuses to acknowledge problems with the systems that you're advocating.

      Qt's disadvantages:

      * Runs on less than 1% of platforms (Linux)
      * Is 5 to 6 times more expensive than the platform that 95% of desktops run (more $$$ than the Windows operating system and Microsoft DevStudio combined)
      * It bloats the pockets of TrollTech - any person who loves Linux should hate them for hijacking KDE in principal.

      Given my first two points (except the second which GTK conveniently makes go away) - WHY would any commercial software developer in their right mind even remotely consider QT?

      Let me phrase this in a way that you might be able to understand:

      THE QT LICENCE IS A PROBLEM.

      FIX IT OR QT WILL DIE.

  20. Time to change the name by harlows_monkeys · · Score: 1, Redundant
    Time to change the name to IrrelevantLinux. BlueCurve indeed makes KDE and GNOME look a lot like, but good user interface is about a lot more than just looking pretty. More people find KDE to be better.

    A distro without KDE is not going to get very far.

    1. Re:Time to change the name by kid-noodle · · Score: 1

      Sure about that?

      Taken a poll? Of a reasonable subsection of intended market sector? You know, that market that doesn't consist of geeks? The ones who use windows and like the pretty UI?

      Or is it just that you and a couple of other techies you asked, prefer KDE to Gnome?

      I'm not trying to be harsh here, and as a disclaimer you can blame my girlfriend pissing me off for any aggressive sarcasm above...

      --
      fortune -o
    2. Re:Time to change the name by optikSmoke · · Score: 1

      As anyone who follows linux polls would know, KDE generally is preferred over GNOME. The first two things I could come up with googling are:

      1. Linux Journal's Annual Reader's Choice Awards. A quote from 2003's edition: With 44% of the votes, KDE is the winner for the sixth consecutive year. GNOME holds on to second place with 23% of the votes.

      2. LinuxQuestions.org's Annual Awards, in wihch KDE also regularly beats GNOME (as far as I remember). This one is perhaps slightly more interesting since the site is meant for linux newbies.

      As a last thought, there is probably a reason why all of the linux distributions made for the desktop (Lycoris, Xandros, Lindows, etc) use KDE. It has always been (IMHO) the more complete, integrated, and polished desktop -- the fact that it has had a usable file selector for years, and GNOME has just decided to try to fix theirs (although it doesn't seem to be much of an improvement) is just one example of why KDE is more inviting to average users.

      On the usability front, here's a dot.kde.org article about a usability survey that found KDE and Windows XP to be comparable for the corporate desktop in terms of usability: http://dot.kde.org/1060717024/. A quote: The usability of Linux as a desktop system has been experienced as nearly equal to Windows XP. A couple of tasks were, in fact, easier and faster to solve on Linux.

      And by Linux, they mean KDE :).
    3. Re:Time to change the name by damiam · · Score: 1
      the fact that it has had a usable file selector for years, and GNOME has just decided to try to fix theirs (although it doesn't seem to be much of an improvement)

      <zealot type=GNOME>

      GTK's current fileselector is, IMHO, the best I have ever used. It's no-nonsense and supports globbing and instant tab-completion. The new fileselector, for which there is no UI yet (the screenshots floating around are just demonstrations of the API, which is a huge redesign and will allow the GUI to be easily switched in the future) will hopefully retain those features, while adding all the eye-candy found in other dialogs.

      </zealot>

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    4. Re:Time to change the name by optikSmoke · · Score: 1

      Unfortunately, whenever I show the GTK selector to someone who has never used linux before, their instant reaction is BLETCH! My brother, for example, does not use linux (unless on my system for a brief period), but has used the GTK selector before. He is an artist and is comfortable with Photoshop, but that file selector alone gave him the impression of the gimp being archaic and poorly written -- indeed, he inferred this onto most linux apps because of his experiences with the gimp.

      I don't find his reaction to be an uncommon one, either. Nor is it particulary conducive to linux adoption on the desktop -- likely one reason why companies looking to woo average users steer clear of GTK.

  21. Not that I really care.... by Anonymous Coward · · Score: 0

    I user neither GNOME nor KDE, hell I don't even use Linux.

    I run BSD's is console only, and use Windows for the desktop. But this is really stupid, I've tried both and KDE wins hands down.
    I bet the people intended as the audience for this YALD (Yet Another Linux Distro) will laugh too.

    And while I'm at it, I can't stand Brunce on his always so high horse and mostly ignorant and silly ideas. Why can't SANE people ever be put in charge of making decisions that effect others?

  22. This actually isn't a bad idea... by drhlx · · Score: 5, Insightful

    Sure, to your average ./ linux geek, not having the _choice_ of desktop environment is sacreligious, but in order to push linux into new markets, a unified, consistent GUI is one of the things needed. Support costs decrease. Documentation (user-level) can be written for a single interface. Users moving from one (UserLinux) system to another receive the same feedback, which reinforces their learning.

    What linux _really_ needs (for the purpose of appeasing your everyday, business/home user) is to adopt the approach Apple took with MacOS X. It presents a single unified interface, well-designed apps, etc. but lets you add the rest yourself. It's powerful in the way that OS 9 wasn't. But because it's UNIX underneath, you know you can get in there and change it. You don't need to be an expert to do that - someone else will develop a little GUI wrapper to do it for you. But the fact is it's possible.

    We've all known and loved this about Linux for years, but it's mass-market adoption is being stifled by lack of a unified interface. Aesthetics is something Apple learnt a long time ago. It counts.

    The point of the various distributions is to target different audiences, to package things in different ways, to pursue different directions. If you don't like one particular distro, choose another. But we really need a distro that is consistent, and doesn't compromise on security (like Lindows). In fact, we need several. Let them fight it out. May the best distro win.

    1. Re:This actually isn't a bad idea... by bfields · · Score: 5, Interesting
      Sure, to your average ./ linux geek, not having the _choice_ of desktop environment is sacreligious

      As a geek, I'm frankly pretty sick of going to the geek next door to help with some debugging only to discover that their desktop is configured so differently from mine that I have to ask their help to get a friggin' terminal window.

      I'm thankful every day that the rest of the world isn't like this--I appreciate being able to use someone else's car, or stove, or whatever, without having to read the user's manual.

      ...we really need a distro that is consistent, and doesn't compromise on security

      Yup.

      --Bruce Fields

    2. Re:This actually isn't a bad idea... by gobblez · · Score: 0

      Great Post.

      Another thing I think needs to be worked on is installation. I reinstalled Windows XP the other day and realized there were no confusing choices. It just asked for my name and timezone. Even the user friendly installs like Mandrake are hard. Has some choices that I'd rather not have to make. I just want it to work.

      My biggest peeve with Linux is I have yet to get it to recognize my cable connection! you shouldn't have to type your ip, gateway, and other stuff i don't know in, it should just work, like windows. having to type startx to start a gui sucks. i know theres ways to get a gui to start automatically, but once i got linux installed with no internet, i can't look it up! blah...

    3. Re:This actually isn't a bad idea... by PzyCrow · · Score: 1

      What is needed it to stop viewing "Linux"(not the kernel) as a product and start seeing what it is, A COLLECTION OF FRIGGIN SOURCECODE!

      What they have done is simply to pick the source code they need to develop THEIR PRODUCT.

  23. blackbox, fluxbox, etc by 0x12d3 · · Score: 1

    I'd personally be completely happy if they went with minimalist solutions to the various implementations. (ie gui, mail client, text editors, browser, etc). I guess this is a bit less feasible for business oreinted ends, but still... gnome? kde? Who tolerates the latency?!

    1. Re:blackbox, fluxbox, etc by Anonymous Coward · · Score: 0

      I prefer yourmomsbox.

  24. For an end user... by Anonymous Coward · · Score: 0

    ..., using a Mandrake 9.x distro, for example Open Office works as fine on their KDE interface as KOffice works on their Gnome interface.

    Programs in the background, interface in the foreground. That is all that end-users care about, libaries should not matter, they are a background thing.

  25. Freedom of Choice by Anonymous Coward · · Score: 1, Insightful

    Is the freedom to create a Linux distribution with only one desktop.

  26. The question is... by autopr0n · · Score: 4, Interesting

    Why hasn't anyone made an OSS implementation of Qt? I don't see why it would be to hard to come up with a drop-in replacement, maybe even based on GTK, (though hopefully more low level).

    --
    autopr0n is like, down and stuff.
    1. Re:The question is... by cduffy · · Score: 5, Informative

      Why hasn't anyone made an OSS implementation of Qt?

      It's GPLed right now, and thus is already OSS. (Now, because it's under the GPL and not the LGPL, *commercial* development with Qt requires a commercial license, and that's a big chunk of the reasoning on why I'm not putting in the time to learn it -- but it certainly is open source).

    2. Re:The question is... by Anonymous Coward · · Score: 0

      Years ago, one was being worked on (called Harmony, I think) - but then Trolltech did the evil thing of re-releasing Qt under the GPL, which is apparently a fairly popular licence which even RMS approves of.

    3. Re:The question is... by Anonymous Coward · · Score: 0

      There was a group working on it. They stopped once Trolltech released a GPL version of Qt. In fact Qt has been GPL for over four years now.

      http://www.trolltech.com/newsroom/announcements/ 00 000043.html

      BTW: You can not deny people buying stock. SCO owns a small share of Trolltech stock, however has no control. Intel owned RedHat stock, however no one ever said Intel owned RedHat. The parent->parent post is pretty misleading.

      It's like me buying one share of Microsoft stock and then proclaiming I own Microsoft. I in fact do own Microsoft, however not enough to even get a Christmas card from them.

    4. Re:The question is... by bedessen · · Score: 1

      That's just a misleading thing to say. There's nothing preventing you from doing commercial development with a GPL library without buying a license. It just means that you have to offer to provide the complete source to the people that you give binaries to. A lot of companies do tons of development on in-house systems that never leave the company, and they would be under no obligation to pay fees to anyone. Likewise, some companies develop specialized systems for other companies or small numbers of clients. In these cases where you're essentially building something to spec, something that you're only going to give to a couple of people, it's not showstopper that you have to give them source as well. Some companies would want to retain their source so that they can be in control, and so they'd need the commercial license. But in other cases they may be glad to hand over the source, in which case they owe nothing to Trolltech.

      So there are certainly situations where GPL and commercial software can work together.

    5. Re:The question is... by Billly+Gates · · Score: 1
      Yes it was called Harmony. I think it was abandoned but I am not too sure.

      Today's QT license is alot more liberal.

    6. Re:The question is... by damiam · · Score: 1

      Before QT became GPL'd, there was a project called Harmony (Google for it) that tried to do exactly that. That effort died down because of the difficulty and relative futility (now that QT was GPL) of its goal.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    7. Re:The question is... by jonbryce · · Score: 1

      QT is available under the GPL. This complies with the requirements of both the Free Software Foundation and the Open Source Initiative.

      This happened on 4th September 2000 - over three years ago. Why do people still pretend that QT is not free software or open source software?

    8. Re:The question is... by cduffy · · Score: 1

      Yes -- I should have said "proprietary" software rather than "commercial" software. My bad.

    9. Re:The question is... by SeanAhern · · Score: 1
      But in other cases they may be glad to hand over the source, in which case they owe nothing to Trolltech.

      Close, but let's be precise here. If they release their software under any license other than the GPL (or compatible license), they will require a commercial license from Trolltech. The availability of the source doesn't actually have a lot to do with it. It's technically a question of license. See Trolltech's FAQ on the free version for more information.

      Specifically, this is interesting:
      Q: Using the Free Edition, can I make software for internal use in my company/organization?

      A: The Qt Free Edition is not intended for such use; it is our policy that when you are using Qt for free, you should in return contribute to the free software community. If you cannot do that, you must get Professional/Enterprise Edition licenses instead.

      Note that software developed with Qt Free Edition must be distributed as free/Open Source software; i.e. the receivers must be free to give it to whomever they like. In-house distribution is no exception to this rule, of course.
    10. Re:The question is... by kfg · · Score: 1

      You are confusing ideas of commercial, open source and propriatary.

      Commercial Open Source software, while unusual at the moment, is hardly an oxymoron and not unheard of.

      It would be more proper to say that if you wish to develop closed source propriatary software based on Qt for distribution (which may, in fact, not be a commercial distribution) you must purchase a commercial license from Trolltech.

      Call me anal if you wish ( the line has already formed to the right, take your place at the rear of the line), but I think it's still important to make this distinction as many are confused by it.

      KFG

    11. Re:The question is... by codermotor · · Score: 1

      Now, because it's under the GPL and not the LGPL, commercial development with Qt requires a commercial license

      If it's licensed under GPL, then its use, by defintion, can't be further restricted.

      You are confusing the terms commercial (e.g. for profit) and proprietary (e.g. closed source). These terms are not interchangeable.

      Software may be commercial and non-proprietary at the same time (for example SUSE Linux). And proprietary does not necessarily imply for-profit.

    12. Re:The question is... by bedessen · · Score: 1

      Yeah, that is a little interesting because there's nothing in the GPL that allows for you to dictate who your downstream recipients can distribute your software to. In other words if Qt is truly GPLed then it should be perfectly acceptable to write a GPL application for internal use -- naturally if anyone inside the company wanted to give the software to any third party they must be allowed, so I suppose there is the case that you'd have no control over "business secrets" in such code. But, if that's not a concern then it's still GPL software, even if you don't actively try to spread it to anyone but yourself. Now, I'm not saying that's the moral thing to do, but going by the GPL it's fine.

    13. Re:The question is... by cduffy · · Score: 1

      I already corrected myself elsewhere in this thread (and 50 minutes before you posted your comment).

    14. Re:The question is... by steeviant · · Score: 1

      Today's QT license is alot more liberal.

      Today's QT[free] license is the GPL.

    15. Re:The question is... by fault0 · · Score: 1

      > to write a GPL application for internal use -

      That really has to do with interpretation of whether a company is internally one entity or many entities. This differs between localities, states, and countries. It coinicidently is one of the more fuzzy areas of both the GPL and LGPL.

    16. Re:The question is... by Elektroschock · · Score: 1

      QT is GPLed for Free Software usage Well: commercial = non GPL LGPL causes license variety. Yes, you can write commercial=closed source=nonFree-Software with a LGPL license. Qt is a wonderful easy, good structured toolkit, quite mature. When you want to write non-free Software with qt you have to pay. This is an easy model. And there is also no danger that trolltech will be overtaken by a mayor company because it is a hacker company with a contract with its users. I think Novell/IBM takeover of Ximian may be very dangerous for the freedom of software, hmm?

    17. Re:The question is... by cduffy · · Score: 1

      I think Novell/IBM takeover of Ximian may be very dangerous for the freedom of software, hmm?

      How so?

      It's not like they can withdraw the licensing they've offered older versions, or anything like that. Besides, it's in IBM's interest to be seen as The Good Guys -- it's good for their services business, and for business in general. (I know *I've* been urging my company to do more business with IBM since they've started doing the responsible-OSS-community-members thing).

      What could IBM do with the resources they've bought that would be worth more than this massive and widespread goodwill?

    18. Re:The question is... by antirename · · Score: 1

      This sounds to me like "If you use the free edition, you SHOULD distribute whatever you create with it. If you don't want to distribute OR you want to distribute with no source you should buy the Professional/Enterprise Edition license". Since when does the GPL require you to distribute anything?

    19. Re:The question is... by SeanAhern · · Score: 1

      I don't have time to find the exact section right now, but...

      Since when does the GPL require you to distribute anything?

      If you distribute binaries of GPLed code, you are required to furnish all source code when asked. That's a distribution requirement, based on other actions.

      Not that it's related to distribution, but it also says that all derived works must also be GPLed. So if you distribute a commercial work (necessarily not GPLed), then you can't use the GPLed Qt.

      I know I'm beating a dead horse here, but someone once said that "belaborment is good". :-)

  27. Good Choice by Anonymous Coward · · Score: 1, Interesting

    Although it might not be a good choice to select Gnome over KDE, I agree with this move.

    I don't think Linux will become widely accepted on the desktop until there is a standard for installations. The amount of software you include in your packages is also taken into effect when you need to support these products (or not have to support them). I think this is why certain packages (i.e. Debian) will include every package, rather than selecting which goes in. Most of the support is kind of fix-it-yourself, and providing all packages allows them to do anything or fix any problem right? This approach is great for Geeks with the do-it-all-yourself type attitude, but it doesn't work elsewhere. This also relates to having to choose which windows manager to use when installing the OS. This division among windows managers has caused and will cause alot of problems in the future when relating to interoperability between applications and elsewhere. I personally feel that every Linux distro should go with 1 windows manager, and not allow people to chose between them (unless this is a Linux distro that caters to the "expert" - but which distro doesnt claim this?).

  28. BFD by Harmotech · · Score: 2, Insightful

    Who cares? It's ONE distro out of how many? It's probably good in the long run if it makes transition from another OS that much easier. KDE needs to follow suit...how many distros would happily use them?

  29. And in the end by Eberlin · · Score: 2, Interesting

    There can be only one!

    Why GNOME over KDE, I don't know. Then again, I'm sure we all have our personal biases. (I happen to like KDE).

    A possible danger here would be the road to .NET -- and how heavily Novell/Ximian will be pursuing it. If this is the direction GNOME itself is going and MS suddenly pulls a patent-fit (released as open standards, blah blah...note SCO distributing their code under GPL doesn't shut them up).

    Support for both would be great, if not needed, though. I like kuickshow too much to give it up. I know that's a trivial app, but put a more heavily-relied-upon app in its place. There are people who couldn't work without at least KDE app support.

    If in the end, there can be only one, I hope it's a product of convergence, and not the demise of one environment (to be technical, the rest of the environments).

  30. the PERL mantra - on playing catch-up by thockin · · Score: 3, Insightful

    The PERL mantra is CRAP. One of the desktop UI projects needs to concede, and they need to put their efforts together. KDE is good, but lacks some of what GNOME has. GNOME's recent offerings have been pretty screwed up, IMHO.

    While competition is good, cannibalism isn't, and that is all the two projects do - cannibalize each other. Put the resources, people, time, brains TOGETHER. It's a hard decision to make, but they really need to do it, if either one wants to get better by the leaps and bounds we need.

    The last few times I have dealt with new GNOME updates it gets WORSE AND WORSE. More bloat, more crap, less options, harder to figure out how to change things. There is nothing more frustrating that a feature you used to use all the time being taken away from you

    Focus on cleanliness and efficiency. That doesn't mean that all the config options have to disappear (ahem, Metacity can bite my ass). It DOES mean that nautilus can't chew up 16 MB of memory per user just to SIT THERE.

    Get it together guys, they're getting ahead of you further than you can catch up at this point.

    1. Re:the PERL mantra - on playing catch-up by Anthony+Boyd · · Score: 1
      One of the desktop UI projects needs to concede, and they need to put their efforts together.

      I agree. We should decide for everyone else. I say Gnome concedes, and KDE takes over. Thanks!

    2. Re:the PERL mantra - on playing catch-up by mwa · · Score: 1
      One of the desktop UI projects needs to concede, and they need to put their efforts together.

      Something like this?

    3. Re:the PERL mantra - on playing catch-up by flacco · · Score: 1
      That doesn't mean that all the config options have to disappear (ahem, Metacity can bite my ass).

      ...and while it's biting your ass i'll sodomize metacity from behind.

      metacity blows. "ease of use" and "useless, featureless piece of crap" needn't go hand in hand.

      --
      pr0n - keeping monitor glass spotless since 1981.
    4. Re:the PERL mantra - on playing catch-up by 0x0d0a · · Score: 1

      That doesn't mean that all the config options have to disappear (ahem, Metacity can bite my ass)

      Don't use Metacity if you're a power user. There are a hell of a lot of GNOME-supporting WMs.

      I've been a fan of sawfish since well before GNOME adopted it, but it's not like there are a dearth of other choices.

  31. gnUserLinux ? by rasjani · · Score: 1
    Quote from Perens:

    I proposed gnUserLinux, but RMS didn't like it! He feels that having the GNU up front would signify that it's an FSF official project. UserGNULinux doesn't roll off of the tongue quite as easily.
    Well, hell! and few others! That be the first from RMS! =))

    --
    yush
    1. Re:gnUserLinux ? by Haeleth · · Score: 1

      So presumably it's now to be called "the UserLinux distribution of the GNU/Linux operating system", a nice neat name to go with its primary application, "the OpenOffice.org office suite"...

    2. Re:gnUserLinux ? by jonathan_ingram · · Score: 1

      Interesting. If he wanted a more 'GNU' distribution, then he should choose KDE over Gnome, given that GTK+ is licenced under the (to RMS) substandard and deprecated LGPL, while Qt is licenced under the (to RMS) ideologically sound GPL.

    3. Re:gnUserLinux ? by Gzip+Christ · · Score: 1
      That be the first from RMS! =)
      Actually, believe it or not, he also said no thanks to this other product being named GNUticles - I think it had to do with patent issues.
  32. KDE will always be available in UserLinux by Anonymous Coward · · Score: 5, Insightful

    KDE will always be available in UserLinux, because UserLinux will be a subset of Debian. Want KDE? It'll be just a few clicks (or an "apt-get install kde") away. Want to run just a particular KDE or QT application? No problem; the libraries you need will be installed automatically. This is Debian, folks.

    The conflict here is about defaults. UserLinux will include and install Gnome by default, and the developer effort will be geared toward GTK. Why? Because GTK is royalty-free in all situations, unlike QT, and UserLinux is building a royalty-free development environment.

    1. Re:KDE will always be available in UserLinux by benjamindees · · Score: 3, Insightful
      UserLinux is building a royalty-free development environment.

      Horseshit. When you see 'User' Linux, do you think "That means it's royalty-free for developers"?

      UserLinux *should* be building a seamless, easy-to-use Linux with a common look and feel and a default set of fully-integrated apps. In short, it should be doing what KDE has been doing for years. Imo, if they would just port OpenOffice.org and Mozilla to qt, they'd be about half-way towards the real goal.

      I wish them luck; but I'm not holding my breath.

      --
      "I assumed blithely that there were no elves out there in the darkness"
    2. Re:KDE will always be available in UserLinux by frank_adrian314159 · · Score: 2, Insightful
      KDE will always be available in UserLinux, because UserLinux will be a subset of Debian.

      This is so correct. You know, this is Linux. You still have a choice. You can even start with the UserLinux environment, add KDE, repackage it and sell it as "Now with KDE!!!!" Simply put, if you don't like it, go fork yourselves.

      All of you folks wanking about choice should remember that a choice has been made. It is a choice to simplify at the expense of having only a single desktop. It simply happens to be a choice you don't like. Too bad. There are already a ton of distros offering choice of both KDE and Gnome - Debian, Knoppix, SuSe, Mandrake, and Fedora all come to mind. Stop whining because your favorite didn't get picked for the beauty pageant...

      --
      That is all.
    3. Re:KDE will always be available in UserLinux by luisdom · · Score: 1

      All of you folks wanking about choice should remember that a choice has been made. It is a choice to simplify at the expense of having only a single desktop. It simply happens to be a choice you don't like. Too bad.
      A choice has been made by Bruce Perens and redhat. Yeah, their choice, not mine.
      Stop whining because your favorite didn't get picked for the beauty pageant...
      I will whine as much as I want about a decision I don't like, thank you, Stalin.

    4. Re:KDE will always be available in UserLinux by luisdom · · Score: 1

      UserLinux will include and install Gnome by default, and the developer effort will be geared toward GTK.

      Which will kill the project from begin, because every KDE fan will actively promote any other option which doesn't make it so blatant that they will not support kde. Maybe is the "UserLinux May Go Without KDE" title of the article, but it really pissed me off the way that they have dismissed kde. Because

      Why? Because GTK is royalty-free in all situations, unlike QT, and UserLinux is building a royalty-free development environment.
      (Again and again) quite arguable. Qt is far better that gtk (of course IMHO) in terms of development, and I think that the only thing that makes gnome a decent product is the exellence of their programmers. Non-OO GUI programming in the XXI century? Come on... Ok, you have bindings, but...
      So. Royalty free. 1000$ for a commercial licence is not that much to pay for if you're not going to make GPL apps. And for the distro, you get a free and much better (again IMHO) framework.

  33. Can we put this myth to rest? by Spy+Hunter · · Score: 5, Informative

    Trolltech is an independent company, not controlled by Canopy. Canopy group owns 5.7% of TrollTech's shares, while Trolltech's employees and founders own 69.7%. This myth of Canopy controlling Trolltech is entirely untrue (but remarkably persistent, thanks to anti-KDE trolls). Read kdemyths.urbanlizard.com and be enlightened.

    --
    main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
    1. Re:Can we put this myth to rest? by Bob+Davis,+Retired · · Score: 1

      3 words -

      Minority Shareholder Lawsuit.

      That is all.

    2. Re:Can we put this myth to rest? by Anonymous Coward · · Score: 0

      OK, you can count - all the way up to 3 - and we're impressed. But what lawsuit is it you're talking about. Can you share your wisdom with us? Or was this just a shot into the dark?

    3. Re:Can we put this myth to rest? by Anonymous Coward · · Score: 0

      Also, let's not forget that Qt is not open source, therefore you cannot redistribute binaries of it in a commercial distribution.

  34. So what? by caudron · · Score: 3, Insightful

    Seriously. So what? If you want to use KDE, use a different distro. This is a non-issue.

    -Tom

    --
    -Tom
    1. Re:So what? by adrianbaugh · · Score: 1

      Amen, brother. I've lost count of the times people complain that X distribution doesn't have features Y and Z when there are plenty of distributions W, V, U,.... that are fine in this regard. Not every distro has to do everything for everyone, actually it's probably better that they don't. Unless you really do use 8000 different bits of software there's a distro somewhere that will make you happy. And if you do use that many packages, there's always freshmeat :-P

      --
      "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
      - JRR Tolkien.
    2. Re:So what? by cpeterso · · Score: 1


      If the KDE developers think KDE is so much better for business users, then why don't THEY create a KDE/Linux distro? Shucks, they could even wait for Bruce to release UserLinux, take his code, and replace GNOME with KDE. Just like that guy creating "White Box" Linux based on Red Hat Enterprise Linux.

    3. Re:So what? by cryms0n · · Score: 0

      Exactly sir.

      The idea is not to make a desktop that does everything.

      Rather, in a sense, you need a desktop for each particular application. This is an extreme example, but I think it rings true.

      A word processor should turn a computer into a dumb word processor. An image editor should turn a computer into a dumb image editor, etc. Do one task and do it well.

      Once you've mastered that task, you can work on integrating features amongst the different environments.

    4. Re:So what? by Anonymous Coward · · Score: 0

      Sounds like DOSSHELL is just the desktop for you.

    5. Re:So what? by Dalcius · · Score: 1

      If I wanted to stick with 'one browser is good enough for everyone' I wouldn't have migrated to Linux.

      Just because you don't have a single desktop doesn't mean companies won't buy in.

      I'll tell you a secret. You can get KDE and Gnome to play fine if you standardize areas where they can interoperate. Installation, administration tools. If your standards says "install libraries for both GTK and QT", then set up some standards for how to get the clipboard to talk between the two.

      What Linux needs most is a standard that says, "ctrl+q is quit" and "include a programs menu" and "program installation is done through X", etc. We need standards so that users don't have to learn 50 different manuals to use Linux.

      If you think this isn't possible without picking a single desktop, you belong back in the Microsoft camp with all the nazis. :)

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    6. Re:So what? by be-fan · · Score: 1

      A *lot* of KDE developers are doing something very similar to that (see the dot.kde.org story).

      --
      A deep unwavering belief is a sure sign you're missing something...
    7. Re:So what? by Anonymous Coward · · Score: 0

      ...and IF you do there's always debian with 12.000+ packages ;)

    8. Re:So what? by caudron · · Score: 1

      If you think this isn't possible without picking a single desktop, you belong back in the Microsoft camp with all the nazis. :)

      lol. :-)

      To be clear, I never commented on whether it was a good or bad idea, only that it's just one distro and if they don't do things the way you or I would do them, them we can just not use it. It doesn't make a whit of difference to me whether he standardizes on Gnome, KDE, BeOS, FreeDOS, or Fluxbox. What matters to me is whether or not it's something I want to use when he's finished making it. If it is, then I will, and if it isn't, then I won't. No big deal either way, to me.

      --
      -Tom
    9. Re:So what? by Dalcius · · Score: 1

      I appologize, you're absolutely correct - I read too much into your post.

      My take was based on the 'talk' I heard when UserLinux was suggested. The impression I remember getting was that of a distro to bring companies to Linux, a united front to standardize Linux and get enterprise behind it.

      A distro is fine -- I agree with you 100%. I do have problems, though, with folks trying to steer the community behind one this or that. Sure, it can work if they pull it off -- if they don't, they might just hurt us more than help us -- but only one environment will get the benefit. I'm up for bringing corporations into the community we have now.
      Sorry if I just spent a while kicking a dead horse.

      Cheers :)

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    10. Re:So what? by adrianbaugh · · Score: 1

      ...and IF you do there's always debian with 12.000+ packages ;) :-) I wasn't going to mention it, you know how much the trolls round here hate Debian 'zealots', but I know what you mean. Most things are just an apt-get away!

      --
      "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
      - JRR Tolkien.
  35. Absolute bullshit by Anonymous Coward · · Score: 0

    [END USER] I want to use application X.

    [COMPUTER] You cannot use application X, it would confuse you too much.

    This is the kind of reasoning that causes 100% of the flaws in Mac OS X

  36. Re:Releasing a distro without KDE... by platypus · · Score: 1

    Releasing a distro without KDE ... is like going to war with France without the Germans.

    Ok, flame me, but I found this funny. Btw. who the fuck could get flamebaited by that? People, these times are long gone.

  37. GTK is OSS by autopr0n · · Score: 1

    In fact, I think it stands for the Gimp Toolkit and came out of the gimp project, although I could be wrong. The real question is, why hasn't anyone made an OSS implementation of the Qt API. Dosn't seem like it'd be that hard.

    --
    autopr0n is like, down and stuff.
    1. Re:GTK is OSS by be-fan · · Score: 1

      1) It would be that hard. GTK+ isn't as good as Qt yet, and its been around forever. And GTK+ doesn't even do a fraction of what the Qt API encompasses (database access, networking, etc).

      2) Qt is OSS! It was GPL'ed long ago.

      --
      A deep unwavering belief is a sure sign you're missing something...
    2. Re:GTK is OSS by cyb97 · · Score: 1

      Qt is available for Windows Unix, MacOSX and embedded linux making it hard to reproduce as pure OSS with no commercial entanglements.
      A Quick Cost analysis of Qt vs GTK.
      (and lets not forget at Qt does much more than GTK does, so it's really a huge job recreating it)

    3. Re:GTK is OSS by ivan256 · · Score: 2, Insightful

      Qt is OSS! It was GPL'ed long ago.

      Exactly the point. GTK+ is available under the LGPL, rather than the *less* free GPL like Qt. You can't create closed applications with a GPLd toolkit, where you can with an LGPLd toolkit. A viable platform has to support closed applications.

    4. Re:GTK is OSS by be-fan · · Score: 1

      You can create closed-source apps with Qt. You've got to pay Trolltech a $2000 per-developer fee, but if you're making commercial apps, you should have no problem using a commercial toolkit!

      --
      A deep unwavering belief is a sure sign you're missing something...
    5. Re:GTK is OSS by abigor · · Score: 2, Insightful

      Christ, I am sick of people who rattle on about this without knowing what they are talking about.

      "A viable platform has to support closed applications" - no shit, Sherlock. You can write closed apps with Qt. Just buy a license and go to it. The thing is dual-licensed.

      The GPL is not "less free". The GPL enforces user freedoms. The LGPL gives developers freedom. Which do you care more about? (Hint: you aren't a developer).

    6. Re:GTK is OSS by Decameron81 · · Score: 1
      Christ, I am sick of people who rattle on about this without knowing what they are talking about.


      I'd like to point out that you shouldn't read slashdot comments if you get "sick" of people expressing their ideas.

      "A viable platform has to support closed applications" - no shit, Sherlock. You can write closed apps with Qt. Just buy a license and go to it. The thing is dual-licensed.


      Pay that fee when I have a platform that lets me develop for free? And which one do you think that I, as a commercial developer, will be choosing? A platform's popularity can also increase by how many applications it offers to the end user and it should support whatever the coder wants to do. If it's closed sourced applications, so be it. The idea that you should enforce the open source choice to other people is just as mistaken as the idea that open source is bad. Freedom for the developer to choose and freedom for the end user to choose is the path.

      The GPL is not "less free". The GPL enforces user freedoms. The LGPL gives developers freedom. Which do you care more about? (Hint: you aren't a developer).


      Both the freedom of the developer, who works for a living, and the freedom of the end user. Neither one is less important. Freedom to develop as you wish, and to choose the applications you want.

      Do you think that any MS Windows user would feel you are protecting their freedom if you wiped their drives and installed a linux distro on it?.

      Think twice next time before telling other people they don't know what they're talking about,
      Diego Rey
      --
      diegoT
    7. Re:GTK is OSS by steveha · · Score: 1

      You've got to pay Trolltech a $2000 per-developer fee, but if you're making commercial apps, you should have no problem

      So much for the shareware market. So much for a simple app that costs $15.

      $2000 is huge.

      And what happens if TrollTech goes insane and starts charging ten times as much? Or starts demanding that you sign weird licenses?

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
    8. Re:GTK is OSS by tepples · · Score: 1

      So much for a simple app that costs $15.

      Usually, a "simple app that costs $15" will not contain patented methods. An app that does not contain patented methods will quickly attract an effort to clone it for free and Free.

    9. Re:GTK is OSS by steveha · · Score: 1

      If you need to invest $2000 to write an app you want to sell for $15, you won't even write the $15 app.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
    10. Re:GTK is OSS by be-fan · · Score: 1

      When that happens, the FreeQt foundation gets together and decides whether the behavior constitutes a breach of the FreeQt agreements, and decides whether to BSD-license the library.

      Also, and I'm not the first to say this, shareware is dead. It has been superceded by OSS software.

      --
      A deep unwavering belief is a sure sign you're missing something...
    11. Re:GTK is OSS by alienw · · Score: 1

      A viable platform has to support closed applications.

      Exactly. That's why TrollTech sells commercial licenses for Qt. Pay them a token sum of money and develop closed-source apps at your leisure.

    12. Re:GTK is OSS by asciiRider · · Score: 2, Insightful

      this userLinux stuff sound really great -

      - it needs to support closed apps
      - it needs to have less choice (1 desktop)
      - one scripting environment

      might as well stick with windows.

      I read an article today about the mozilla platform, all of this talk about kde vs. gnome helps me understand that article better. If I was a developer I'd probably just choose mozilla and have it run everywhere...heck, even java would help out those worried developers, hehe...

    13. Re:GTK is OSS by steveha · · Score: 1

      I don't know why you are bringing up the FreeQt agreements. I was talking about TrollTech going crazy and jacking up the developers' price. My point is that TrollTech has reserved the right to set the price for developers, and they might decide to charge more later. Especially if KDE becomes hugely successful.

      TrollTech is free to charge what they want for Qt; it's theirs. I don't care. But we know how much a developer needs to pay to write payware for GNOME: $0. This makes the choice of GNOME for UserLinux a sensible one.

      shareware is dead. It has been superceded by OSS software.

      Don't be silly. There's still plenty of shareware around. I just paid the license fee for some shareware four days ago.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
    14. Re:GTK is OSS by ivan256 · · Score: 1

      Christ, I'm sick of people who don't know what they're talking about telling other people they don't know what they're talking about.

      (Hint: you aren't a developer)

      Most companies *are* developers. They write internal applications. They care about developer freedoms at least as much as user freedoms.

      Now, if you have to pick a platform and one has zero licensing costs, but both are (arguably) equals in other ways, which do you pick?

    15. Re:GTK is OSS by ivan256 · · Score: 1

      this userLinux stuff sound really great -

      - it needs to support closed apps
      - it needs to have less choice (1 desktop)
      - one scripting environment


      May as well have it just like all the other distros, huh?

      Seriously, if you don't like it, pick a different one. User Linux is being made because some very smart people with the ear of businesses think it will meet the needs of business users better. It's not one size fits all, and it's not out there to shut the other distros down.

    16. Re:GTK is OSS by ivan256 · · Score: 1

      Once you've switched to the Qt commercial license you've left behand the reasons you switched to an open platform in the first place. If you're going to buy a Qt developer licens, then why wouldn't you just stick with Visual Studio?

  38. Usability (i.e. the idiot interface) by AMystery · · Score: 5, Insightful

    I've used linux for years, from back at redhat 4.2 I believe. I've also used a number of the GUIs and I have some pretty strong feelings about them. In every distribution that I've dealt with, Gnome just works. Sure, it has some bugs, but in general its a smoother user experience. I'm sure you can do everything in KDE, but that's if you want to spend hours configuring it. Gnome just works. I do like the power and options available in KDE, but if I was starting with linux, I wouldn't want that. In fact, when I migrate people to linux, they get Gnome. Once they learn the OS, then I might mention there are other GUIs, but for a migration or business oriented distro, go with the one that just works.

    That said, I read the article *gasp* and it was about supporting the environments, not the relative qualities of the GUIs and I have to agree that its easier to standardize on one development environment.This is a good move for a new distro and helps to keep their costs down and quality up. I just hope that the fallout from the geeks doesn't kill them before they get going. I'd love another good Debian based distro

    KDE is great, but too much is exposed. I don't need three text editors in a right click menu, I want one that just works, although I generally use vi and they never include that in the click menus:(

    1. Re:Usability (i.e. the idiot interface) by leandrod · · Score: 1
      > you can do everything in KDE, but that's if you want to spend hours configuring it. Gnome just works.

      Actually in Debian Gnome tends to be a little flaky. Nothing that the integration job proposed by Bruce for UL wouldn't be able to fix.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    2. Re:Usability (i.e. the idiot interface) by SyntheticTruth · · Score: 1

      Regarding your first argument:

      The first time you run KDE, a nice wizard walks you through some very basic options, and that's it. A new user would not have to be concerned with the power of KDE's customability. KDE as well "just works" out of the box, as I've seen giving two brand new computer users (note, *computer* newbies, not just *nix newbies) a KDE desktop. It was no more harder than a new user to Windows, etc.

      I do agree with the over abundance of Text apps in KDE. WTH? Tho, on the other hand, I did teach myself PyQT by writing yet another text editor. lol

    3. Re:Usability (i.e. the idiot interface) by Anonymous Coward · · Score: 0

      KDE is great, but too much is exposed. I don't need three text editors in a right click menu, I want one that just works, although I generally use vi and they never include that in the click menus:(

      It's better than it used to be. There's just Kwrite and Kate as text editors now, and they both fit very different niches. Kwrite's the usual straightforward text editor, while Kate is practically a full-blown development environment. It's great! They do use the same editor widget, so they're very similar to use, except Kate has lots of additional features which your average user won't use, but any developer would love.

      Anyway, right-clicking on a text file in Konqueror (KDE 3.1.4, SuSE 9.0) gives me four applications to choose from. Kwrite is first, and is the default, Emacs (!) is second, but only because I have it installed, next is KWord and last is Kate. With the exception of Emacs, they're prefectly sensible choices for *.txt, and middle-clicking just opens with Kwrite, the default...

      At this point, I'm off to uninstall Emacs. I hate it, and don't know why I installed it in the first place. :)

    4. Re:Usability (i.e. the idiot interface) by LordMyren · · Score: 1

      gnome runs smooth alright, smooth like molasses.

      i dont know about operational overhead when running, but in terms of loading a program gnome takes absolutely forever. i can grab a soda while my 866 mhz crusoe (/w 5400 rpm hd) loads gedit. i find it flabbergasting.

      kde/gnome take vaguely in the same domain of time to load, but their respective programs... whew... i cannot believe. gedit, the basic notepad for gnome ldd's 56 libraries, many of them non trivial. kedit 38, but it loads in under half the time. that is insane.

      if it werent for the speed issue, i'd be running gnome. gnome 2.4 is very very slick. i ran it for a while on my laptop before i just got fed up with waiting. its fairly responsive once loaded, but the load time and fluxbox being faster...

      then again, most people these days run computers four times faster than my piddly crusoe.

      Myren

    5. Re:Usability (i.e. the idiot interface) by AMystery · · Score: 1

      Speed is a good argument for running KDE, but not for a new computer user. They want it friendly, fast is a distant second, actually its probably third behind games. I use gnome on my desktop just because of how reliable I've found it. I've fragged KDE many times but I've found it harder to really break Gnome. Sure, I can get a soda while something loads, but I can generally do that, I'm running a celeron 700. Also, we are arguing the technical wisdom of picking one GUI over another, but that's not really the important part. A good newbie linux distro brings more people in which gets us closer to a critical mass and the all important application developer support. I horribly miss Dreamweaver and photoshop. Gimp is nice, I've done some good things in it, but its not what I'm used to. Bluefish is also nice, but that's just silly in comparison. We have the better OS, we just need the support so we can make it usable for everyone, not just for the subset that can change how they work to accomodate what is available or what a geek thinks they need.

      I love having the power to inspect the code of everything I run, but that is almost never an issue for me. I want things to just work. I'd also like an easier upgrade path. I'm still struggling with 2.6. Having some USB issues but I'll get it eventually. My mom however...

    6. Re:Usability (i.e. the idiot interface) by StarCat76 · · Score: 1

      KDE is great, but too much is exposed. I don't need three text editors in a right click menu, I want one that just works, although I generally use vi and they never include that in the click menus:(

      I know this is comment was in jest, but you can set KDE to open them up with vi by just adding vi to the mime/file association type and having it open in console.

    7. Re:Usability (i.e. the idiot interface) by Elektroschock · · Score: 1

      the editor variety will be reduced as soon as kate supports a few lacking features. Esp. bidi. 3.2 will be a great improvement.

  39. Am I missing something? by Whatanut · · Score: 2, Insightful

    Is there are a reason KDE can't be used anyways? You'll just have to download it instead of it being distributed with the initial install.

    If you like KDE... keeping using it. For the business world they get less complication and you still have choice.

    --

    yvan eht nioj
  40. Standards... by mythosaz · · Score: 1

    I will be modded down for heresy, but...

    Until there is *The One True Linux Desktop*, you're going to have trouble getting the mainstream to accept it. You saw successes with Redhat (ok, maybe a bad example now) because we knew that Redhat n+1 was going to have roughly the same desktop as Redhat n.

    There is no -1 "I disagree"

  41. Then don't name it UserLinux by Fefe · · Score: 5, Interesting

    If Bruce Perens honestly wants this to be a Linux for business people (instead of the unwashed masses of normal users), he should not call it UserLinux but BusinessLinux or whatever.

    I'm a user and I want KDE. Most people agree that KDE is more mature and robust than GNOME anyway, so from a business point of view it is obviously better suited. KDE also has more stability from other points of view, for example it doesn't change the default window manager for each major release, the groupware and the kiosk mode are very important as well. I'm not talking down on GNOME here, but KDE is more mature and all the major business wins Linux has had so far were with (and because of) KDE.

    I think the maintainability argument is a fallacy. Admins already are completely unable to contain the complexities of different applications. Each major application and framework calls for its own class of admins. In large companies you have a Cisco admin for the networking infrastructure, you have an Oracle DBA, you have the Apache guy, you have the SuSE/RedHat/whatever admin, and the 5000 Windows reboot monkeys. Nobody expects all of this to go away if they switch to Linux. There will still be complexity. Deciding to standardize on GNOME will not make OpenOffice any less daunting to install and maintain in a multi-user environment. Or Mozilla. Or Apache.

    And if we accept the argument, we would clearly choose the platform with the more robust administration interface, which clearly is KDE. kcontrol is integrated and pretty much all-encompassing, while GNOME is constantly shifting from CORBA over XML to a binary registry and back. GNOME has become so bad that they actually added a regedit style "config editor" and apparently really expect users to use it to configure applications. Hint: This is the kind of nightmare people want to get rid of when they switch from Windows to Linux.

    Anyway, I don't see why we need to standardize on a GUI, and if we do, we standardize on KDE, of course, as it fulfils more of the requirements businesses have, hands down.

    1. Re:Then don't name it UserLinux by Anonymous Coward · · Score: 2, Informative

      Wrong. He is applying rule of economics and business to his decision. Businesses can develop and distribute proprietary applications in Gnome w/o paying any license fee! With KDE, they cannot! In order to develop/distribute proprietary software, they need to pay a $1300 license fee to TrollTech.

      Which option is more business friendly?

    2. Re:Then don't name it UserLinux by ChangeOnInstall · · Score: 2, Informative

      kcontrol is integrated and pretty much all-encompassing, while GNOME is constantly shifting from CORBA over XML to a binary registry and back. GNOME has become so bad that they actually added a regedit style "config editor" and apparently really expect users to use it to configure applications. Hint: This is the kind of nightmare people want to get rid of when they switch from Windows to Linux.

      This statement is incorrect. Much (all?) of Gnome's configuration data is handled by GConf. GConf is a registry, but all the data is stored in XML. Just look at your .gconf directory if you have any applications that use it. You'll find nothing but XML files.

      The "registry editor" you're referring to is gconf-editor. Gconf-editor is not intended to be used by end users. It's quite similar to the windows registry editor (though it does seem to be better layed-out than that). I've personally only had to use it to make very geek-oriented adjustments, such as binding keys to launch terminals and skip songs in XMMS.

      There's very little conceptual difference between storing config information in a bunch of "dot-files" off your home directory and storing them in a directory hierarchy containing XML files off the ~/.gconf directory.

      --
      What has *science* done?!? -- Dr. Weird (ATHF)
    3. Re:Then don't name it UserLinux by Anonymous Coward · · Score: 0

      How many times does this need to be said??
      $1300 is pittence compared to the money needed to employ programmers. Even on small commercial projects, the reduced development time you get by using QT over GTK (due to the superior toolkit design, commercial support and better doccumentation) makes the total development cost signifigantly lower with QT.

      Furthermore, many real commercial applications are already using QT (opera, theKompany, nasa, adobe, ...). Where are all these commercial apps that are developed with GTK because it's free-as-in-beer?

    4. Re:Then don't name it UserLinux by Anonymous Coward · · Score: 0

      Lies!! you are not a user. You are a Power User. Get it right. Users are the ones who use the computer because its a computer. Not because they know KDE is out there in the woods hiding ready to play with you.

    5. Re:Then don't name it UserLinux by Anonymous Coward · · Score: 0

      What if they made GTK good like sex?

    6. Re:Then don't name it UserLinux by caseih · · Score: 2, Insightful
      I'm a user and I want KDE. Most people agree that KDE is more mature and robust than GNOME anyway, so from a business point of view it is obviously better suited. KDE also has more stability from other points of view, for example it doesn't change the default window manager for each major release, the groupware and the kiosk mode are very important as well. I'm not talking down on GNOME here, but KDE is more mature and all the major business wins Linux has had so far were with (and because of) KDE
      Yes but you can't develop proprietary apps (for good or bad) using KDE without paying the trolltech licensing fee.
      nd if we accept the argument, we would clearly choose the platform with the more robust administration interface, which clearly is KDE. kcontrol is integrated and pretty much all-encompassing, while GNOME is constantly shifting from CORBA over XML to a binary registry and back. GNOME has become so bad that they actually added a regedit style "config editor" and apparently really expect users to use it to configure applications. Hint: This is the kind of nightmare people want to get rid of when they switch from Windows to Linux.
      Actually the gconf configuration system is what the registry should have been. It's not really binary at all. Instead it's a distributed hiarchy of xml entries (using the file system to provide for folders and the tree structure). It works very well and you can edit it with vi. gconf-editor is there, and it works, but it's still plain xml text and probably will remain so. As for inter-process communication, KDE and GNOME are converging on the same mechanism (I think it has something to do with DBUS) that is probably rpc via xml, as defined in the freedesktop specs.

      I find your comments on gnome show a bit of ignorance as to what really goes on in with gnome. Gnome is quite a bit better designed than you think. Whether or not it's better than KDE isn't the issue here. The main issue is providing an environment that lends itself to development needs of businesses (the LGPL actually does us a favor here). The user aspect of that is another story. All businesses have a few proprietary inhouse software packages that they would want to port with the minimal effort and expense (and licensing is part of that).

      All that said, KDE is a wonderful interface. I am constantly driven nuts, though, but the insistance on using the backwards Microsoft way of placing buttons in dialogs. Apple got that one right.
    7. Re:Then don't name it UserLinux by LordMyren · · Score: 1

      i think part of the reason he's choosing just GNOME is to allieviate the 300 people for 300 tasks problem.

      ps: a config editor that manages my 500 .proggie directories and files would be spiff.

    8. Re:Then don't name it UserLinux by Anonymous Coward · · Score: 0

      I both agree with you and disagree.

      On the first point, I agree completely. "UserLinux" is a weak name for a business-oriented distro because it's technical person terminology. "User" is the technical person's term for a non-developer. If you want your regular Joes to be comfortable with it, you should name it something they can relate to, not some term that only makes sense to technical people. It would be similar to making a bicycle that is for casual users and calling it NoToeClipsBicycle. Because, as a bicycle geek, one of its distinguishing features to you would be that it has no toe clips. But the casual user doesn't want toe clips, maybe doesn't know what toe clips are, and likely doesn't understand the significance of not having toe clips (which that it correlates with simpler bicycles and less-experienced riders). I have a hard time thinking up a better name. How about RegularHumanLinux? NormalGuyLinux? Even NonGeekLinux or NonTechieLinux. I would suggest SimpleLinux but that would probably imply that it's less capable, which wouldn't be so great.

      Anyway, on the second point, I disagree. The maintainability argument isn't a fallacy. Yes, there is complexity all over the place, and that's a fact of life. Paring it down to one GUI won't eliminate that complexity. Still, installing some insulation in my house won't reduce my heating bill to zero, but it will save me money. In other words, the fact that it's impossible eliminate complexity doesn't mean we should make no effort to reduce complexity.

      By the way, installing Mozilla, Apache, or OpenOffice and maintaining it in a multi-user environment shouldn't be all that difficult. In some cases, you just install it on the NFS server one time and live happily ever after. If that isn't workable because of having a single point of failure, then rdist or rsync it out to every client. Disks are cheap enough these days that you can have a separate copy of /usr/local on every desktop box. Of course, it's slaved to a master copy, but the user doesn't have to know that or care about it. (And to you developers who think it's OK to write into /usr/local at some time other than software install time: YOU'RE WRONG and you should STOP! Thanks for listening.)

    9. Re:Then don't name it UserLinux by Fefe · · Score: 2, Insightful

      How many companies do you know that actually create their own GUI applications? And I'm not talking about some internal admin interface here that some guy wrote for himself. Obviously, web interfaces don't count either, and neither does Java stuff.

      And if an in-house application gets written, the planning stage until even the decision whether something will be written is done, even that phase easily costs a hundred fold of the Qt fee. Then you count in the time and productivity lost to internal training sessions, and you end up with numbers where the $1300 don't even register in the 0.x percentage range.

      Also, since in-house applications are used internally and not given away, you don't need a license that allows selling the code, the GPL is perfectly fine for that.

      To make this very clear: if there is anyone who is actually making graphical applications for Linux, and this argument has to carry any weight, it's neither a big company nor is it an in-house application. And if you expect to make money on an application, labor cost by far dwarfs any fixed hardware or licensing cost. Heck, MS Visual C++ alone probably costs more than the Qt license, and do you know any Windows development company who ever went under because of the MSVC license cost?

      Neither do I.

    10. Re:Then don't name it UserLinux by orkysoft · · Score: 1

      EasyLinux? Or is that too dangerous legally, with all the Easy.+ names being tm of that Greek businessman?

      EasyLinux sounds good to me. It doesn't sound like it's less capable than regular Linux, as SimpleLinux would sound, and it doesn't sound hard to use either (duh).

      --

      I suffer from attention surplus disorder.
    11. Re:Then don't name it UserLinux by Anonymous Coward · · Score: 0

      TrollTech says that you can't use the GPL/Qt for internal applications, which is a huge FUD factor against that plan.

      (This makes some sense when you consider that the GPL is a distribution licence, so an application hasn't really been "GPLed" until it has been distributed to someone.)

    12. Re:Then don't name it UserLinux by 0x0d0a · · Score: 1

      I'm a user and I want KDE.

      Fine. Bruce is making a simple distribution with one GUI. He's making it to appeal to folks that don't want to muck about with TrollTech, and he said that he's more than happy to see folks making competing KDE-based distributions. That's just not how he wants to spend his time. He even pointed out that you're free to use his work to base your own on.

      Most people agree that KDE is more mature and robust than GNOME anyway,

      Not the people I talk to. At one point, this was certainly true.

      KDE also has more stability from other points of view, for example it doesn't change the default window manager for each major release

      KDE has had three major releases. In two of those, the window manager changed.

      GNOME has had two major releases. In two of those , the window manager changed.

      Not a *huge* difference is window manager stability. Furthermore, it doesn't look real likely that the WM will change in either of them any time soon.

      For that matter, the default WM is a distro-specific choice.

      Nobody expects all of this to go away if they switch to Linux. There will still be complexity.

      He isn't talking about complexity from an end-user or administrator point of view, as far as I can tell, though that is certainly an issue. He was talking about how many resources the UserLinux distribution has.

      kcontrol is integrated and pretty much all-encompassing, while GNOME is constantly shifting from CORBA over XML to a binary registry and back.

      Uhhh....what? What you just said makes absolutely zero sense.

      GNOME has become so bad that they actually added a regedit style "config editor" and apparently really expect users to use it to configure applications.

      Actually, I'm not a gconf fan, and think it isn't a good idea -- probably the main drawback of GNOME. That being said, (a) gconf is very, very technically different from the registry, and (b) it's not really intended for end user use.

      Anyway, I don't see why we need to standardize on a GUI, and if we do, we standardize on KDE, of course, as it fulfils more of the requirements businesses have, hands down.

      You want a KDE-based distro, get off your butt and make a KDE-based distro. This is *not* rocket science -- lots of people already package things for you and you can reuse the non-GNOME portions of UserLinux. It only takes a couple of people to maintain a distro (especially a slow-moving distro that will appeal to businesses). Complaining about this is just so *stupid*. I don't say "those KDE people waste so much time working on their dumb KDE software". It's what they *want to do*. It's their volunteer time. You're free to put in your own volunteer time wherever you want, but don't bash people who are volunteering effort.

    13. Re:Then don't name it UserLinux by sydb · · Score: 1

      The main issue is providing an environment that lends itself to development needs of businesses (the LGPL actually does us a favor here). The user aspect of that is another story. All businesses have a few proprietary inhouse software packages that they would want to port with the minimal effort and expense (and licensing is part of that).

      However there is nothing stopping those business developing in-house applications in Qt as long as they don't then distribute them outside the company. The GPL only applies if you distribute.

      The argument is more about enabling commercial software development. Personally I think there's something wrong with choosing a default desktop which would give one company (Trolltech) a position for financial gain, and if UserLinux took off in the way everyone hopes, with a KDE-default, I'd be surprised if you didn't see changes in pricing and/or licensing. Certainly, I'd be buying shares in TT.

      --
      Yours Sincerely, Michael.
    14. Re:Then don't name it UserLinux by sydb · · Score: 1

      TrollTech says that you can't use the GPL/Qt for internal applications, which is a huge FUD factor against that plan.

      (This makes some sense when you consider that the GPL is a distribution licence, so an application hasn't really been "GPLed" until it has been distributed to someone.)


      No, this makes no sense at all, and if TrollTech really do say that, they are wrong. I couldn't find that statement on their web site, do you have a link.

      Downloading Qt from the TT website is the act of distribution, at that point the GPL gives me the right to do whatever I like with that code including linking and changing it provided I don't redistribute it. That's the GPL, TT can't change it.

      --
      Yours Sincerely, Michael.
    15. Re:Then don't name it UserLinux by Anonymous Coward · · Score: 0

      http://www.trolltech.com/developer/faqs/free.html

      It doesn't really matter what slashbot IANALs think, corporations are unlikley to defy the wishes of a software publisher. That effectively eliminates GPL/Qt as a choice for internal applications, regardless of our interpretations of the GPL.

    16. Re:Then don't name it UserLinux by inc_x · · Score: 1

      > Which option is more business friendly?

      Given the amount of commercial software available based on Qt it seems that businesses rather spend $1300 on Qt than use GTK. So that makes Qt-based KDE the more business friendly option.

    17. Re:Then don't name it UserLinux by sydb · · Score: 1

      Thanks for that - I still think they can't do that, but you're right, corporations won't want to challenge it.

      Yet another reason for Free Software people to keep away from TrollTech - they spread FUD. Interestingly they have employed a developer - Lorn Potter - to poison the opie-devel mailing list with propaganda. I don't like them.

      --
      Yours Sincerely, Michael.
    18. Re:Then don't name it UserLinux by scrytch · · Score: 1

      > Heck, MS Visual C++ alone probably costs more than the Qt license

      See below.

      http://www.trolltech.com/products/qt/pricing.htm l

      http://msdn.microsoft.com/vstudio/howtobuy/prici ng .aspx

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
  42. Dumb by swagr · · Score: 1, Flamebait

    Perens and his cohorts are applying the rules of communist economics to this projects requirements. How many of the end users they hope for are participating in this requirements and design phase?
    Why even bother calling it USER Linx?

    They should take a look at how a good project involves it's target users. http://www.intellij.net

    --

    -... --- .-. . -.. ..--..
    1. Re:Dumb by MazTaim · · Score: 2, Insightful

      Obviously you don't want userlinux to make their own decisions. Why else would you post something so rediculous? In fact, from your post, I would call YOU more communist than they are.

      The whole point of OSS is to allow freedom of choice. UserLinux is making a "choice" (notice the key word "choice") to include only one GUI.

      They have the choice to either include KDE or exclude KDE. You may chose to use KDE and forget about Gnome. Do you get communist remarks made to you because you forced your OS to only use only KDE?

      They aren't forcing you to choose their distribution. You don't like it, get another distro and quit your bitching.

    2. Re:Dumb by swagr · · Score: 1

      My point is this:
      Forget what the developers of UserLinux think.
      What do the potential users think?

      Sure anyone can put together whatever distro they want. Just don't do it under the guise that it's for some 3rd party's benefit, unless that 3rd party gets to call the shots.

      --

      -... --- .-. . -.. ..--..
    3. Re:Dumb by MazTaim · · Score: 1

      Users Schusers. There is still no loss of choice.

      Benefits are ultimately for the person or persons making the distribution. An ideal distribution (or as close to an ideal distribution) is one that is made by the user. Since most users really don't want or know how to roll their own distro, you are never going to please every user. "Who cares if you don't like it. I made it, use it if you like."

      As for 3rd party benefits. It all goes back to the fact that the distribution is made ideally for those who created the distribution. Who cares who wrote the software, you want to use it, it will be included as you create the distribution. If you don't want it, it's not in your distribution.

      There is no "guise." They threw everything out on the table. They didn't ask anybody to like it or dislike it, just as I wouldn't require you to like what I am saying right now.

      Or after reading your last sentence again, Do you not think that one of the primary reasons people don't currently use OSS distributions is because they are over-burdened by choice? Choice is good, but you will get nowhere when you have too much choice. How does one find out what the users want? All they can do is survey people. I believe surveys have been done more than enough. I personally agree with UserLinux if we are to see linux hit mainstream desktops. I probably won't use UserLinux since I don't particulary care for a Gnome-only desktop. I use and will continue to use Gentoo until they start putting more "cons" than "pros" into their distro.

      If you are afraid of the possible future lack of choices, then you really need to do further research. Plenty of other options are available. And will continue to be available. That's the beauty of OSS. I believe Knoppix has the best shot currenty (as it is alreay a real and tangible distribution) OSSes best shot at mainstream distribution.

  43. UserLiGNUx by SharpFang · · Score: 1

    UserLiGNUx. Sounds OK and with the right capitalisation

    --
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
  44. I'd include a "softer wm'... by huckda · · Score: 1

    and let gnome and kde be add ons that are not included in the distros..

    --
    "Just Smile and Nod." --Huck
  45. KDE is not to be ignored-Horse head by Anonymous Coward · · Score: 0

    "...while Bruce Perens has posted a response."

    and

    "This is a mistake if they don't include both."

    Pistols at dawn.

    or
    [Bugs Bunny]
    "This means war!"

  46. here's a screenshot of emacs by SweetAndSourJesus · · Score: 4, Funny
    --

    --
    the strongest word is still the word "free"
  47. Commercial development requires payments. by khasim · · Score: 4, Informative

    If you want to do commercial development with Qt, you have to pay a one time fee.

    Bruce objected to that and is putting together a distribution that has NO payment requirements for commercial development.

    That's his approach, that's his goal.

    Whether he will succeed or not, only time will tell.

    1. Re:Commercial development requires payments. by Anonymous Coward · · Score: 0

      So Perens has decided to release a commercial royalty free version of the qt libraries? That's nice of him. Maybe he can release a free version of microsoft office too.

    2. Re:Commercial development requires payments. by Brian+Knotts · · Score: 2, Insightful
      If you want to do commercial development with Qt, you have to pay a one time fee.

      I take it when you say "commercial," you actually mean "closed-source."

      If you want to develop closed-source software, based on someone else's toolkit, you should have to pay for the privilege.

      Another reason why GPL is the best license for these sorts of things.

    3. Re:Commercial development requires payments. by ultrabot · · Score: 1

      If you want to develop closed-source software, based on someone else's toolkit, you should have to pay for the privilege.

      Why, exactly?

      --
      Save your wrists today - switch to Dvorak
    4. Re:Commercial development requires payments. by Rahga · · Score: 1

      "If you want to develop closed-source software, based on someone else's toolkit, you should have to pay for the privilege. "

      What if I work for a company that encourages me to take part in these GPL projects and LGPL libraries, while developering their own closed source, commercial application that runs on top of that platform? I would do that with Qt, because it makes no sense to pay royalties on something I took part in developing. Whereas with Gtk+, I have incentive to know that profit-taking on my labor is not something that I can't take part in. (Example, look at the guys who sell WinGimp variants.)

      The fact of the matter is that this happens all the time. If both Gtk and Qt forced commercial closed-source users to pay a royalty, I'd probably look for yet another toolkit to use instead.

    5. Re:Commercial development requires payments. by Brian+Knotts · · Score: 1

      You don't see the irony of people bitching about someone charging them a fee to use their toolkit, when they intend to do exactly the same thing with the software they are writing?

    6. Re:Commercial development requires payments. by ultrabot · · Score: 1

      You don't see the irony of people bitching about someone charging them a fee to use their toolkit, when they intend to do exactly the same thing with the software they are writing?

      No, I don't. Toolkit is a different thing from an application. I would never use a commercial TCP/IP stack, for example.

      --
      Save your wrists today - switch to Dvorak
    7. Re:Commercial development requires payments. by Anonymous Coward · · Score: 0

      If you want to do commercial development with Qt, you have to pay a one time fee.

      No your don't. If you want to do closed-course development with Qt you have to pay a one-time fee. Get your facts straight - GPL != non-commercial. Ask Redhat.

    8. Re:Commercial development requires payments. by Brandybuck · · Score: 1

      If I had my druthers, I would have Qt be under the MIT license, just like XFree86, freer than anything GNU puts out. But I don't own Qt, so I don't get to make the decisions.

      But fair is fair. Just like in any other business, if you expect your customers to pay you, then you should expect to pay your suppliers.

      --
      Don't blame me, I didn't vote for either of them!
    9. Re:Commercial development requires payments. by Brandybuck · · Score: 1

      Bruce objected to that and is putting together a distribution that has NO payment requirements for commercial development.

      Companies that purchase or otherwise aquire UserLinux aren't going to be doing to writing GUI end user applications. This distro is meant for the corporate desktop, not proprietary development workstations. These companies aren't going to expect all of their proprietary development tools to be freely downloadable. They certainly don't today when they buy Windows, Solaris or AIX.

      Think about it before spouting off. If I buy Solaris I have to pay extra for the compiler and Motif if I want to write an application for their desktop. If I buy Windows I have to pay extra for the compiler and MFC/.NET if I want to write an application for their desktop.

      They won't care if the underlying toolkit of their desktop requires payment for development of their proprietary product. There's nothing stopping them from downloading GTK+. Frankly, if they're too dumb to do even that, they shouldn't be in the development business.

      --
      Don't blame me, I didn't vote for either of them!
    10. Re:Commercial development requires payments. by Charlotte · · Score: 1

      I would never use a commercial TCP/IP stack, for example.

      For some computers there still are no freely available TCP/IP stacks. People still make a very good business selling commercial TCP/IP stacks e.g. for mainframes.

      Even on PCs none were available until Linux or BSD 386 (which is one of the reasons Linus wrote Linux). The DOS ones truly sucked :).

    11. Re:Commercial development requires payments. by Anonymous Coward · · Score: 0
      Damn! I don't think I've ever seen a scentence with so many double-negatives in it. Exactly what did you try to say? You lost me before I got half-way through.

      I actually read your post twice...

    12. Re:Commercial development requires payments. by lokedhs · · Score: 1
      No your don't. If you want to do closed-course development with Qt you have to pay a one-time fee. Get your facts straight - GPL != non-commercial. Ask Redhat.
      Amazing how many people doesn't read the licenses.

      I'm not only referring to you, but all the other people posting in this thread.

      Thing is, you can't even do all kinds of open source development with a GPL'ed library. You need to use the GPL license yourself. No others are acceptible.

      The kind of tough commercial licensing Qt has is even worse than that of Windows. Sorry, I just don't like it.

      Now please mark me offtopic. I deserve it. This really has nothing to do with the article.

    13. Re:Commercial development requires payments. by tepples · · Score: 1

      I would never use a commercial TCP/IP stack, for example.

      Never? The Microsoft Windows OS contains a "commercial TCP/IP stack" which is also proprietary. So do many LAN router appliances.

    14. Re:Commercial development requires payments. by AstroDrabb · · Score: 2, Informative
      Did you RTFA?
      At the core of UserLinux is a not-for-profit entity in charge of the Linux distribution, with engineering-by-meritocracy as in the Linux kernel. Surrounding that non-profit are for-profit companies that are in the business of providing service and engineering for the UserLinux distribution.
      So basically the WHOLE POINT of UserLinux is for a FREE Linux distro for for-profit companies to provide COMMERCIAL services and applications. QT takes the FREE out of that picture, while GTK+ being LGPL still allows those for-profit companies to develop closed source proprietary applications/services. These for-profits are going to all collectivly support the non-profit UserLinux, thus spreading the cost out and making it very cheap for each for-profit. Why would those for-profits want to fund the development of UserLinux and then have to turn around and pay ONE vendor to be able to develop on the system that the for-profits have already paid for?
      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    15. Re:Commercial development requires payments. by Natalie's+Hot+Grits · · Score: 1

      BZZZZZZZT WRONG... ERROR...

      With QT, you have the choice: QPL, GPL, or QT Pay.

      The QPL allows you to write software falling under the "open source" definition. The GPL allows you to write software falling under the GPL, and the QT Pay license allows you to write closed source software. The only license that charges is the pay license. The QPL and GPL are both FREE. And the QPL and GPL together support all forms of free and opensource software. Before QT was GPL'd, the QPL was the only free license, and it supported all free software licenses, including BSD, GPL, MIT, Artistic, etc..

      The ONLY REASON that Qt added the GPL option was because RMS had a fit and started the GNOME project because RMS thinks that the QPL is incompatible with the QPL (which BTW, RMS is really the only person who really thinks that)

      In other words, your post is uninformed, ignorant, and just plain flamebait.

      --
      Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.
    16. Re:Commercial development requires payments. by Brandybuck · · Score: 1

      So you're saying a key component of the UserLinux distribution is the involvement of PROPRIETARY software development companies?

      p.s. You don't need to release proprietary software in order to provide service and support for free software.

      --
      Don't blame me, I didn't vote for either of them!
    17. Re:Commercial development requires payments. by Elektroschock · · Score: 1

      Well and if you write GPL software you don't have to pay. I think the business model of Trolltech is quite fair and has a gpl licensing incentive while the gtk world causes a multi-license environment.

      When you write "commercial" (here=nongpl software) you have to pay for the toolkit. Well, that's very normal and the fee isn't very high.

      qt is really wonderful, I believe its the best structured toolkit for this purpose.

      What applications weren't written because companies coulnd't afford QT?

      KDE is the leading DE on the desktop. Bruce is a nut. I also don't understand what this Userlinus was for. If he wanted a mature desktop linux distro with a few millions from the market, why doesn't he buy the company Mandrake Linux?

    18. Re:Commercial development requires payments. by ultrabot · · Score: 1

      Never? The Microsoft Windows OS contains a "commercial TCP/IP stack"

      And I don't have to pay MSFT for the privilege of creating a closed source program that uses it.

      --
      Save your wrists today - switch to Dvorak
    19. Re:Commercial development requires payments. by AstroDrabb · · Score: 1

      It appears that UserLinux will be targeted at corporations. Corporations use many, many closed source, proprietary applications. UserLinux NEEDS to make a way for those proprietary applications to get onto UserLinux without those proprietary vendors having to give up their source. I am all for Open Source, though it will take time for companies to realize that seeing their source code will not destroy their business. Until/if that happens, UserLinux need to provide a way for those vendors to deliver applications. Picking ONE desktop and GUI toolkit/API is an important step in that process. Allowing those vendors to not have to pay extra to just use that toolkit/API is another important step IMO. According to Bruce, he is working with IT companies who plan to support (read give money) to UserLinux to keep it going. They want to do that because it will be much cheaper to split the cost over many companies. The IT companies also want to be able to deliver their applications/services to the UserLinux platform. They are already paying for the development of UserLinux, it seems silly to turn around and tell them that they then have to go and pay TrollTech to use the native toolkit. Another issue is that UserLinux can customise the packages according to the supporting companies needs, including making changes to the native GUI toolkit. UserLinux will not be able to make those change to QT. IMO, UserLinux should use wxWindows as the native GUIL toolkit. Then you can have an excellent C++ toolkit that also works great under MS Windows and Mac. wxWindows also allows companies to develop Open Source or Closed source applications without the need for extra licensing fees.

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    20. Re:Commercial development requires payments. by lokedhs · · Score: 1
      It really depends on how you look at it.

      As a commercial software developer as well as open source developer, I prefer licenses that allow me to use both. I often integrate open source code with BSD style licenses in the commercial projects, and I contribute open source code to the community. It's a give and take thing.

      Qt does not give me freedom. It uses the GPL to take it away.

      And I know exactly what you're going to say now. I develop commercial applications, I should pay for it, blah blah. Windows doesn't force me to do this. Neither does OSX. Not even (formerly) commercial toolkits such as Motif used to do this.

      If a commercial software developer wants to use Qt and pay for it. Fine, I'm sure he'll be very happy. But I think it's wrong to force this policy onto all users of the system. It means that commercial developers can create a Windows and an OSX version without paying for the library, but not a Linux version. Do you seriously think that is a good thing when you are trying to take over the desktop from Windows?

    21. Re:Commercial development requires payments. by Natalie's+Hot+Grits · · Score: 1

      MS Windows XP Professional License: $299.99
      MS Office 2003 Pro: $549.99 (developer edition $$??)
      MS Visual Studio .NET 2003 Pro: $999.99
      MS SQL Server License: Big money
      MS Server 2003 License: Big money
      MS MSDN Subscription: $2,000+/year

      Mac OS X: $99
      Apple G5 Computer capable of running os X: $1000 price premium over equivilent x86 hardware.

      You must have AT MINIMUM the Windows XP Pro license, and a license to a compiler (and if your not using ms visual, why even bother on windows). This adds up. and it is REQUIRED to obtain in order to develop for the windows platform. This license must be purchased for EVERY developer involved in the project. On top of those minimums, there are all the addons, MSDN Subscriptions (which almost every big time MS Developer has), office developer, SQL server, IIS Server, etc etc etc etc... the list goes on. After adding a couple of extra licenses, you end up paying MORE than the QT license. You can say.. "i want a base which is free for everyone, including developers" but you can't use "no fees on windows" as an excuse for this statement. Not only this, but you still must pay for your GUI Toolkit on windows platform, as GTK+ is not 100% ported and working, QT costs, and MFC is a project's death card.

      In other words, your argument is void because of its purpose. Tell me you want the gratis development platform for everyone "just because" and then at least you will have a coherent argument. But the MS EXCUSE just doesn't cut it.

      I'm not pushing for GTK+ or QT to be the default, im just pushing for the stop of ignorant arguments. so here goes:

      "But I think it's wrong to force this policy onto all users of the system"

      Even IF QT/KDE became the default desktop, there is NOTHING preventing anybody from writting KDE applications using the GTK+ toolkit. There are already projects out there that do just this. and they integrate nicely, and look identical to eachother. Speed isn't an issue cos GTK and Qt libs are already required on any GUI desktop on linux anyway, just because of the diversity of the applications already in existance. If GTK+ and Qt were the only 2 major toolkits on linux desktops, that would be better than any other platform in existance: Windows, Mac OS X both have several different competing toolkits that are used commonly on every day end user desktops (QT, Cocoa, Carbon, MFC, GTK, Borland[?] Visual Basic).

      You must also realize that there aren't many GTK+ commercial/closed apps. But there are plenty for Qt already. Why is that if companies aren't willing to pay for it? (photoshop elements, theKompany software, Opera, to name a few)

      --
      Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.
    22. Re:Commercial development requires payments. by lokedhs · · Score: 1
      There are alternative compilers for Windows. A free one is Watcom. I know, I use it myself.

      MS Office? SQL Server? What are you talking about? Who needs SQL Server in order to be able to develop Windows applications?

      No one needs MSDN subscriptions. At our site we have them, I never use it though. No one else in my team (we try to write platform independent code). All the reference manuals are freely available anyway.

      XP Professional license? Mac OS X licenses? Well, an OS is needed, right?

      I have no idea what an MS Server 2003 license is. Never needed it.

      I have never said Qt is "bad". I have said it's bad when it's used as the standard or default user interface toolkit. You should be able to develop commercial applications using the standard toolkit without being controlled by a company that might change policies on a whim. What if they suddenly decide to increase the price ten-fold? And then a new developer joins the team and needs a development license. What am I to do? Start porting to GTK+?

    23. Re:Commercial development requires payments. by Natalie's+Hot+Grits · · Score: 1

      If you read my post, you would have read that the MINIMUM requirement is a windows license, with optional compiler, server OS, SQL server, MSDN, etc..

      if you want to write programs for MS server, you must shell out money for their server OS. if you want to write applications using MS SQL Server, you must shell out money to license it. if you want the support from MS, you must shell out the money for MSDN. if you want to write applications that integrate into Office, you must shell out money to buy an office developer license. etc etc etc.. I never implied that you needed all these. I simply stated you need it if you plan on developing for it.

      If you are just programing for windows XP Pro, then yea, you might be able to get away with $299.99 and use a free compilier. Good luck with MFC if you plan on making a non-trivial GUI.

      "What if they suddenly decide to increase the price ten-fold? And then a new developer joins the team and needs a development license. What am I to do? Start porting to GTK+?"

      What if MS decides to increase their windows license price ten fold? What are you to do then??? the HORROR!

      --
      Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.
    24. Re:Commercial development requires payments. by JabberWokky · · Score: 1
      So why not BSD license your Qt source? That is allowed under the QPL (not the GPL, but you get to choose one of three licenses when you do Qt work).

      Perhaps you don't understand - Qt is free to use with any open source license. If OSI says it's an open source license, you can use it. Doing that is incompatable with the GPL, according to RMS, so it's also explicitly licensed under the GPL as well. The third license is for release under closed source licenses, and that does cost money. But any open source license is free. Read the QPL.

      --
      Evan

      --
      "$30 for the One True Ring. $10 each additional ring!" -- JRR "Bob" Tolkien
    25. Re:Commercial development requires payments. by lokedhs · · Score: 1
      Contrary to what you might believe, there is no license that tells me I need to buy Windows in order to develop for it. I could use something else, like Wine.

      Contrieved example, I know. But it serves to point out the fact that the license cost is not tied to the development of commercial applications but rather to other components (in this case, the operating system that Microsoft sells).

      And what if they increase the price of the Windows license? Well, yes. We'd be SOL. It's a good thing we aren't tied to Windows then. Believe it or not, we're not tied to any license costs at all. The people that wants to use Windows when developing are free to do so (at the cost of the OS and all supporting software he needs) other people might want ot use Linux (like myself) and we should be allowed to do so. If we had chosen Qt, we'd be stuck regardless of OS.

      Open Systems are about choice. The choice of being able to choose a different OS, different hardware, etc... so that you are not in the hands of one manufacturer. Either through open standards and multiple manufacturers, or through free and open source which you can fork if you really need it. Qt does not fulfill this. It's a commercial non-free toolkit disguised as an open source solution to suck in the slashdot crowd.

    26. Re:Commercial development requires payments. by lokedhs · · Score: 1
      I know what the license says, and I find it limiting. Trolltech should be allowed to license their toolkit anyway they want. They are entitled to do so.

      However, in a (hopefully) world-wide commonly used, standard desktop environment, I should not have to pay money to develop for it, even if my application is commercial closed source.

      I think all of this biols down to what woul dhappen if someone decided to implement an LGPL-licensed version of Qt. Would trolltech attack you with patent claims, ip rights or whatever to stop you from doing so? If they did, would you still be singing their praises?

      Now, if trolltech has offcially opened their API's for anyone to implement, then many of my arguments become moot. Can you point me to documentation that clarifies this?

    27. Re:Commercial development requires payments. by JabberWokky · · Score: 1
      Not directly, but there was the Harmony project which lost momentum when Qt was GPLed. It was not harassed, and was led by several KDE developers who also had a relationship with Trolltech. There is also the fact that if Trolltech every goes out of business or removes Qt from QPL/GPL, then the last release goes to a BSD license.

      In my observation, Trolltech Gets It, whatever the "It" of open source is. Yes, they operate for profit, but they do not hide anything, leave all their code for open review, encourage free use of it for free projects and also encourage Free use of it for Free projects.

      KDElibs are all LGPL. So are the KOffice libraries. All the apps are GPL.

      --
      Evan

      --
      "$30 for the One True Ring. $10 each additional ring!" -- JRR "Bob" Tolkien
    28. Re:Commercial development requires payments. by JabberWokky · · Score: 1
      Oh, and to reply to myself as an example of how Qt does not go after any reimplementation, they officially bless projects like PyQt, which is a reimplementation of the Qt API in Python. Not quite the same as what you asked, but other than the unfinished Harmony project, it's the best example I can come up with.

      --
      Evan

      --
      "$30 for the One True Ring. $10 each additional ring!" -- JRR "Bob" Tolkien
    29. Re:Commercial development requires payments. by lokedhs · · Score: 1
      Thank you for the information. It does make me feel a little bit more relieved. Not entirely though, and it still doesn't feel "right" for me to see Qt as a core library.

      In the end, I predict that Qt will be LGPL or BSD licensed. Probably because tolltech goes out of business or they just get bored with it (or come up with a new product or something). At that time we can all agree with eachother. :-)

  48. Re:Letter "A" now internationally copyrighted by Anonymous Coward · · Score: 0
    You mean as in
    1. m
    2. aicrosoft
    or
    1. M
    2. AICROSOFT
    .
  49. Okay, so why GNOME, not KDE? by SharpFang · · Score: 2, Interesting

    Not trying to troll or anything, I just want a reasonable answer to this one:

    I heard a ton of arguments why ther should be only One. Okay, development, toolsets, all that crap.

    So, if KDE IN and GNOME IN is not an option, they go with KDE OUT, GNOME IN.
    Why not KDE IN, GNOME OUT?

    How is GNOME better than KDE?

    --
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    1. Re:Okay, so why GNOME, not KDE? by Anonymous Coward · · Score: 0

      it's just that some like to drive a ferrari (kde) and some are content with a p.o.s. pinto (gnome).

      my suggestion - don't use it. i can't think of any reason to drop a major distro for the half-baked promises of bruce mussolini.

      loserlinux is going nowhere because it's being set up as a single gui system with no flexibility - just like wincrap.

      maybe it should be called winux?

    2. Re:Okay, so why GNOME, not KDE? by c4Ff3In3+4ddiC+ · · Score: 1
      As the article on Newsforge states. The problem is when you want to develop commercial applications with QT you have to buy a license. With GNOME there is no need to purchase a license to develop commercial applications.

      It is actually quite simple:

      QT = $$$$

      GNOME = Free

      --
      *twitch*
    3. Re:Okay, so why GNOME, not KDE? by Capt.+Beyond · · Score: 1

      You are wrong. Only if you want to create closed source, proprietary software do you have to buy a Qt license.

      If you prefer closed source software, use GNOME and UserLinux.

      If you prefer open source software, use KDE.

      --
      -- "Perceptions create reality. By changing your perceptions you change your reality."
    4. Re:Okay, so why GNOME, not KDE? by Anonymous Coward · · Score: 0

      Only if you want to create closed source, proprietary software do you have to buy a Qt license.

      Right. And since, as Perens has said several times in the UserLinux propaganda, one of the points of UserLinux is to encourage proprietary software developers to develop for the Linux platform, this makes sense.

      If you prefer closed source software, use GNOME and UserLinux.
      If you prefer open source software, use KDE.

      This, OTOH, is just misinformation. Shame.

    5. Re:Okay, so why GNOME, not KDE? by 0x0d0a · · Score: 1

      Only if you want to create closed source, proprietary software do you have to buy a Qt license.

      No. There are many open source licenses that are not GPL-compatible.

      If someone made a GUI mail client containing code from pine, for instance, they'd be in violation of Qt's license rules. There would be no such problem with GTK+.

    6. Re:Okay, so why GNOME, not KDE? by prockcore · · Score: 1

      Probably because the Gnome Foundation has a hell of a lot of developer and financial backing. Compared with.. um.. er.. The Kompany.

  50. No more Trolltech Trolls.. by Drathos · · Score: 3, Informative

    Just because the Canopy Group and SCO invested in Trolltech, doesn't mean that Trolltech is part of the Canopy Group.

    Alltogether, Canopy Group owns a grand total of 5.7% of Trolltech. They have practically no say in the operations of Trolltech.

    People really need to stop dragging Trolltech's name through the mud with this pointless argument.

    (Note:: I am not a Trolltech/QT/KDE fanboy. In fact I don't use any desktop environment. My WMs of choice are Enlightenment and BlackBox.)

    --
    End of line..
    1. Re:No more Trolltech Trolls.. by Anonymous Coward · · Score: 0

      Just because the Canopy Group and SCO invested in Trolltech, doesn't mean that Trolltech is part of the Canopy Group.

      How about we try to engage in an honest discussion?

      Whatever Canopy and SCO investing in Trolltech might mean, Trolltech IS part of the Canopy Group. Or at least, Canopy say it's part of the Canopy Group, have said so for as long as I can remember, and Trolltech are not disagreeing with that and have never disagreed with that.

      If we can agree on that much then we can consider whether it matters. Playing word games to give the impression that it's open to doubt without actually saying so, doesn't achieve anything. Sure, "Just because the Canopy Group and SCO invested in Trolltech, doesn't mean that Trolltech is part of the Canopy Group" but indisputably, Trolltech IS part of the Canopy Group, agreed?

  51. It's all very simple by Pivot · · Score: 1

    Ask yourself; would Linux as a GPL'd kernel be as successfull, if it required the applications running with it either be GPL, or that the developer had to pay Linux $1000 up front for the rights to release applications for Linux under a different license?

    1. Re:It's all very simple by Anonymous Coward · · Score: 0

      A truer analogy would be:

      would Linux as a GPL'd kernel be as successfull, if it required the kernel modifications either be GPL, or that the developer had to pay Linux $1000 up front for the rights to release kernel modifications for Linux under a different license

  52. Hey buttheads!!! by Anonymous Coward · · Score: 0

    this is user-linux's project they can build it however they see fit, and KDE can go jump in a friggin lake if they don't like it...

    on some distros KDE runs great, other distros i think KDE sucks, just depends on what the developers of a particular distro want to do, you would not like it if i came up to you are started telling you what to do with your project- show user-linux the same respect!!!

  53. MOD PARENT TROLL by Anonymous Coward · · Score: 0

    I'm amazed that this has got to +5..

    yes, the canopy group still owns some shares in trolltech from when they weren't big-bad sco.

    the amount if shares they own is small and insignifigant.
    >50% of the trolltech shares are owned by trolltech's employees.

    SCO does not have and never will have a controlling interest in trolltech.

  54. Good for them by JamesKPolk · · Score: 1

    I use KDE, I write KDE applications, and I've shipped apps in the KDE release, but I say good for UserLinux.

    UI consistency is more than similar widgets and colors.

    I wish this would teach the KDE people some lessons: stop being a follower, stop throwing away your own stuff for in favor of GNOME, and start going back to doing the things that made KDE great. Any other path just leads to KDE becoming treated as a GNOME auxillary, nice to have but optional when the real work has to be done.

  55. Right on the money. by steve+buttgereit · · Score: 5, Insightful

    First: I am not a developer and I have no stake in -any- OS outside of the business value proposition it offers; yes I am a pointy-haired manager type. OK, except at home where I've got a little of everything (Sun, OS X, Linux, Windows).

    Mr. Perens approach is right on the mark. Reducing comlexity in the overall product reduces the cost to support the platform, thus making Userlinux more viable. Even if IT departments were the ones making the choice, in a lot of small & midsize shops you would have a good chance of getting a mixed desktop environment based on the 'technically correct' choice of the moment (i.e. ignoring an overall strategy that factors in business needs and downstream support... which raises costs.)

    Choice is good, but an offering where a number of those choices have been made will ultimately present a stronger picture to business. Especially at the desktop level, there is less tolerance for a wide range of choices.

    Many managers fear getting into a situation where they are so unique in their implementations that only existing staff can understand them and later choices are limited due to deviation from the norm. Even not controlling versions, of say, Windows/MS Office strategically can complicate the support picture and even reduce the overall efficency of the company. I know from the experience of cleaning it up, and from having made the mistake myself of allowing sys admins having too much choice (letting the purely technical override the strategic).

    Clearly making choices at the time of putting a distribution together makes good sense from a Corporate point of view.

  56. KDE is dying by yeremein · · Score: 0, Troll

    Yet another crippling bombshell hit the beleaguered KDE community when recently it was learned that UserLinux may not be including their desktop. Coming on the heels of the news of Novell's acquisition of Ximian and then SuSE, a once KDE-centric distro, KDE will lose more market share as SuSE switches to Ximian's GNOME desktop. You don't need to be a Kreskin to predict KDE's future. The hand writing is on the wall: KDE faces a bleak future. In fact there won't be any future at all for KDE because KDE is dying.

  57. A GOOD thing by AvantLegion · · Score: 5, Insightful
    I love KDE, but this is a good thing to me.

    Answer me this: why must every Linux distribution be about infinite choice?

    I want to see more specialized Linux distributions, and less distribs that try to present all software to everyone. Instead of distribs that have 1/3rd of their GUIs break at various times, a distrib that picks one GUI and makes sure it works is great.

    Don't like that GUI? Pick one that uses your GUI. Or pick one of the jack-of-all-trades distribs.

    But stop pressuring every Linux distrib to offer every single damn software package under the sun.

    1. Re:A GOOD thing by Rex+Code · · Score: 1

      Answer me this: why must every Linux distribution be about infinite choice?

      This is a point I've long believed in. With so many distributions favoring GNOME, is it time for some other distribution (Slackware, maybe?) to drop GNOME and focus on KDE?

    2. Re:A GOOD thing by gad_zuki! · · Score: 1

      >Answer me this: why must every Linux distribution be about infinite choice?

      Exactly. Heaven forbid they push out a distro that works well with "limited" options. There's no way to please everyone, that's why we compromise. There's also nothing wrong with Gnome, and if they went the KDE route the complaints regarding licensing would be deafening.

      I can also smell the MS disnformation campaign, "Sure Linux is free, but if you want to develop software its $1300 smack-a-roos." Or headlines with "Linux's hidden costs? Why not just buy MS?"

    3. Re:A GOOD thing by gad_zuki! · · Score: 1
      Also from Peren's proposal
      GUI desktop: GNOME. The fact that it comes with a license to develop and distribute proprietary applications is the sole reason for this decision. A long discussion on the mailing list has made it clear that GNOME and KDE are similar in technical merit and commercial acceptance at this time, leaving only the licensing issue as a basis for this decision. If you like KDE, it's still there in Debian, please go ahead and support it, and form a sub-group with everyone else who wants to. However, I think that it is better for the overall group to make a decision than to support two GUIs.
    4. Re:A GOOD thing by damiam · · Score: 1

      Slackware would never do that. It's a geek's distro, and geeks are all about choice. Knoppix, Mandrake, SuSE, Xandros, Lycoris, Lindows, Libranet, and in fact just about every commercial distro except for Fedora/RedHat ship KDE as default. I think some (Lindows at least) don't even offer GNOME as an option.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    5. Re:A GOOD thing by SQLz · · Score: 1

      Probably because at this point in time, most people using Linux as a desktop are using it because of CHOICE

  58. KDE is based on Qt by supun · · Score: 1

    "Score: 5, Interesting" on a untrue statement. Very sad moderation.

    Buying stock in a company does not make that company "part" of the purchaser. I can not find anywhere on the Trolltech page the statement "a division of the Canopy Group."

    The Canopy Group does not own a controlling share of Trolltech. They are not partners. They just own a small share of Trolltech stock. All companies own stock in other companies.

    --
    :w!
  59. Communist Economics by handy_vandal · · Score: 1

    Perens and his cohorts are applying the rules of communist economics to this projects requirements.

    In other words:

    1. Set wildly unrealistic goals.

    2. Compel large numbers of people to work toward said goals.

    3. Lie about the results: goals will never be met, but always pretend they have been exceeded.

    4. Arrest anyone who protests, and send them to the gulags.

    5. Arrest those who know the truth, and send them to the gulags.

    6. Arrest the original authors of the goals, and send them to the gulags.

    7. Arrest some other people at random, and send them to the gulags. (Repeat as necessary.)

    -kgj

    --
    -kgj
    1. Re:Communist Economics by swagr · · Score: 1

      You could say similar things about the States. That aside, do you even know what communism is?

      Or is this an attempt at humour?

      --

      -... --- .-. . -.. ..--..
    2. Re:Communist Economics by handy_vandal · · Score: 1

      You could say similar things about the States. That aside, do you even know what communism is?
      Or is this an attempt at humour?

      Partly an attempt at humor; partly a reflection of The Gulag Archipelago, which I recently read.

      I have no direct experience with communism, so I won't claim to know what it is, other than what I've read (which isn't much).

      In regard to saying similar things about the States: similar, in the sense of scathing condemnation -- democracy in the US is a hollow shell, real power resides with a murderous cabal of spooks and criminals. But not similar, in the sense that the US does not "disappear" millions of innocents into labor camps. (Not yet, anyway. After the next election, maybe ... if there is an election ....)

      -kgj

      --
      -kgj
  60. This may sound unfriendly by stealth.c · · Score: 1

    ...but I'm sick of the KDE/GNOME debate. Let's just pick one. There are things I like about GNOME. There are things I like about KDE. I prefer KDE, but GNOME is a fine choice. It DOES look more professional, GNOME 2.4 happens to run faster than KDE 3.1 on my hardware. If someone made it as customizable as KDE, I'd switch to it in a heartbeat.

    I kind of like the competition. It keeps both camps on their toes. But unified efforts might be a better idea. In doing that, Longhorn could end up looking paltry indeed.

    Besides, if choosing GNOME can make GNOME pushersshut up then what are we waiting for!

    1. Re:This may sound unfriendly by be-fan · · Score: 1

      GNOME is not a fine choice! It has the level of sophistication of NT4. Its as if all the features invented in the last several years (component technology, web-integrated desktop, file-location transparency) haven't happened. Its not a competitor for Windows 2000, much less Longhorn.

      --
      A deep unwavering belief is a sure sign you're missing something...
    2. Re:This may sound unfriendly by damiam · · Score: 1
      Component technology: Bonobo works fine, and is being used. Just because your file manager and web browser aren't the same program doesn't mean the technology's not there to do it.

      Web-integrated desktop: That sounds like a buzzword to me. I'm not sure exactly what you mean. If it's something like MS's Active Desktop, gdesklets provides much of the same functionality and looks much better at the same time.

      File-location transparency: Look up gnome-vfs sometime. Ximian's even patched OpenOffice to use it.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    3. Re:This may sound unfriendly by be-fan · · Score: 1

      The technologies exist, but adoption is poor. When I see a KDE app, I know it'll support KIO and KParts. Even standard apps like GEdit don't support the corresponding technologies in GNOME!

      --
      A deep unwavering belief is a sure sign you're missing something...
  61. Can't succeed without KDE? Windows did! by Fringe · · Score: 2, Insightful
    Some of these threads pointing out that choice is essential or that "some" people find KDE more usable completely miss the point and are why Linux can't make progress on the Desktop.


    Windows gives no choice. Windows rules the desktop. Windows ME/XP is (pick one: more | less) usable than the Windows 9X interface, but both succeeded.


    IMHO, if more distributions picked a single UI and went with it, patching in the most annoying gaps, the biggest problem with Linux would quickly be solved. The idea that multiple choices with fewer developers is somehow superior to fewer choices better done seems disingenous at best.


    I prefer KDE myself, but what I'd really like is for one to win and get most of the wrinkles ironed out. Either one. Because I don't have to worry about the UI choices in Windows, Mac, java apps, Palm apps or even PPC.

  62. Quite griping, KDE is not being shut out by meanfriend · · Score: 2, Informative
    A quote from the white paper

    Remember, whatever choices we make apply only to what we choose to support as a group. Our choices don't cause the alternatives to be removed from Debian, they don't constrain what a service provider can support to their own customers...

    IOW, if you want to use KDE, go ahead and use it, no one is stopping you. If they were making changes that made it impossible for KDE to run properly, then there may be a good basis for petition. Not having KDE included in distro XYZ in no way invalidates all the great work they've done to date. (I'm a happy KDE user)

    Also the white paper suggests supporting MySQL as the database, Python as interpretive language, and Mozilla as the browser. I dont see postgreSQL, PERL, and Thunderbird development teams getting thier panties in a wad.

  63. Nothing against KDE by steveha · · Score: 3, Insightful

    Don't forget that he isn't going to do anything that would pull KDE out of Debian. He isn't going to void the UserLinux certification of anyone who supports KDE. He is doing nothing against KDE.

    If you want to be a certified UserLinux support guy, you will need to understand GNOME so you can support it. You will not need to understand GNOME to get the certification, but you can understand it if you want to. You can advertise yourself as a certified UserLinux expert who will support KDE, if you want.

    So: UserLinux implies GNOME. UserLinux does not imply lack of KDE.

    I think Bruce Perens is 100% correct on this issue. There is no reason to demand companies and consultants to grok two complete desktop environments, and there are good reasons why a standard distro like UserLinux should just have one. And if there is going to just be one, the one that is more free is the correct one. No one ever has to pay anyone for the privilege of writing apps for GNOME, even proprietary commercial apps, so it's the correct one.

    steveha

    --
    lf(1): it's like ls(1) but sorts filenames by extension, tersely
    1. Re:Nothing against KDE by steveha · · Score: 1

      Argh! Error in the second paragraph. It should say "you will need to understand GNOME... You will not need to understand KDE to get the certification..."

      Sorry for the mistake.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
  64. Make up your damn minds slashbots! by Jeffery+McGrew · · Score: 3, Funny

    *every* time an artcle is posted about Linux/BSD vs. Windows/OS X usability, someone chimes in that 'if only the open source community could pick one developement platform, and limit user choice, then developers could focus on one platform, everything would work well, things would be easy, new users and business would love it, birds would sing, and MicroSoft would be overthrown'.

    Then that guy gets modded up to +5.

    Now, someone's making a serous effort to do *exactly that* and everyone's bitching about leaving out KDE and how it limits user choice, forces everyone to work on one platform, and how this will make things harder; when it appears that it has a large part to do with the licencing of QT vs. Gnome, and nothing about KDE or Gnome being 'better'.

    Sheesh. And I'm sitting here posting about it. I can't think of what's sadder!

    1. Re:Make up your damn minds slashbots! by Makarakalax · · Score: 1

      You've just proved that there isn't a single voice that can be called "slashdot". People have different opinions on these subjects. Sometimes you read an opinion at +5 that differs to another you just read.

      How surprising.

  65. Replay - Tilt by Anonymous Coward · · Score: 0

    Sounds like a replay of Redhat's game playing Gnome and ignoring KDE. It was the time when Mandrake came into the game. Partly because Redhat believed it could dictate the direction. Mandrake took over lots of users from RH. Redhat had to adjust.

    Again it might proof difficult giving out game plans to Linux users which ball they should have to use in their game. If they don't like the color of your ball, they'll simply look for another playground.

  66. KDE by Simple-Simmian · · Score: 1
    KDE is the default window manager for most successful distros. RedHat seems to be the only one that goes with Gnome in that group.

    Gnome zealots need to get over it. KDE zealots do too. I use what works for me. It appears it does as well for the majority of Linux users

    Trotting out the QT dead horse is a waste of effort. All the revelant libs are GPLed and have been for sometime. It's a non issue unless you are building commercial apps. Just like many developer tools you will have to pay if you use them in a commercial way. BFD. If you are writing commercial apps you should pay for your tools. It's a non issue.

    Use what you like. I wouldn't use UserLinux if forced to use Gnome. I have plenty of Debian based KDE distros to choose from beside that one.

    --
    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?
    1. Re:KDE by damiam · · Score: 1
      KDE is the default window manager

      KDE's not a window manager. It's a desktop. KWin is a window manager.

      I wouldn't use UserLinux if forced to use Gnome.

      You're not forced to use GNOME. You can apt-get install kde at any time. That said, if you know enough about the two desktops two make an informed choice between them, you're not in UserLinux's target user base.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    2. Re:KDE by RevSmiley · · Score: 0

      Thanks for the typical slashdot pendant reply that told no one nothing they didn't know already but stoked your own ego. You added so much to the discussion by doing so we all couldn't have done without it.

      --
      As you can see I don't care about my karma.
    3. Re:KDE by arose · · Score: 1

      Thanks for the typical slashdot pendant reply reply that told no one nothing they didn't know already but stoked your own ego. You added so much to the discussion by doing so we all couldn't have done without it.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
  67. This sucks! by be-fan · · Score: 5, Insightful

    This is one danger of commercial entities involving themselves in OSS development. The commercial companies are choosing GNOME not because of technical advantages, but because of monetary advantages (LGPL = no Qt license fees). If GNOME goes from being the second biggest DE (according to most polls), to becoming the standard Linux desktop because of something as stupid as that, that'd royally suck. Especially since, in most areas, GNOME's technology lags behind KDE's.

    I just hope this isn't yet another example of great technology dying because the commercial software industry has a tendency to preserve the status quo in lieu of pushing the envelope.

    --
    A deep unwavering belief is a sure sign you're missing something...
    1. Re:This sucks! by Anonymous Coward · · Score: 0

      I just want to point out a few quotes from the Perens article (available at Newsforge):

      According to it, it was Perens' decision:

      Bruce says:

      As you can see on our mailing list, most of the software consolidation in UserLinux is going on by consensus. I saw that no consensus would be possible regarding the GUI. So, I made a decision by fiat to get the project moving past the GUI issue.

      I agree you can argue about it a lot, but read on.

      Bruce says:

      In February, my book series will publish C++ GUI Programming with Qt, the official Trolltech guide to Qt 3.2, by Jasmin Blanchette and Mark Summerfield. I have a minor financial interest in promoting Qt (I don't make much money from my books), but no such interest in the case of GTK/GNOME at this time. Because of a miscommunication with my publisher, there is some non-free software on the CD attached to that book - Windows Qt and some compilers from Borland. Although that is against my policy for the books, and I told my publisher not to allow it to happen again, I chose to allow it to continue this time rather than create hardship for Trolltech at a late stage in their book production. I also recently recommended Qtopia to a consulting customer, for what could be a billion-dollar project. I point this out so that you might have some clue that I not an anti-Qt ogre.

      Again, it is important that we 'get in the door' (as he puts it) before something like DMCA, patent, and even totally unrelated matters such as piracy are used by the likes of Microsoft to destroy the free (as in freedom) and open source movements.

    2. Re:This sucks! by Anonymous Coward · · Score: 0

      This is one danger of commercial entities involving themselves in OSS development.

      Trying... hard... to read it... as something negative...

    3. Re:This sucks! by be-fan · · Score: 1

      Well yay for him. If UserLinux makes it big and gives GNOME a solid lock on the enterprise market, I'm sure that KDE users will appreciate the Qt book! If Linux is to be a software meritocracy, where the best software becomes the most popular software, such important decisions cannot be made by fiat! When I became a Linux users, years ago, I did envision Linux becoming mainstream. But in a way that fundementally changed the mainstream. This is just more of the same --- pushing stale technologies because preserving the status quo is convenient.

      --
      A deep unwavering belief is a sure sign you're missing something...
    4. Re:This sucks! by Anonymous Coward · · Score: 0

      >This is one danger of commercial entities involving
      >themselves in OSS development.

      You're right. Damn you, Trolltech!

    5. Re:This sucks! by omega9 · · Score: 1

      financial interest... consulting customer... billion-dollar project...

      Whatever my opinion of Mr. Perens was before, it is now solidly based on his consistant trend to view whether or not a decision is profitable, and to to-quickly judge something for its monitary value. He has displayed an attitude and series of actions that I cannot accept as best intentions for the community, but only for his personal agenda.

      --
      I'm against picketing, but I don't know how to show it.
    6. Re:This sucks! by msimm · · Score: 1

      I don't care who becomes the standard so much as I care that some DE becomes standard. I think it more important that this happens then who it happens with. The advantages of having a standard in an open environments should be pretty obvious to most of us. Right now its like every DE is its own proprietary environment. Applications have to be written specifically for your favorite DE. Why is that? I use an open source operating system and I have to have multiple libraries installed with applications functioning completely differently based on which one they use. I'm getting pretty tired of it. The days of the patchwork Linux are limited, but don't worry too much, Linux is an open environment still and those who don't like the default will always be able to customize EVERYTHING (maybe KDE and Gnome can finally work interchangably and you can chose based on your own personal preference? GASP!).

      --
      Quack, quack.
    7. Re:This sucks! by be-fan · · Score: 1

      What's going on with GNOME appears to be a process of picking the standard. And true to fashion, the commercial software industry has decided to pick the lesser technology *again*, because its more convenient.

      The basic problem is that Linux doesn't have to be any better than Windows to be sucessful in the commercial market, because of cost factors, so a "good-enough" solution is just fine.

      --
      A deep unwavering belief is a sure sign you're missing something...
    8. Re:This sucks! by Decameron81 · · Score: 2, Insightful

      The point is KDE has a problem, the problem of making it harder to develop closed source applications for it. I can't see why this shouldn't be important to developers.

      Developers are the root of all software, freedom is all they ask.

      Diego Rey

      --
      diegoT
    9. Re:This sucks! by be-fan · · Score: 1

      They can make closed-source applications, they just have to pay for it. If they're making for-pay software, they should be willing to pay for their tools.

      That's all besides the point. Perens isn't even giving developers the freedom to choose between GTK+ and Qt for their apps. Perens is just deciding for them.

      --
      A deep unwavering belief is a sure sign you're missing something...
    10. Re:This sucks! by 0x0d0a · · Score: 1

      Especially since, in most areas, GNOME's technology lags behind KDE's.

      I've written a number of comparisons of the two in Slashdot threads, and have generally found the two to be roughly equal from a "new and interesting ideas" standpoint. Can you name a few examples of why exactly you feel that KDE has a significant advantage?

    11. Re:This sucks! by sheldon · · Score: 1

      This is one danger of commercial entities involving themselves in OSS development. The commercial companies are choosing GNOME not because of technical advantages, but because of monetary advantages (LGPL = no Qt license fees).

      This wins the "Most Bizarre Statement of 2003" award.

    12. Re:This sucks! by Anonymous Coward · · Score: 0

      Umm, hello?

      He picked Gnome, but has financial interest in Qt and KDE... how does this further his 'personal agenda'?

      Since this disto is to be for businesses, perhaps basing a decision on monetary issues is not too nutty, is it?

    13. Re:This sucks! by Decameron81 · · Score: 1
      If they're making for-pay software, they should be willing to pay for their tools.


      No. Why? Is this a new rule of some sort? I develop closed source commercial software and I would never choose a platform that makes me pay $1000 to develop for it. No matter how many people states that it is my duty to be willing to pay $1000. That's just nonsense.

      Diego Rey

      PS: I read the initial proposal of using only GNOME and not KDE at all, and this discussion we're having is NOT besides the point. The only reason why Perens wants GNOME and not KDE is because GNOME allows people to develop for free. Not a single other reason was given for his decision. I fully agree with it.
      --
      diegoT
    14. Re:This sucks! by inc_x · · Score: 1

      > I just hope this isn't yet another example of
      > great technology dying because the commercial
      > software industry has a tendency to preserve
      > the status quo in lieu of pushing the
      > envelope.

      Ask Bruce which companies have promised him money for this decision and you will know.

    15. Re:This sucks! by IamTheRealMike · · Score: 1
      Especially since, in most areas, GNOME's technology lags behind KDE's.

      That's basically irrelevant - almost all the apps that I use on a day to day basis and actually matter to me are neither KDE nor GNOME, they are things like emacs, bash, irssi, gaim, firebird and so on.

      The only non-desktop neutral app I use and would think twice about replacing is Evolution.

      KDE has this problem where they spend all their time making shining pearls of API perfection, and then wonder why there are so few third party apps using them. The fact is that dragging in the KDE or GNOME frameworks does carry a cost for the users and typically the benefits of the additional functionality offered doesn't outweigh the cost.

      The GNOME guys have the right idea imho - work on making a great desktop first, and let that drive the infrastructure, rather than the other way around. In time most of the real functionality should be pushed down into either the toolkit (GTK/Qt) or highly modular desktop neutral 3rd party libraries.

    16. Re:This sucks! by Anonymous Coward · · Score: 0

      Please excuse me while I parody you:

      One: If Linux goes from being the second most common kernel, to becoming the standard desktop kernel because of something as stupid as licensing, that'd royally suck. Especially since, in most areas, Linux's support for desktop hardware lags behind Windows'.

      Two: KDE is the most popular free desktop. I hope GNOME doesn't overtake it because commercial developers like it. The commercial software industry has a tendency to preserve the status quo in lieu of pushing the envelope.

    17. Re:This sucks! by be-fan · · Score: 1

      Its a big strech to believe that a $1000 (actually, its more like $2000, but that's irrelevent) per-developer fee is going to affect commercial development on the platform. $2000 is peanuts to commercial developers. Even smaller companies happily shell out about that much for a copy of Visual Studio, and thrice that for a Rational Rose license. Given the choice, I don't think a lot of developers are going to forsake Qt and commercial support to save $2000.

      If developers really don't want to pay the Qt license fee, they won't, and GTK+ will naturally become the most popular choice. But that natural selection isn't being allowed to happen --- Perens is choosing GTK+ because that's what his backers are leaning towards.

      --
      A deep unwavering belief is a sure sign you're missing something...
  68. Something to consider by MazTaim · · Score: 1

    One of the most painful things in life to do is to "grow up." We have seen many different projects over the years face off against one another for "market" dominance. Fact of the matter, there is going to come a time (such as this) where decisions will be made as to what software packages to provide to users.

    Although one of the benefits of OSS is choice, it can also be a hinderance. People who are not used to any GNU/Linux (whatever you want to call them) distributions, really don't want to spend time trying to make choices as to what software they are going to use. They are interested in how easy and stable applications are to use.

    Arguements over which software applications are moot. As we have seen in the past, it doesn't really matter which one is more techically sound. It's what appeals to the consumer that counts when you try to create a standard anything (look at VHS vs. Beta-Max).

    I am glad so see somebody finally set up and make a stand when it comes to "too many" choices. I would love to see a distribution that doesn't require 1300+ packages to be installed.

  69. Should have made everybody mad and gone with XFCE4 by jensend · · Score: 1

    Though consistency of interface is important in creating a distribution which is targeted at end-users, this does not have to come with the baggage which is associated with the current two leading DEs. A desktop should be simple, light, and operate well with anything which follows a set of standards; the standards, rather than the fact that all the applications are part of the same monolithic heavyweight project, should be the source of consistency. Most commercial companies would, I think, prefer a desktop which is development environment-agnostic over one which makes the choice for them, be the chosen environment lgpl'd or no.

  70. the answer is simple... by nighty5 · · Score: 1

    I prefer QT over any other GUI toolkit available.
    But if QT is not going to be included in this distribution, its just another distribution I won't consider to install or offer to my clients.

    1. Re:the answer is simple... by cyb97 · · Score: 1

      Look at it from a different angle, if you don't support GTK+ you're just another consultant that won't be offered to work for ACME Inc which recently deployed a non-Qt distro and needs several million dollars worth of work porting their proprietary applications to their newfound toolkit...

      While many regard Qt as the best solution, the pointy-haired-bosses rarely pick the best solution.

    2. Re:the answer is simple... by nighty5 · · Score: 1
      While many regard Qt as the best solution, the pointy-haired-bosses rarely pick the best solution.

      and thus, is my job as a consultant to ensure that my clients best interests are met. My target market isnt GTK, there is enough work to go around.

      I use QT because its clearly the best multi-platform development tool available.

  71. Re:Perens is a Gnome Zealot(tm) by aristotle-dude · · Score: 1
    Unlike KDE, Gnome is free Translation : GPL is freerer than LGPL. LGPL allows corporations like Novell and Sun to have propeitry forks and lock away their changes from the user. Now that Novell has taken over Ximian you can expect Gnome to get put under corpirate lock. With KDE you have the choice, you either PAY UP or pay with your source code.
    I guess you don't want commercial apps like Photoshop then for linux? As for the rest of your comments I don't want to feed any trolls. :) BTW. My mac has a three button mouse. It's a logitec USB optical scroll mouse.
    --
    Jesus was a compassionate social conservative who called individuals to sin no more.
  72. who cares by Anonymous Coward · · Score: 1, Insightful

    Did everyone forget that just because it ships without kde doesn't mean you can't download kde and install it. We are talking about linux here folks.

  73. Re:Releasing a distro without KDE... by Anonymous Coward · · Score: 0

    Whats funny about that? i dont get it.

  74. I prefer KDE, but I agree with Bruce by mfearby · · Score: 2, Interesting

    I personally prefer KDE over gnome, but if Linux is ever going to make it into the corporate world in decent-sized rollouts, some hard decisions are going to have to be made. The Gnome interface looks less sophisticated than KDE, but I know for darn sure that I don't want to ask my users "are you using KDE or Gnome" and have them replying "I dunno", then having to figure out the difference. Yes, I *realise* that IT departments would set the standard and possibly would uninstall one or the other, but does anybody care about Windows not having a plethora of other desktop-systems?

    As much as I bag the shit out of Microsoft for their products, their Windows interface is consistent and you know what you're dealing with. Linux will eventually be all the better for it if KDE and Gnome can just ditch one in favour of the other and focus their collective development efforts on one, kick-arse, desktop environment. I used to use WindowMaker before we had desktop environments, but I don't lose sleep at night because I switched to KDE.

    You people might think that Gnome vs KDE are holy wars that must be fought, but it is this division that Microsoft are tickled-pink to witness. Ever heard of the saying "Divide, and conquer" (or should that be "Divide, and konquer"?

    Get with the program you religious zealots and do something that benefits Linux for a change! At the end of the day, I couldn't care less which desktop environment wins out, just as long as one of those frigging things is a clear winner.

    This is one of the main reasons why I still keep booting into Windows XP for a lot of things - because things are consistent and they interoperate seamlessly without me having to run memory-hogging applications like klipper just so the many different clipboard protocols appear to work "seamlessly"

  75. It's because of a naming problem, really.... by Malor · · Score: 5, Interesting
    (this is an almost verbatim copy of a post I made at Linux Weekly News, so if you've seen this before, my apologies.)

    Bruce says: "UserLinux is intended to be a system for business people."

    OK, that's great, but why on earth call it UserLinux then? Shouldn't it be BusinessLinux?

    Names are important. UserLinux sounds like a Linux distro intended for end users. Someone like my Mom, not someone like HP. Bruce may be right about GNOME being a better solution for business. I will, however, bet nickels to dollars that much of the controversy is because people assume that a distro called UserLinux should be about, well, users, and that's KDE's main focus.

    I have assumed ever since the initial announcement that UserLinux might end up being my distro of choice, and I was upset when I heard about KDE's exclusion. Now that I read further, I see I have no reason to be upset, because UserLinux isn't intended for me.

    It wouldn't surprise me to see the whole project fail because of this fundamental naming problem. Is a distro called UserLinux even going to register on a CIO's radar?

    BusinessLinux might have. I don't think UserLinux will.

    1. Re:It's because of a naming problem, really.... by TheDarkener · · Score: 1

      Hate to burst your bubble, but end users include business users. It's the people who don't administrate the computers, it makes no distinction of whether they're actually using the computer in a business or at home.

      --
      It is pitch black. You are likely to be eaten by a grue.
    2. Re:It's because of a naming problem, really.... by Malor · · Score: 1
      Sure, business users are users.... but not all users are in business.

      UserLinux implies the set of ALL users, when Bruce really wanted the subset of BUSINESS users.

      It is just a terribly bad name, and I believe it will rob the project of much of its potential success.

      Think about it a minute.... if it WERE called BusinessLinux, and Bruce said "GNOME only".... how upset would you be? I'd be a little bummed, because I like KDE, but I'd respect the decision. From a business perspective, it makes good sense. But excluding KDE from a distro called UserLinux seems impossibly stupid.

      Until this brouhaha started, I didn't fully understand that UserLinux is meant for business. I was paying peripheral attention to UL because I thought I might someday move to it when the kinks were worked out. I do Linux every day. I've been doing Linux for a long time. Yet, even near the center of my knowledge base, I was confused about the project's focus. What are management types going to think?

      Thousands and thousands of times, consultants are going to have to explain, "No, no, UserLinux is meant for business."

      Names matter. This project has the wrong one.

    3. Re:It's because of a naming problem, really.... by disntrstd · · Score: 1

      Well, judging by the name UserLinux, it seems to be a proper name. I mean, after all, it was made for the people that use it.

    4. Re:It's because of a naming problem, really.... by Enucite · · Score: 1

      The name isn't finalized. There's currently several discussions on the mailing list about what the name should be.

      Right now "Enterprise Debian" and "Business Linux" seem to be the most popular choices. Although some still want to stick with the UserLinux name.

    5. Re:It's because of a naming problem, really.... by Malor · · Score: 1

      Either name would be better. I like Enterprise Debian myself, it has a really nice sound.

      With a name like that, it could be extremely successful, IMO. Even with icky GNOME. *grin*

      I'll bet you that if it were ALREADY called Enterprise Debian, it would never have made the front page of Slashdot.

    6. Re:It's because of a naming problem, really.... by Enucite · · Score: 1

      That's actually the one I'm in favor of as well. :)

      There was a logo mock-up posted on the list with an 'e' at the center of the debian swirl. Very good idea for a logo IMO.

      The only problems with the name are:
      1) Need approval from the Debian group to use their trademark
      2) "Debian" has less name recognition than "Linux"

      Maybe something better will come up, but right now I like the name "Enterprise Debian" in spite of those potential problems.

    7. Re:It's because of a naming problem, really.... by benb · · Score: 1

      Agreed.

      And even "BusinessLinux" is silly. Sounds like "Windows" or "Word". As if it were the only Linux for Business. Even worse, if it was called e.g. "Heridion", you'd even have to read a whole line of text to know that it's a linux for businesses!

    8. Re:It's because of a naming problem, really.... by benb · · Score: 1

      Luckily, Bruce Perens says himself that he doesn't like the name and asks for better ideas. Maybe that would be a good and useful slashdot discussion.

  76. Gnome vs KDE by Archangel+Michael · · Score: 1

    Begun, the flame wars have.

    Okay, now that I have that troll (pun intended) out of the way.

    I personally like KDE over Gnome. That being said, I am all for picking just ONE, desktop to be the ONE. I see arguements for BOTH. However, I think the inclusion of one over the other should NOT be made primarily on Religious/political grounds, but on Technical ones.

    Things like USABILITY, SPEED, APPLICATIONS, and DEVELOPEMENT, should be the deciding factor. Of course much of that is very subjective, but a consensus can be reached.

    Further, Userlinux can actually benifit marketing wise, if they just PICKED ONE as the ONE. No confusion on software boxes. "Requires Userlinux 4.0".

    If people really want the option of the OTHER the softwarebox could say, "Requires Userlinux 4.0 with KDE".

    --
    Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
  77. Time to change the name-GUI Boss. by Anonymous Coward · · Score: 0

    "A distro without KDE is not going to get very far."

    KDE, the "Red Hat"(1) of the OSS world.

    (1) Remember when Red Hat was feared to be the next Microsoft?

  78. for programmer purposes, eh? by LordMyren · · Score: 1

    then why not go purely fltk, eh?

    i honestly cannot imagine a distro without gnome libraries. i'm sure they'll be there, just not in linkable form.

  79. Under linux, Qt has the same license as Gnome. by woods · · Score: 2, Informative


    Non-GPL'd Qt development requires payments to Trolltech. Qt has the same license as Gnome under Linux.

    Trolltech has licensed Qt under the GPL for Linux, which is the same license as Gnome. They will also sell you another license if you don't like the GPL and want to write apps that link to Qt using some other more restrictive license.

    As far as I know, Gnome is only licensed under the GPL. Unless I'm mistaken, that means to me that with Gnome, you have one choice of license, whereas with Qt, you can opt to purchase a non-GPL license.

  80. Why ... ? by CedgeS · · Score: 1

    ... does the slashdot linux pinguin icon have a bag over its head (it's face is blacked out)?

  81. One gui for one operating system by Enrique1218 · · Score: 1

    Certainly, with the express purpose to develop a user friendly desktop linux, one should settle on one user interface. As I read some of these replies, I feel some in the slashdot crowd overlook the fact the basic user may not have the desire or the spare time to tinker with different desktops to understand their various idiosyncrasies. A pretty destop may not be necessary but a consistent one is. A person who uses a computer as part of their profession would require a consistent layout. Commercial operating systems don't waste time with supporting different gui, so why should open spource developers, with less resources and who are working voluntarily on this project, be required to accomodate? Just because it is out there isn't a valid reason with respect to this goal.

    Now, which gui is a different matter all together. KDE or Gnome seem to have equal support and function (at least from my perspective). One could just a as well flip a coin rather than do a comprehensive comparison of their various features.

    --
    You don't have to be smart to use a Mac, you just have to be smart enough to buy one
    1. Re:One gui for one operating system by __past__ · · Score: 1
      Commercial operating systems don't waste time with supporting different gui
      Download Solaris some time, it's free, and definitly commercial. The current version comes with two desktop environments (CDE and Gnome) installed by default, and several optional ones.

      For Mac OS X, while having a consistent default desktop, Apple "wastes time" with supporting completely unrelated graphics subsystems, their own and X11. They also have their own version of Java's Swing, as a second API for their look and feel.

      It's just MS Windows that is that monocultural. It might still be a valid choice for UserLinux to only support one desktop, but it is not the only possible one.

    2. Re:One gui for one operating system by be-fan · · Score: 1

      Don't forget that Apple also has two different-looking L&Fs (Metal and Aqua) as well as legacy support for MacOS Classic. Also, Windows has at least three unavoidable toolkits (Explorer, MS Office, .NET).

      --
      A deep unwavering belief is a sure sign you're missing something...
    3. Re:One gui for one operating system by Enrique1218 · · Score: 1

      A clear example of slashdotters obscuring a point with useless factoids just to look smart. Solaris is commercial OS with two supported desktop environments. GIVE THE MAN A CIGAR. Has that fact help Sun maintain profits? Has it given them a large user base? But I'll give to you, I hereby amend my statement to replace COMMERCIAL with SUCCESSFUL AND MAINSTREAM. PS: You can keep it I got better ways waste time like read Slashdot. As far as Apple is concern, there is only ONE desktop environment (AQUA). X11, though it is self-sufficient, is not quite the same as KDE or Gnome. They provide extra functionality over the x11 layer. I guess that is maybe why some people even bother developing them. Apple mainly provides it, like Classic, as an appendage to expand the list of available software with the purpose of selling computers to a larger market. Apple is not giving it users the same kind of choice as *nix users have when choosing KDE or Gnome. For instance, it doesn't seem to be intend for you you to use x11 or Classic in place of Aqua Please save fingers! If it is not useful don't type it.

      --
      You don't have to be smart to use a Mac, you just have to be smart enough to buy one
  82. XFCE by charnov · · Score: 1

    Personally, I am not happy with either environment (although Ximian Desktop 2 gets really close). I use XFCE. It's clean, lean, and works great.

    --
    [RIAA] says its concern is artists. That's true, in just the sense that a cattle rancher is concerned about its cattle.
    1. Re:XFCE by Anonymous Coward · · Score: 0

      I *seriously* have to agree with you. I've used XFce on my FreeBSD boxes for the longest time, and since the 4.0 RC's, its just been absolutely phenominal.
      Never crashed, never took more than 15mb memory with everything loaded, ran fast as lightning. Highly configurable. About all it really needs is a better file manager and an optional desktop component.
      Considering they had to work around X-Windows, and with no toolkit to base off of, they did a hell of a job.

    2. Re:XFCE by dskoll · · Score: 1

      XFCE 3 is great, and I use it. With XFCE 4, they got rid of the icons when you close windows in favour of the wretched taskbar. :-(

      Unless/until they re-introduce the option of iconifying windows the old way, I stick with XFCE 3.

  83. I wish KDE and Gnome would merge by gilesjuk · · Score: 1

    Subject says it all, it would result in thousands of conistant apps and make Linux more paletable.

    Of course it might be better for one of the desktops to just die. Merging two architectures isn't easy.

    If they did merge I'm sure someone would fork a project off from the merged desktop.

  84. But how good is GTK's Windows support? by truth_revealed · · Score: 1

    Qt works equally well for applications developed on UNIX and Windows. Is the same true for GTK? Businesses demand cross platform support for their applications. GTK was not up to par with UNIX a year ago when I tried it out on Windows. Has it improved?

    1. Re:But how good is GTK's Windows support? by Julian352 · · Score: 1

      It has greatly improved over the past year with the improvements in GTK 2.2. The biggest poster child for GTK on windows is I think Gaim. Few of my friends have switched to Gaim on windows even though they've never used Linux on their own.

      I would say that it is a fairly stable choice if users are switching from AIM to Gaim and not complaining on stability. (And these aren't OSS advocates but non-programmers)

    2. Re:But how good is GTK's Windows support? by Hatta · · Score: 1

      You might want to point out to them that there's a gaim-encryption plugin that's completely transparent to the user. You get the warm fuzzies of privacy, and sexy red lock icons taboot.

      --
      Give me Classic Slashdot or give me death!
    3. Re:But how good is GTK's Windows support? by Julian352 · · Score: 1

      The problem with any type of a plugin that does encryption is that it requires both sides to have the same plugin/software. That is very unlikely with the current dominance of "vanilla" AIM on the desktop.

      If you want something that's more likely to be widely used, then AOL's implementation of encryption is more likely to work. Quite a few windows users I know have downloaded some type of a certificate, and since any certificate can be used, even a privately signed one will work.

    4. Re:But how good is GTK's Windows support? by Trepalium · · Score: 1

      GTK for Windows looks just as out of place as it did years ago. Qt/Windows gives you applications that use the native widget set, GTK/Windows does not. A 'theme' for GTK+ does exist called GTK-Wimp, but it's more of a look-alike than a native set of widgets.

      --
      I used up all my sick days, so I'm calling in dead.
    5. Re:But how good is GTK's Windows support? by Hatta · · Score: 1

      I was talking about your friends who already have gaim. I recommend gaim and gaim-encryption to everyone I meet who uses aim(if it comes up in conversation). If they like it and stick with it, I get to speak with them securely. If they don't, I haven't lost anything.

      As for AOL's encryption. Have they provided source? If they don't give us source how do we know it's actually a secure algorithm. Also, without source, how can developers of open source clients write their own implementation?

      --
      Give me Classic Slashdot or give me death!
    6. Re:But how good is GTK's Windows support? by Julian352 · · Score: 1

      Have you read ALL of gaim's source?

      From what I heard, it was done by using Netscape's IP on encryption for their browser. (Says somewhere on the website about using the certificates) Thus you can trust it about as much as you can trust IE or Netscape to encrypt your credit cards. Some security is better than none, and since they are selling this to big companies, it is important for them to make it atleast secure enough for that. (ie. as secure as IE which is accepted level of security)

    7. Re:But how good is GTK's Windows support? by peschmae · · Score: 1
      Qt/Windows gives you applications that use the native widget set,
      Sorry. This is not true. Qt always draws its widgets itself without using any native widgets. Qt uses styles (just as Gtk does, too) to emulate the Windows LnF. These styles are well made thus noone really notices them... Peschma
    8. Re:But how good is GTK's Windows support? by Trepalium · · Score: 1

      I stand corrected. You are quite right. Damn advertising, implying one thing, meaning something else. Qt/Windows applications always seemed to draw faster than GTK+ Windows apps did, so I made a bad assumption.

      --
      I used up all my sick days, so I'm calling in dead.
    9. Re:But how good is GTK's Windows support? by Hatta · · Score: 1

      I trust that on a project as big as gaim, if there were backdoors installed so that the government could evesdrop on my conversations, someone would pick up on it. If AOL puts a back door in their encryption, we'll never know. Choosing between software given away by community minded people who are willing to have their source scrutinized, and software released by a profit driven megacorporation is a no brainer.

      --
      Give me Classic Slashdot or give me death!
  85. This is nice. by miffo.swe · · Score: 1

    The more distributions started the better. I wish the best of luck to Bruce and i think he will pull this off.

    I really love the cleaness of gnome and i do hope it wont get pregnant.

    --
    HTTP/1.1 400
  86. this is the other way by LordMyren · · Score: 1

    anyone insists their way is the only way, and they are probably wrong. but if everyone insists there was is the only way, is that way right?

    this is the other way. every other distro in the world has gnome and kde both. just as kde has advantages over gnome and gnome has advantages over kde, providing only one has advantages and disadvantages over providing both or neither.

    it makes a helluva lot of sense for a buisness class distro, which is what UserLinux seems to want to be. a distro built around LGPL would really make a lot of sense for the buisness world: no suprises for your managers. put it on the front page: the power of linux plus no worries about viral gpl when you start writing gui software. the point is moot in the face of the fact that UserLinux has no such grand goals (i'm sure that'd go over better than saying no kde... lol). But it makes some sense, again, especially when you are talking about buisness.

    Myren

  87. They should use KDE by Brian+Knotts · · Score: 1
    ...and dump GNOME.

    KDE is a simpler, more familiar interface for average Joe end users to figure out.

    And, Qt has a better license: GPL.

    1. Re:They should use KDE by Anonymous Coward · · Score: 0

      GPL is not better than LGPL.

    2. Re:They should use KDE by Cid+Highwind · · Score: 1

      If you think KDE's interface is simpler than Gnome, you must still be using version 1.x of both desktops. Gnome is now stripped of many options, and KDE has more control panels, tabs, buttons, sliders, and checkboxes than any sane person could ever want.

      --
      0 1 - just my two bits
  88. Never mind, Gnome is GPL, but GTK+ is LGPL. by woods · · Score: 2

    Never mind, gnome is GPL'd, but GTK+ (the toolkit, which is the proper parallel to draw to Qt) is LGPL, which is much less restrictive than the GPL.

    I see Bruce's point. With GTK+, you can write GUI applicaitons, and not release your source code. The same activity with Qt requires a commercial license.

    My mistake.

    1. Re:Never mind, Gnome is GPL, but GTK+ is LGPL. by Carewolf · · Score: 1

      So??

      You still can't make use the GNOME libraries and make GNOME applications.

      KDE libraries are licensed by LGPL.

    2. Re:Never mind, Gnome is GPL, but GTK+ is LGPL. by juhaz · · Score: 1

      GNOME libraries are LGPL, even if most of apps are GPL. So yes, you can make use of GNOME libraries and GTK+ to make full closed-source and/or commercial GNOME applications.

  89. Stop complaining. by starnix · · Score: 1

    I am getting so tired of hearing KDE supporters bitching and moaning when ever a distro decideds to use Gnome as the default DE. I may be wrong but does anyone hear Gnome supporters bitching when KDE is chosen as the default? (Lycoris, Xandros, Lindows, Mandrake) Most of these distros are based on Debian so you can always install KDE if you wish to. As pointed out in numerous other posts, anyone who want's KDE installed will know where to get it and know how to install it. If they don't, then they probably don't need it. All I'm saying is that I think Gnome is a good choice in as far as it being simple to use and clean looking. KDE is always cluttered and hard to use. Lest we forget that we are targeting ease of use here. KDE in its default state is targeted at people who want choice and configurability. Being a network admin I can say that giving users that type of choice would only confuse them.

  90. GUI in C was a bad idea then, a bad idea now by Starrider · · Score: 5, Insightful

    As a programmer, C is great because it is quick and low level. Operating systems are written in C. Network stacks are written in C.

    For a GUI, C is horrific. GUI just lends itself to Object Oriented programming. I know the hard core *NIX geeks will flame me for this, but why on earth would you NOT want to do a GUI in OOP. The beauty of coding for windows using MFC and .NET is you just extend classes already there. It's an elegant and tidy way to do things.

    Languages like C with functions just turn code into a nightmare. Ever wonder why most game companies program in directX and NOT openGL? OpenGL is C, directX is not.

    The commercial issue with QT is really a non-issue. It might even be possible companies and write inhouse software without paying a license fee (since the code is never redistributed.) If companies want to make money writing with QT they will. What do *companies* want, to pay a fee to QT and own their own code, or give it away with the GPL and Gnome?

    When someone starts talking about something being "FREER" as in the gpl, I turn on my Stallman filter. These people claim the BSD license isn't free because the code can be 'hijacked' by closed source projects.

    If you give something away, you give it away for good. The BSD license gives it away for EVERYONE to use, and doesn't discriminate.

    When decisions are NOT based on technical merit, rather on politics, then you are no longer a geek. You are an activist.

    Would you use a distro developed with activism placed over technical merit? This is why Linus carries so much weight. He doesn't get into politics.

    1. Re:GUI in C was a bad idea then, a bad idea now by BitchKapoor · · Score: 1
      I agree with your assertion that GUIs are inherently object-oriented, as they attempt to reconcile programmatic constructs with tangible objects. However, MFC is a bad example of an easy-to-program GUI library. Furthermore, I don't think extending classes is particularly useful for GUI programming -- by deriving, you're either essentially encapsulating the parent class's functionality along with other functionality, or doing weird stuff to the internals of the parent to extend it.

      What's really important is that GUIs are concurrent and event-based, and hence the primitives which are reused all over the place need to be as well. Contrast a push-button, which generates an event for the containing program to handle whenever the user decides to click on it, with a square-root function, which only when instructed by the containing program takes a value, performs a finite amount of computation, returns another value, and stops. This is why Qt has its signals and slots. This is why TCL/Tk has been used so much for GUI programming despite its terribly lacking language features. This is why Java uses threads in its GUI frameworks. This is why the failed BeOS focused on highly efficient multi-threading.

      Although I 100% agree that object-oriented encapsulation is essential for organizing the code of widgets, asynchronous lightweight concurrency is at least as important to make GUIs work. Derived objects, on the other hand, don't seem too useful for GUIs so long as you have interfaces or a good implementation of generic functions and type inference.

      Regarding OpenGL vs. DirectX, in my experience OpenGL is very easy and intuitive to program, and is structured very naturally. You have to remember that drawing to the screen is essentially procedural. Even in toolkits like DirectX designed in so-called object-oriented languages, your drawing code looks essentially the same. The only real difference is that when you create objects like buffers or textures, they're "real objects" in your language rather than quasi-opaque handle numbers. I do think that is a good incremental improvement, but I also think OpenGL object handles can be easily wrapped into objects in, say, C++, without sacrificing performance. The real arguments for DirectX, in my opinion, are (1) it's more than just graphics -- DirectSound, DirectInput, etc., and (2) it's heavily supported by Microsoft -- this means that game developers can be more confident that their product will work well on their customers' systems, and hence not be returned or gain a reputation for unreliability. Indeed, as Microsoft has demonstrated with the XBox, DirectX is an attempt to make PCs more uniform, predictable, and console-like, appealing to developers without as high up-front costs of development kits and lingering threat of not "making the cut" when the console proprietor decides whether or not to license your game.

    2. Re:GUI in C was a bad idea then, a bad idea now by Anonymous Coward · · Score: 0

      For a GUI, C is horrific. GUI just lends itself to Object Oriented programming. I know the hard core *NIX geeks will flame me for this, but why on earth would you NOT want to do a GUI in OOP. The beauty of coding for windows using MFC and .NET is you just extend classes already there. It's an elegant and tidy way to do things.
      GUIs do lean themselves towards OOP, but MFC was, is, and almost certainly always will be, a giant, bloated, piece of crap. It has been the hardest thing I've ever had to code with. I've found it much, much easier to write my own wrappers around the widgets themselves, as they are after all, only windows within windows. This is much faster, conforms more to the basic windows user interface, and easier to manage, as a whole.

      Languages like C with functions just turn code into a nightmare. Ever wonder why most game companies program in directX and NOT openGL? OpenGL is C, directX is not.
      I'm sure it has nothing to do with Microsoft being a monopoly, unlike SGI. And certainly nothing to do with virtually 100% of cards implementing at least 95% of the directx extensions, and less than 20% implementing even close to that amount of opengl extensions, let alone fully accelerated.

      When someone starts talking about something being "FREER" as in the gpl, I turn on my Stallman filter. These people claim the BSD license isn't free because the code can be 'hijacked' by closed source projects.

      If you give something away, you give it away for good. The BSD license gives it away for EVERYONE to use, and doesn't discriminate.

      When decisions are NOT based on technical merit, rather on politics, then you are no longer a geek. You are an activist.

      Would you use a distro developed with activism placed over technical merit? This is why Linus carries so much weight. He doesn't get into politics.


      The BSD license is `more free' than the GPL. I don't get where you're coming off with this activism thing. I really have a hard time with, giving out code without expecting anything in return being more activist, than giving away code, but ONLY if you pay the authors, or give out your entire source code to the public. By your definition, you make it sound like BSD is FORCING everyone to take their code, and do whatever the hell they want with it! That'll show those capitalist, monopolistic bastards who's boss!

      Oh, and by the way. Not everyone takes being called a geek as a compliment. Cheers :)

    3. Re:GUI in C was a bad idea then, a bad idea now by BitchKapoor · · Score: 1
      Support for DirectX vs. OpenGL extensions... that's another good point.

      I think the original poster was arguing that the GPL is more political than the BSD license. But that's irrelevant here, because GTK+ is LGPLed, while Qt is GPLed/other license available. Since most application developers won't be modifying either toolkit's libraries, GTK+ is actually more lenient (at least for cheapskates).

    4. Re:GUI in C was a bad idea then, a bad idea now by Anonymous Coward · · Score: 0

      When decisions are NOT based on technical merit, rather on politics, then you are no longer a geek. You are an activist.

      Exactly right. Thank goodness those nearsighted folks who's preoccupation with minutia clouds their ability to see the big picture don't manage the show.

    5. Re:GUI in C was a bad idea then, a bad idea now by 0x0d0a · · Score: 1

      For a GUI, C is horrific.

      For GUI design? Yes, I agree. I'd prefer a layout description language, perhaps in XML. This is what Glade, the GTK/GNOME GUI RAD tool, generates.

      GUI just lends itself to Object Oriented programming.

      GTK+ and GNOME are both object oriented, even in their C forms (even ignoring the C++ gnomemm and gtkmm bindings).

      I know the hard core *NIX geeks will flame me for this, but why on earth would you NOT want to do a GUI in OOP.

      You don't. GTK+, GNOME, KDE, Qt and MFC are all object-oriented. I would assume that whatever Apple's using these days is as well.

      The beauty of coding for windows using MFC and .NET is you just extend classes already there. It's an elegant and tidy way to do things.

      With all due respect...have you actually coded in GTK+? It's an awful lot cleaner than MFC, at least. Not sure about .NET -- I haven't poked at it.

      Languages like C with functions just turn code into a nightmare. Ever wonder why most game companies program in directX and NOT openGL? OpenGL is C, directX is not.

      [Laughs] Not even close.

      DirectX and OpenGL are wildly different. Direct3D is a vague approximation of OpenGL, but DirectX is a full game/multimedia programming API. Game companies use DirectX because they get a well-supported API that does everything they want instead of going to the extra work of learning multiple APIs.

      The commercial issue with QT is really a non-issue.

      You may find it so. I know at least one major company that has had issues with the licencing of Qt.

      It might even be possible companies and write inhouse software without paying a license fee (since the code is never redistributed.)

      Wrong. TrollTech just dropped their Windows Qt GPL license, so you're fucked with respect to cross-platform capabilities.

      If companies want to make money writing with QT they will.

      Yup. And if they want to do so using GTK+, they will as well. So far, there are a lot more people writing software with GTK+ than with Qt.

      What do *companies* want, to pay a fee to QT and own their own code, or give it away with the GPL and Gnome?

      That makes no sense. It is, in fact, backwards. Qt is dual GPL/commercial licensed. The only way to freely release Qt software is to GPL it. GTK+ and GNOME are both LGPLed, which means that they place no restrictions on the licenses of software that simply link to them.

      When someone starts talking about something being "FREER" as in the gpl, I turn on my Stallman filter. These people claim the BSD license isn't free because the code can be 'hijacked' by closed source projects.

      You'd be turning your back on Qt, which is GPLed.

      If you give something away, you give it away for good. The BSD license gives it away for EVERYONE to use, and doesn't discriminate.

      Yup. With Qt, you may not freely write BSD-licensed Qt-using software. You may do so with GTK+. You are supporting the other side most eloquently.

      When decisions are NOT based on technical merit, rather on politics, then you are no longer a geek. You are an activist.

      Fine. Qt is less modular, duplicates functionality, has more overhead, runs into more ABI-related problems, and has license issues that produce technical issues.

      The main bad thing about KDE is Qt. If KDE used a free widget set, it would have taken over the world -- most people didn't have any real issue with KDE itself. Instead, the KDE folks chose to fight it out over Qt, and now KDE is increasingly falling behind.

    6. Re:GUI in C was a bad idea then, a bad idea now by SEE · · Score: 2, Informative

      You seem to miss the point.

      Qt is available under GPL or under a proprietary licesne. This means a closed-source software developer must either give away his source or pay Troll Tech a license fee.

      GTK+ is LGPL. Thus, a closed-source software developer can use it for free and without releasing his source.

      GTK+/Gnome is therefore being picked because it is less ideologically pure than Qt/KDE, not more so.

    7. Re:GUI in C was a bad idea then, a bad idea now by Jimithing+DMB · · Score: 2, Insightful

      As a programmer, C is great because it is quick and low level. Operating systems are written in C. Network stacks are written in C.

      Actually, several GUI libraries are written in C as well. In fact, I'd be willing to bet that more GUI libraries are written in C than in any other language. Win32 is written in C. Apple's Carbon and classic APIs are written in C. Numerous X toolkits are written in C. The first NeXT API was written in C. Of course, it's worth noting that Win32 stems from Win16 which was originally written in Pascal. Ditto for the classic MacOS. NeXT was later written in Objective-C and became Apple's Cocoa. Carbon is a mix of APIs modeled after both classic MacOS and more recently Cocoa.

      Mac OS X is rather interesing because the entire CoreFoundation as well as the newer Carbon stuff like HIView is quite obviously modeled after Cocoa APIs except as a C API instead of an Objective-C API. The interesting thing is that even though C lacks any OO features the newer Carbon APIs are quite clearly object oriented. In fact, many CF classes are "toll-free bridged" to their Foundation (Objective-C) counterparts which means you can do neat stuff like use a CFStringRef as an NSString* because the in-memory layout of CFString and NSString is identical.

      For a GUI, C is horrific. GUI just lends itself to Object Oriented programming. I know the hard core *NIX geeks will flame me for this, but why on earth would you NOT want to do a GUI in OOP. The beauty of coding for windows using MFC and .NET is you just extend classes already there. It's an elegant and tidy way to do things.

      Ugh, where to begin. I'll agree that from an application developer's perspective a C interface to the GUI is horrific. That's why MS has MFC and .NET (as you mentioned) and why GTK has things like GTKMM (C++) and GTK# (C#) bindings. And I agree with you that you would want to do a GUI in OOP. Unfortunately, you neglect to realize that GTK is object oriented in many respects and for that matter so is Win32 to a lesser extent.

      Even in Win32 and GTK one can do the same sort of subclassing as one would do with a C++ toolkit like MFC. The big difference is that in a toolkit like Win32 or GTK you are dealing with the toolkit's method of doing OO whereas with MFC you have a more well-known C++ syntax for OO. However, you still have to deal with the object hierarchy and design of the toolkit. MFC, Qt, wxWindows, and other C++ toolkits all have their own ideas about OO and their own APIs even if they are all written in the same language. While I've heard people call wxWindows or Qt programing elegant and tidy, I've never heard that said about MFC. That's a new one.

      The commercial issue with QT is really a non-issue. It might even be possible companies and write inhouse software without paying a license fee (since the code is never redistributed.) If companies want to make money writing with QT they will. What do *companies* want, to pay a fee to QT and own their own code, or give it away with the GPL and Gnome?

      I think you're confused here. Qt (pronounced "Cute" not to be confused with QT which is the abbreviation for QuickTime) is dual licensed under either the GPL or the Trolltech commercial license. Qt costs a lot of money to use commercially. IIRC, Trolltech wants like $1k a seat or something ridiculous like that. Your other option with Qt is to use the GPL. So, what do *companies want*: to pay a fee to Trolltech and own their own code or to avoid the fee and "give it away" with the GPL and the GPL-licensed Qt.

      GTK on the other hand is licensed under the LGPL license which specifically allows linkage with non-free software. The only LGPL requirement is that you provide a way for the user to modify the free portions (the library). In practice that means you simply dynamically link with GTK which you must do anyway because of the design of GTK t

    8. Re:GUI in C was a bad idea then, a bad idea now by dvdeug · · Score: 1

      What do *companies* want, to pay a fee to QT and own their own code, or give it away with the GPL and Gnome?

      Most of the Gnome libraries are LGPL. In any case, QT is similar to GTK, and KDE is similar to Gnome.

      Ever wonder why most game companies program in directX and NOT openGL? OpenGL is C, directX is not.

      And all the OpenGL programmers immediately jumped to DirectX when it was first released. Oh wait, when it was first released they thought it was junk. It took many releases for it to mature. Perhaps there's something more then just C versus not C, perhaps there's actual differences between the two.

      These people claim the BSD license isn't free

      Bullshit. I've never heard that from anyone who wasn't completely troll. It's not a position that Stallman agrees with.

      If you give something away, you give it away for good.

      Perhaps you should work on the whole sharing thing. See, I can give you something, and when you're done with it, you can give it back.

      When decisions are NOT based on technical merit, rather on politics, then you are no longer a geek.

      Geeks can't be political? In any case, human affairs are political, not techical, and a license is a document to other humans, not computers. Everyone makes political decisions every day, and people who don't tend to have serious troubles living in the real world.

    9. Re:GUI in C was a bad idea then, a bad idea now by jesco · · Score: 1
      I think you're confused here. Qt (pronounced "Cute" not to be confused with QT which is the abbreviation for QuickTime) is dual licensed under either the GPL or the Trolltech commercial license. Qt costs a lot of money to use commercially. IIRC, Trolltech wants like $1k a seat or something ridiculous like that. Your other option with Qt is to use the GPL. So, what do *companies want*: to pay a fee to Trolltech and own their own code or to avoid the fee and "give it away" with the GPL and the GPL-licensed Qt.

      The original poster wrote about in-house. The GPL doesn't force you to make your application available to everyone in the world. It just says that if you do so, you also have to include the source. You can do contract-work using GPL'ed libraries, the only string is that you have to hand over the source-code to your client as well (something which every reasonable client should demand anyways).

      I think you're confusing some things.
    10. Re:GUI in C was a bad idea then, a bad idea now by Jimithing+DMB · · Score: 1

      The OP wrote:

      The commercial issue with QT is really a non-issue. It might even be possible companies and write inhouse software without paying a license fee (since the code is never redistributed.) If companies want to make money writing with QT they will. What do *companies* want, to pay a fee to QT and own their own code, or give it away with the GPL and Gnome?

      I wrote:

      I think you're confused here. Qt (pronounced "Cute" not to be confused with QT which is the abbreviation for QuickTime) is dual licensed under either the GPL or the Trolltech commercial license. Qt costs a lot of money to use commercially. IIRC, Trolltech wants like $1k a seat or something ridiculous like that. Your other option with Qt is to use the GPL. So, what do *companies want*: to pay a fee to Trolltech and own their own code or to avoid the fee and "give it away" with the GPL and the GPL-licensed Qt.

      You wrote:

      The original poster wrote about in-house. The GPL doesn't force you to make your application available to everyone in the world. It just says that if you do so, you also have to include the source. You can do contract-work using GPL'ed libraries, the only string is that you have to hand over the source-code to your client as well (something which every reasonable client should demand anyways).

      So, as you can see, while the OP opened the paragraph talking about in-house software he closed it by talking about software for sale. I was responding to the latter part.

      However, the fact still remains that the client who purchased the in-house software is clearly free to redistribute the source code to others which while unlikely may or may not be acceptable for those writing in-house software. For example, let's say I write an accounting package and charge the client a lot of money for it (since it was a lot of work). Let's say part of the contract is that the client has a copy of the source code (I agree, this is reasonable). If I don't use any GPL software I am free to tell the client that they may not redistribute the source. If I do use GPL software as part of my product I now have to distribute it to my client under the GPL. The client may now legally redistribute the software to a third party and neither of them will have to pay me a dime more. One way to get around this is to put a clause in the support contract stating that if the code is redistributed then the support contract will be terminated and money will not be refunded. This would not conflict with the GPL legally (as far as I can tell) though it certainly conflicts with the spirit of it.

      There is also this other sticky issue of clause 3b which essentially means that if the developer doesn't do 3a (distribute source alongside the object code) then he must (emphasis added) "Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code[...]"

      Ouch! That means that if I don't give my client source alongside the binary then I must give them a written offer that states they or anyone else in the world can request it directly from me.

      The GPL makes a lot of sense for applications and I can see where it makes sense for libraries that you want to limit to free software use. However, for a GUI toolkit (of which there are plenty of alternatives) it really makes zero sense to release under the GPL and force commercial developers to choose a different toolkit or in the case of Qt pay for a commercial license. If you want it to be widely adopted, then using GPL licensed libraries is simply not an option. Stallman tells you this much in the text of the LGPL (it's the reason it exists).

      Personally, I use and develop wxWindows wh

  91. Re:But how good is GTK+'s Windows support? by truth_revealed · · Score: 1

    Me english not so good. Please let me correct my previous post....

    Qt works equally well for applications developed on UNIX and Windows. Is the same true for GTK+? Businesses demand cross platform support for their applications. GTK+ on Windows was not up to par with GTK+ on UNIX a year ago when I tried it. Has it improved?

  92. How about neither? by plinius · · Score: 1
    KDE has its origins in paywareland and is therefore tainted. I do recall it had a tendency to exhibit a Windows-like temptation to bomb completely when just one KDE program bomb.

    Gnome is C-based and last I checked, not the friendliest system to write code for. Have things changed? It is up to par yet? I doubt it.

    My question is, what would be wrong with just going with Motif, since it is now free and it has been tested for years. It is reliable and easy to program for. Why reinvent the wheel?

    1. Re:How about neither? by Anonymous Coward · · Score: 0

      because Motif sucks ass, and looks like it too

  93. They better call it "Loser-Linux" by Anonymous Coward · · Score: 0

    It will be dead in the water without KDE.

  94. Re:wtf? by Anonymous Coward · · Score: 0

    And in other breaking news, water = wet. Where are my informative modpoints?!?!

  95. Re:Releasing a distro without KDE... by Anonymous Coward · · Score: 0

    Probably because you're French.

  96. KDE has licencing ADVANTAGE by no_choice · · Score: 2, Insightful

    Some people have said that Gnome has an advantage over KDE because you need to buy a licence to make commercial software with QT.

    First of all, this is wrong. Read the QT FAQ. Developers can write commercial apps to their hearts content using QT with complete freedom (beer & speech) as long as your apps are GPL'd. Now, if a developer wants to write PROPRIETARY, NON-FREE apps -- programs where the developer keeps the source code secret and does not allow the users to review, change, or share the program or source with others -- well, the developer can do that, but then they need to buy a QT commercial licence from Trolltech.

    And what is wrong with that? If a developer refuses to share his source freely with others, why should Trolltech have to share their source with him??!

    This kind of licenceing encourages the development of free (as in speech) software (including commercial free software--COMMERCIAL NON-FREE). Isn't advancing free software supposed to be the whole point of userlinux?

    1. Re:KDE has licencing ADVANTAGE by Capt.+Beyond · · Score: 1

      I wholeheartedly agree with you.

      The LGPL is not about free software, it is about proprietary, closed source software.

      Linux is all about free, open source software.

      I dont see where Bruce and his proprietary ideals fits in.

      --
      -- "Perceptions create reality. By changing your perceptions you change your reality."
    2. Re:KDE has licencing ADVANTAGE by Anonymous Coward · · Score: 0

      Some people have said that Gnome has an advantage over KDE because you need to buy a licence to make commercial software with QT.

      They say this because it's true...

      Developers can write commercial apps to their hearts content using QT with complete freedom (beer & speech) as long as your apps are GPL'd.

      Also true, but I thought we were talking commercial sopftware, not GPL software...

      Now, if a developer wants to write PROPRIETARY, NON-FREE apps ...apps commonly referred to as "commercial" software.

      well, the developer can do that, but then they need to buy a QT commercial licence from Trolltech.

      So your post starts out saying that the proposition "To write commercial software with QT, you must buy a license" is false. Then you show that it is in fact true. Then, you go on to defend the reasoning for TrollTech's commercial licensing scheme. Nice job. Was there supposed to be a point in that post somewhere?

    3. Re:KDE has licencing ADVANTAGE by Anonymous Coward · · Score: 0

      Was there supposed to be a point in that post somewhere?

      Good question. I hope it gets an answer.

    4. Re:KDE has licencing ADVANTAGE by Christ-on-a-bike · · Score: 1
      Here it is:

      commercial = "Having profit as a chief aim: a commercial book, not a scholarly tome." (dictionary.com)

      proprietary = "Exclusively owned; private: a proprietary hospital. ... Owned by a private individual or corporation under a trademark or patent: a proprietary drug." (dictionary.com)

      Spot the difference. If you're having trouble, try to realise that the Linux kernel is commercial and not proprietary. It is for sale. It is GPL'd. See? HAND.

  97. There are plenty of KDE only distros out there by Anonymous Coward · · Score: 0

    Funny that people don't complain like this about those distros.

    1. Re:There are plenty of KDE only distros out there by Anonymous Coward · · Score: 0

      Perhaps that's because GNOME is the equivolent of a 1976 Volvo Station Wagon, while KDE is more like a McLaren F1.

  98. a comprehensible answer... by Goonie · · Score: 2, Informative

    It's the most complex text editor ever written, used mainly by programmers to edit code and a million or so other things besides. Some programmers love it, others hate it, preferring the much more lightweight (but with its own UI issues) vi text editor, or alternatives like nedit. The jargon file's entry on EMACS gives some explanation, see also vi, and holy wars. If the above links are still too opaque, and you need more details on EMACS itself rather than the culture wars, see the Wikipedia entry on Emacs.

    --

    Any sufficiently advanced technology is indistinguishable from a rigged demo
    --Andy Finkel (J. Klass?)
  99. FUD alert! Mod DOWN!!! by mangu · · Score: 1
    If you want to do commercial development with Qt, you have to pay a one time fee.


    According to these guys, Qt is distributed under the GPL.

  100. The irony of their paths ... by Random+BedHead+Ed · · Score: 1
    Isn't it kind of ironic that GNOME was once a hacker's desktop environment, filled with a million applications whose names all started with G, whereas KDE was a scorned desktop built upon a proprietary toolkit? Because things are going full circle: despite the enormous popularity of KDE amongst Linux enthusiasts, GNOME seems set to become a defacto standard among the suits.

    Doubt it? Red Hat has always favored GNOME, and the new UserLinux project seems ready to make the same decision. Sun's Java Desktop is GNOME-based. And SuSE, while always partial to KDE, is now owned by Novell, which also owns a big development community at Ximian. It looks like the corporate world is poised to start embracing GNOME, leaving KDE for hobyists like me (and maybe you).

    I quite like both desktops, and hope the choice remains for *nix users. Particularly with the Patent Wars looming ahead of us, a diversity of open source and free software projects is a useful thing. Think of what would happen if a patent infringement lawsuit was filed against Gecko developers, preventing its availability. There goes Mozilla, Epiphany, Firebird and others. What are we left with? KHTML. I hope the need to standardize doesn't kill off the great variety we have now.

  101. Jingoism. by chris_sawtell · · Score: 2, Informative
    It's jingoism pure and simple.
    Sorry to have to say it, but from the UserLinux people's point of view KDE isn't made here, so it's not their first choice. Neither cost nor freedom matter one fig to business. To think that they do is pure self deception.
    KDE folks: Get over it, if you can't join them, beat them; and kome up with a really KooLinux.

    It's more than possible by taking an appropriate subset of the Gentoo distribution and adding basic accounting functions ready to go. Now write an ebuild file and install with:-
    emerge KooLinux
    Now that would be a piece of cake. Granted it'll be time consuming to make, but it's far from rocket science, yet very VERY Kool.

  102. One or the other .. not both. by naelurec · · Score: 1

    While I agree that a decision must be made between KDE or Gnome for many reasons (less variations in deployed systems, consistency across the application base, ability to draw in more commercial support, etc..) I question the rational for simply discarding KDE due to commercial licensing cost.

    Big advantages that I hear over and over again for QT is the consistent API, fast development time, ease of cross platform development, etc. Things that in and of themselves are very important when developing any type of software.

    While I am not in a position to determine the relative strengths and weaknesses of each toolkit, I believe that this analysis NEEDS to be done before simply zeroing in on cost for commercial software development and discarding what is the #1 or #2 *nix desktop environment. It might cost some money for developers if they release commercial software, but if they are able to develop it faster, be able to port it to multiple platforms, and have cleaner code (due to a consistent, easy to use API) .. doesn't that justify the relatively small costs?

  103. What about development effort? by mangu · · Score: 1

    If the only thing one had to worry about were ordinary end users, then maybe you would have a point. But what about developers? I have created applications in both Gnome and KDE and I must say that KDE is much easier to program in, because of Qt. I don't want to flamebait, so I invite you to try: get any development system you prefer and try to create two versions of any application, using both Qt and Gtk.

  104. transcending exclusive desktop choices by Doc+Ruby · · Score: 1

    This KDE/GNOME choice is one being made every day, by people who want Linux on their desktop. The choice itself, with its ambiguous consequences, is a roadblock to many, perhaps most: some apps are cross-desktop, some aren't, many are n% coexistant, YMMV. Windows achieved market dominance with several incompatible OS versions (bound to their respective desktops) lumped together in a single "Windows market share", despite a fragmented platform. At one time, (and therefore today, as all these platforms are still running around the world) a developer or user had to choose between Win3.1, WinForWorkgroups, Win95, WinNT, WinForPenComputing, ModularWindows, and several other marginal platforms, including DOS. But market analysts gave Microsoft an illusory single market share, even though the actual markets were incompatible. Linux, with GNOME/KDE/etc, can't flimflam the analysts like Microsoft, especially when the separate desktops look different, unlike the confusingly similar Windows versions. The dependency trees of Linux software, which fork at the desktop layer, divide the potential market, and stop many people. Linunx developers must allow software to operate regardless of which desktop the user has installed, even if some "advanced" features that depend on a specific desktop are unavailable. And these desktop packages must be built with a tiered architecture, so they can peacefully coexist in multiple installations, without losing operational features when the graphic rendering is unavailable due to their displacement by the alternate desktop. Desktops of the world, unite your toolchains: you have nothing to lose but your smug good looks!

    --

    --
    make install -not war

  105. Ack! stop modding parent up! by woods · · Score: 1

    Oh man, quit modding the parent "insightful +1" -- it's "wrong -5" (see my other reply).

    Oh, maybe they're trying to punish me...

    Or sarcastic...

  106. No reason for flames by Qetu · · Score: 1

    I have read the original Bruce Perens reasoning on the subject and i must say i mostly agree on the reasons he puts forth.

    Meanwhile, if any KDE advocates try to recreate the UserLinux project with --Gnome and ++KDE, they could let the market decide ...

    Or maybe that's a bad idea.

  107. Here's hoping the GNOME team ... by Trogre · · Score: 1

    ...gets keyboard navigation working sometime soon.
    If KDE is being 'phased out' in a major distribution, that is.

    As a sysadmin, I have to look after legacy windows machines as well as linux boxes.

    While overall the linux boxes are much easier to administer in large volumes than their Win2000/XP counterparts, the ones running GNOME lose out big time.

    In windows I can navigate the whole machine entirely by keyboard. For example, I can shut down a group of logged-in machines by walking up to each one, hitting CRTL-ESC, UP, ENTER, 'S', ENTER. (there may be another 'S' in there, depending on where "Stand by" sits). This takes about two seconds per machine. I don't even have to look at the screen.

    On the GNOME machines, I can try as many hotkey combinations as I can think of, and the bottom-left menu icon just sits there smiling at me. Eventually I give up in disgust and sit down to use the mouse.

    This is one area where KDE is streets ahead of GNOME, although even it has a long way to go.

    Of course, we'll have to get to work on porting the really cool KDE applications that (AFAIK) have no GNOME equivalent, such as Kstars and Kalzium. Maybe we could even give them sensible names? No, I don't mean Gstars and Galzium :)

    --
    "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    1. Re:Here's hoping the GNOME team ... by damiam · · Score: 1

      GNOME's menu icon can be invoked with Ctrl-F1. The GNOME desktop is theoretically entirely keyboard-navigable. Details can be found here.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    2. Re:Here's hoping the GNOME team ... by Dr.+Photo · · Score: 1
      Wait... You administrate a bunch of systems... by hand?

      Off the top of my head, ssh keys plus a shell script (and a list of computers) would suffice to type one measly command, which in turn would remotely login and shut down each computer.
      #!/bin/sh

      while read x ; do
      # must have ssh keys set up. See ssh manpage.
      ssh root@"$x" shutdown -h now
      done <<EOF
      192.168.123.97
      frodo.localdomain
      samwise. localdomain
      gaffer.localdomain
      merry
      pippin
      ga ndalf
      etcetera
      EOF
      Or, to quote Back to the Future, Part II:
      "You mean you have to use your hands? That's like a baby's toy!"
    3. Re:Here's hoping the GNOME team ... by FreeUser · · Score: 1

      ..gets keyboard navigation working sometime soon.
      If KDE is being 'phased out' in a major distribution, that is.


      I wouldn't call UserLinux a "major distribution." Bruce Perens may be able to trade on his name recognition to make it one, but then again, maybe not.

      Frankly, as an enterprise sysadmin, it is a part of MY job to select the desktop for my users, not my distribution's job. My users are quite comfortable, indeed happy, with KDE ... had it been gnome, there is a good chance they would have rebelled and insisted we do all of our development under Windows instead. Not now, now that they get the "free as in freedom, freedom as in the freedom to conduct our business without being held hostage by our vendors", but during that critical transition phase when we were still winning their minds and hearts. You list a number of great reasons for preferring KDE over Gnome, and I could certainly add to that list (my nits with KDE, like hardcoding user defaults in the software wizard rather than allowing the sysadmin to configure sensible defaults ... e.g. focus-follows-mouse rather than that gawdauful kick-to-focus crap, notwithstanding), but there are undoubtably reasons some might have for preferring Gnome over KDE.

      I think chosing one major desktop, rather than providing the sysadmin with a choice of the two top desktops, is a mistake. As others have observed, they have effectively halved their potential contributing developers, not to mention their potential users. It is unnecessarilly polarizing and penny-wise, pound-foolish to do this (and I say this as someone who has preferred Gnome over KDE in the past, who has preferred Enlightenment over both, and who now prefers xfce4).

      I frankly won't be surprised if UserLinux is relegated to the ranks of fringe distributions living in the shadow of Gentoo, Debian proper, or some other derivation of one or the other.

      --
      The Future of Human Evolution: Autonomy
    4. Re:Here's hoping the GNOME team ... by Trogre · · Score: 1

      I think you might have missed the point.

      I realise that most routine stuff can be done (and is in fact done) remotely by scripts.

      What I am talking about is in a computer lab situation where someone comes up to you and wants something done NOW. Checking print jobs on a single workstation, for example.

      Perhaps my shutdown workstation scenario was a bad example.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    5. Re:Here's hoping the GNOME team ... by Dr.+Photo · · Score: 1

      Fair enough, though the print jobs example isn't a good one either. With CUPS (and probably lpd), you can check print jobs remotely, and definitely without a GUI. (man lpstat) :-)

      Also, what made your shutdown scenario so compelling on the surface was that you had to do it to a bunch of machines sequentially, and right when you wanted to go home. Checking one thing on one computer a bit faster seems to be a wishlist item. That said, you should definitely send an email to the GNOME people, to request a simpler (or more customizable) set of keyboard shortcuts in the future. (Wishlist bugs are still bugs, after all!)

      Anyway, hope you don't have to shutdown those Linux boxes manually anymore. :)

  108. FUD, FUD, FUD!!! by mangu · · Score: 1

    Qt is GPL.

    1. Re:FUD, FUD, FUD!!! by damiam · · Score: 1
      Qt is GPL.

      That's the problem. GTK is LGPL. That's Perens' solution.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    2. Re:FUD, FUD, FUD!!! by Capt.+Beyond · · Score: 1

      LGPL is only good if you like using nonfree proprietary software.

      --
      -- "Perceptions create reality. By changing your perceptions you change your reality."
    3. Re:FUD, FUD, FUD!!! by GrenDel+Fuego · · Score: 1

      LGPL is only good if you like using nonfree proprietary software.



      Or you're planning on WRITING non-free proprietary software. This distribution is for businesses after all. If they're a software company putting out non-free desktop software, then linking against an LGPL'ed library would be preferred.
    4. Re:FUD, FUD, FUD!!! by damiam · · Score: 2

      LGPL is good if you like giving other people the freedom to use proprietary software if it better suits their needs. No one forces you to use proprietary software just because a library is LGPL'd.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    5. Re:FUD, FUD, FUD!!! by fault0 · · Score: 1

      > LGPL is good if you like giving other people the freedom to use proprietary software if it better suits their needs. No one forces you to use proprietary software just because a library is LGPL'd.

      Using that argument, Qt would indeed be a better solution, since a commercial license of Qt gives you pretty much ALL freedoms. :-)

    6. Re:FUD, FUD, FUD!!! by damiam · · Score: 1

      A commercial license of QT gives you no more freedom than the LGPL does. Yet, it costs money. I'm not seeing why it's a better solution.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    7. Re:FUD, FUD, FUD!!! by fault0 · · Score: 1

      > A commercial license of QT gives you no more freedom than the LGPL does.

      Nope.. with a commercial Qt license, you can link to modified copies of Qt without having to rerelease the source of said modified copy, which you would be required to release with the LGPL.

    8. Re:FUD, FUD, FUD!!! by be-fan · · Score: 1

      Your $2000 also buys you professional commercial support and a more well-documented and feature-filled toolkit.

      --
      A deep unwavering belief is a sure sign you're missing something...
    9. Re:FUD, FUD, FUD!!! by damiam · · Score: 1

      Possibly true, but that's irrelevent to the Freedoms we're discussing.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    10. Re:FUD, FUD, FUD!!! by damiam · · Score: 1

      Are you sure about that? I can't find Trolltech's proprietary license terms on their site, but your scenario implies that they allow you to resell a binary-only QT for profit under your own license (thus meaning that anyone who bought QT could then sell it to anyone else, undercutting Trolltech). That's not exactly standard for a commercial library license.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    11. Re:FUD, FUD, FUD!!! by 10Ghz · · Score: 1
      Or you're planning on WRITING non-free proprietary software. This distribution is for businesses after all.


      And how many businesses write software? This may come as a shock to you, but most companies do NOT write software as their business! Yes, most companies USE software, but very few WRITE software. And you can write closed in-house software for free with Qt. GPL allows that.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    12. Re:FUD, FUD, FUD!!! by Roberto · · Score: 1

      Yes, you are allowed, as long as what you are distributing is not a wrapper or a GUI programming library.

      At least that's what I've heard.

  109. Bruce? (was Re:KDE is not to be ignored) by BigRedFish · · Score: 1

    Ignoring KDE in favor of GNOME would be like only including VI and not Emacs (or Emacs and not VI), and forcing all users to use one. This is a mistake if they don't include both.

    I concur. And something in Bruce's response got me.
    From Bruce Perens's response:

    the Red Hat "Bluecurve" project has created a theme that makes the two GUIs look identical. Applications from KDE and GNOME run reasonably well together today. Users don't care what GUI toolkit their application was built with. But all of the efforts to unify these two desktops do not change the fact that there are two entirely different desktop software development kits. [....] Maintaining expertise in both of two GUI development kits is an expensive proposition.

    I see what Bruce is getting at, but if the apps run fine under both KDE and GNOME, and look the same thanks to BlueCurve, and the users don't care whether the apps are built in Qt or GTK, then why not just pick one (GTK, fine), default to GNOME on the standard install, but keep access to the KDE packages there, even unsupported, so the user can run KDE if so inclined?

    Of course, the UserLinux team is free to include (or not) whatever it wishes. It just seems a curious decision, and unless I'm misunderstanding him, Bruce has debunked his own justification.

    1. Re:Bruce? (was Re:KDE is not to be ignored) by Charlotte · · Score: 1

      ... then why not just pick one (GTK, fine), default to GNOME on the standard install, but keep access to the KDE packages there, even unsupported, so the user can run KDE if so inclined?

      Even unsupported packages cost time and money to maintain for the distributor. It looks like UserLinux just made a conscious decision based on a cost analysis and input from the marketing guys. That decision is subject to change though.

      For instance, envision the KDE guys writing a totally compatible GTK interface and supplanting gnome. It is possible, just takes effort. Also don't forget the embedded market where QT is making inroads (and the embedded market could end up making the PC business look like a flee market).

      Point is this all isn't important, what is important is that there be choice. You don't have to use UserLinux - right? Try gentoo or debian.

    2. Re:Bruce? (was Re:KDE is not to be ignored) by AstroDrabb · · Score: 1
      The problem is that the two do not inter-operate well. I use Gnome, though I fire up a KDE app now and then. Guess what. I cannot copy-n-paste between the KDE app to my GNome app. KDE apps try to use arts for sound while Gnome apps usually use esd. KDE apps use a differnt tool for RPC then GNOME. Do you see where I am going? I can see tons of corporate users complaining that then cannot cut-n-paste between two apps. While the two apps may look the same, one is a KDE app and the other is Gnome. I can see a home user trying to run a KDE app and Gnome app that both play some sound. The Gnome app is using esd and the KDE is trying to play sound through arts. Let your imagination run wild with all the possible problems caused by users running applications for KDE and Gnome at the same time. It would be a corporate admins nightmare. Pick ONE Linux desktop. I don't care wich, just one. I am bias for Gnome so I say Gnome. Others say KDE. Agian, in the end I don't care which one. Just pick and may it a great desktop. Make it have ONE API (though with many language bindings like GTK), so the commercial software industry can make tons of software for Linux. Simple software that flurishes under MS Windows like a gretting card program, or GAMES, or etc, etc. I write software for a fortune 500 comapny and I know that I would not want to have to deal with a KDE user not being able to drag-n-drop or cut-n-past with my Gnome based app, or visa versa.

      For more commercial desktop software to get to Linux, Linux needs ONE desktop and ONE GUI toolkit. I don't see large commercial support for Linux any other way.

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    3. Re:Bruce? (was Re:KDE is not to be ignored) by juhaz · · Score: 1

      Well, that's almost exactly what they ARE doing.

      User so incluned can apt-get install "unsupported" kde and fire away with it.

      This is Debian, it's not like being excluded from installation media means you must go trough pains of installing it from source or something.

    4. Re:Bruce? (was Re:KDE is not to be ignored) by BigRedFish · · Score: 1

      User so inclined can apt-get install "unsupported" kde and fire away with it.

      Thanks - from the way the article and response were worded, it had given me the impression that the user couldn't install via the underlying Debian package system. If I misunderstood, then I'm happy to have been wrong!

  110. IMHO this is good by Janek+Kozicki · · Score: 1

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

    by this 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
    #
  111. I don't understand by bankman · · Score: 1
    Ignoring KDE in favor of GNOME would be like only including VI and not Emacs

    I always thought that Emacs was a desktop environment....

    --
    I feel so sig.
  112. User Linux Means Usable by users! by drfindley · · Score: 0

    UserLinux is intended for the business USER. It's ineded for those who don't understand how to turn the computer on. Although it may be targetted at businesses, I'd recommend UserLinux to my grandmother, because finally she'd have an free (as in freedom) OS that she can USE. That's the intent to make it more USABLE than linux currently is. Linux was created by a nerd for nerds. It's called userlinux because it's intended for the non-nerd AKA as a User.

    I think the term works out, it's got the right intentions. It's not intended to be built for businesses, but for users, particularily business users. There is a difference.

    1. Re:User Linux Means Usable by users! by Malor · · Score: 1
      Well, it appears you and Bruce differ. This is what he says:

      "UserLinux is intended to be a system for business people. Central to its design is a network of competing for-profit service providers, who perform engineering and support services for the system."

      "Business people", not "end users in business". You have a pretty theory, but it doesn't match what the architect is actually saying.

      Given his stated goals for the project, the name is completely wrong. How the heck is a marketer going to work with this? (and we're all marketers when we're trying to sell someone on a project.) It is a fundamentally confused message, and it's going to hurt this project. Badly.

      Any given brand can own only one or two words in someone's head. Linux mostly owns "quality" and "free". (which is a very, very rare combination!) Adding User to Linux, but then changing the definition of User to mean Business means that the marketing/branding effort is largely wasted. They can't spend much time on "quality" and "free" because "user" is exactly wrong.

      The closest analogy I can come up with is Nabisco deciding to launch a new line of premium cookies, something like the Pepperidge Farm line, and calling them "Saltine Cookies".

      Likely ensuing debacle left as an exercise for the reader.

  113. KDE/Qt is more free by Brian+Knotts · · Score: 2, Informative
    Yes. And the one that is more free is KDE/Qt, because it is under the GPL, which is more free than LGPL.

    Don't believe me? Ask Richard Stallman.

    1. Re:KDE/Qt is more free by Cid+Highwind · · Score: 1

      "because it is under the GPL, which is more free than LGPL"

      Exactly true! It's like cars. If I give you a car, that's free. If I give you a car, but prohibit you from driving it to work, or from using it in your job, or driving it on toll roads, that's *more* free!

      --
      0 1 - just my two bits
  114. Stop the FUD, please! by mangu · · Score: 1
    If you want to do commercial development with Qt, you have to pay a one time fee.


    If you want to do commercial development with Gtk, you cannot, it's GPL. Same as the "free" version of Qt. The fact is that Qt offers the developers two options: they either buy a licence to do "commercial" development OR distribute their work under the GPL.

    1. Re:Stop the FUD, please! by jcupitt65 · · Score: 1

      No, GTK+ is LGPL. You can do closed-source development with GTK on any platform without getting a licence. Check the page.

    2. Re:Stop the FUD, please! by Anonymous Coward · · Score: 0

      This is a lie! GTK is GPL. So YOU stop the FUD please.

    3. Re:Stop the FUD, please! by Chris_Mir · · Score: 1

      *sigh* You would think they would lie on their own site about their license?

    4. Re:Stop the FUD, please! by juhaz · · Score: 1

      Yes, stop the FUD please. GTK is LGPL. Clear enough?

  115. KDE, please die by xahlee · · Score: 1

    KDE, please die. actually, i don't wish you terminated, but stay in a niche existance. Don't fuck with the universality progress and development of gnu/linux.

    --
    Xah
    xahlee.org
    http://xahlee.org/PageTwo_dir/more.html
    1. Re:KDE, please die by be-fan · · Score: 1

      Heh, not surprising you're a GNOME user.

      Funny you should use GNU/linux. Since the whole "using LGPL to gain commercial popularity" is completely against what RMS and GNU espouse.

      --
      A deep unwavering belief is a sure sign you're missing something...
    2. Re:KDE, please die by bjarvis354 · · Score: 1

      I must be missing something...Not to defend the troll, but I don't see anything about GNOME being LGPL on the GNU site:

      http://www.gnu.org/directory/gui/gnome.html

      that site states:

      Licensed under The GNU General Public License, Version 2 or later. This is a GNU package.

      No KDE to be found...

    3. Re:KDE, please die by be-fan · · Score: 1

      The KDE and GNOME libs are both LGPL or BSD. KDE and GNOME applications are mostly GPL. GTK+ is LGPL, while Qt is GPL. That means that you can make closed-source GTK+ apps, but to make closed source Qt apps, you have to get a special commercial license from Trolltech.

      --
      A deep unwavering belief is a sure sign you're missing something...
  116. Missing the point (flamebait but true) by waferhead · · Score: 1

    If the intended user is buisiness, then concentrate on the UI that WORKS, with the
    best code, and most complete feature set.

    (I am a USER, old Amiga freak, linux user since `94. IANAP)

    Gnome crashed/burned/died on me within 5 minutes every time I tried it for years, and by the point Gnome didn't as often, KDE just worked so well and was so comlete that switching to Gnome was like ... Going back to Win 3.1.1 as far as feature set.

    Some of the apps for gnome rock. But the UI does NOT.

    Give me KDE or give me XFCE/WM (both is best)

  117. They Better Call It GratisLinux by Anonymous Coward · · Score: 0
    Anybody noticed that Bruce P. is boasting negotiating with an anonymous consortium of Big Business corporations who want to finance his BruceLinux to the tune of 1 million $US per year?? (It is in his white paper).

    So, who is paying for the tunes Bruce is piping nowadays?

    His whole points boil down to this: get rid of all GPL requirements, because it is "bad for business".

    The idea of Free Software is to share, but it is also to "give back if you received". Qt, used under the GPL requires to give back code, while Qt used under a Commercial license requires to give back money (should you for some reasons not want to comply with the GPL) to the developers whose work you are utilizing....

    Has Bruce forgotten the basics he taught me once (a long time ago)?

    Bruce nowadays wants to change the emphasis more torwards an LPGL/BSD-style licensing. RMS' and Linus' comments on this move should be quite interesting reading!

    Who is writing the secret agenda for UserLinux? Why is Bruce trying to forcefully kick out Qt/KDE?

    It is deeply ironic that...

    ...the former fiercest critics of Qt (who where right then), demanding Qt should be GPL-ed, are today morphing into 'gratis LPGL/BSD' style license advocates, now that Qt really *is* 100% GPL!

    ...and that the KDE group has now become the fiercest defenders of Free Software and the GPL a la Stallman!

    Ciao, a happy MacOSX user

    1. Re:They Better Call It GratisLinux by be-fan · · Score: 2, Interesting

      What the *fuck* is going on in Linux-land? It keeps getting trippier and trippier.

      --
      A deep unwavering belief is a sure sign you're missing something...
    2. Re:They Better Call It GratisLinux by Anonymous Coward · · Score: 0
      What about all those people in parts of the world that can't afford Qt. Fortunately, for them there is a library totally written and maintained by the free software community - GTK.

      RMS certainly never said that a combined Proprietary/GPL licence was better than the LGPL.

  118. Re:Perens is a Gnome Zealot(tm) by Anonymous Coward · · Score: 0

    so you payed 5 grand for a fucking girls computer to use a wheel mouse? I do that with my wife's dell running xp.

  119. qt with gtk? by Sunnan · · Score: 1

    Listen; in this post I won't debate the merits/lack-there-of of say, konq vs nautilus or kicker vs gpanel, just as a question.

    You can compile moz to sort-of use gtk and look like gtk. Same goes for Java. QT looks like windows on windows and sort-of like aqua on Mac OS X. Won't it make sense to have qt have a gtk/gdk backend? If gtk looks ugly, improve its looks. I'm just longing for a merger between the two camps.

    The same is true for GNUstep. I acknowledge that a lot of people prefer the programming paradigms inherent to KDE or GNUstep, but it feels like the time to choose a sort-of standard widget toolkit is now, esp. with say Cairo nearing.

    I'm not that much of a technical wizard, and I'm not intending to flame, just asking.

  120. Show me the beef by Stumbles · · Score: 0
    Perens has yet IMO given the real reason to splinter and divide such a large group of developers and users. He talks a similar sounding game as the proprietary folks. What research was his basis to conclude the business world wanted Gnome over KDE? I saw nothing in his white paper to support it, just a lot of speculation.

    IMO he has also failed to adequately explain the exclusion of KDE. Yes I know what he has said about Debian and AFAICS is not a relevant excuse. I could easily say Gnome rules over KDE on Mandrake or any other distro.

    Another point I find disturbing is this secret group of supporters. When will we know who they are and why do they need to hide? One of the greatest strengths of open source is it's transparency, I see none of this with Perens proposal, I see only deception. So I would really like to know his real motivations.

    --
    My karma is not a Chameleon.
  121. Oh... by Sunnan · · Score: 1

    The parent didn't say KDE was crashy.
    Stable has many meanings.

    1. Re:Oh... by RoLi · · Score: 2, Insightful
      Yeah, one meaning is to think first and then stick to decisions and

      • not change window managers with each release
      • not change toolkit APIs with each release
      • not moronically start to partly copy the worst parts of Windows ever envisioned (the registry)

    2. Re:Oh... by Anonymous Coward · · Score: 0

      Well yesterday a random screen saver took it down on my box.

      KDE is pretty, GNOME is a dog. A dog that should be beaten.

    3. Re:Oh... by LizardKing · · Score: 1

      not change window managers with each release

      The original GNOME chose to be window manager agnostic, but it usually shipped with Enlightenment. Since then, two window managers have been the official choice of the GNOME project, with metacity being the standard since GNOME 2.0 was released. To the average user, the switch from sawfish to metacity was seamless.

      not change toolkit APIs with each release

      There has been one major API overhaul in GTK+ since its adoption by the GNOME project, and that still allows the older API to be used until the next major version. Having maintained a number of GTK+ applications since the October GNOME era, I can assure you that GTK+ API changes have had less impact than the switches from Qt 1.x, 2.x and 3.x. The only windowing API that has remained backwards compatible during this period despite changes to it, is Win32 - and that's why it's such an ugly mess.

      not moronically start to partly copy the worst parts of Windows ever envisioned (the registry)

      The Windows registry was a good idea, but badly implemented. The Gconf system relies on a much simpler XML backend built on top of the superb libxml2 library. Other backends can be plugged in, but none have gone beyond the proof of concept stage, as the XML one has proved itself to be excellent. What do you suggest instead? Separate configuration file formats for each application?

      If you enjoy KDE with it's fetish for configuration dialogs, slow startup times and reliance on Qt (MOC - what a fscking joke), then so be it.

      Chris

  122. UserLinux --- NOT by Anonymous Coward · · Score: 0

    Why is it called "UserLinux" when it is aimed at the business folks?

  123. Re: Java desktop ? by Cochonou · · Score: 1

    " I'm not talking down on GNOME here, but KDE is more mature and all the major business wins Linux has had so far were with (and because of) KDE."

    Then what about Java Desktop, which includes only GNOME ?

  124. Re:But how good is GTK+'s Windows support? by Anonymous Coward · · Score: 0

    and GTK+ working on Windows affect UserLinux how?

  125. Force them to use only Emacs by axxackall · · Score: 0, Troll
    would be like only including VI and not Emacs (or Emacs and not VI), and forcing all users to use one.

    Forcing users to use only Emacs and not VI is The Good Thing (TM). VI should be dead together with Assembly language both are too primitive for modern tasks (but both still can be used for very specific tasks).

    The comparison is not correct since both KDE and GNOME are not primitive (well, GNOME is better and more power and more applications, but this remark about GNOME is my personal opinion).

    --

    Less is more !
  126. Deja Vu? by k8to · · Score: 1

    Bruce Perens is repeating all the same things with this "User Linux" idea he tried years ago with his "Linux Standard Base" idea. A standard distribution that should be the generic linux choice, based on Debian, using gnome not KDE, etc. etc.

    Bruce Prens, no one liked your vision then, why do you think they will like it now? Or, is it in fact a different vision? If so, you need to try harder to make that clear, because right now it looks like you're just going to push the same ideas harder this time.

    --
    -josh
  127. but GTK+ is LGPL, GPL doesn't allow closed source by Anonymous Coward · · Score: 0

    that's what he means by "commercial"!

  128. What happened to Free as in Speech? by LMCBoy · · Score: 1

    Sounds to me like UserLinux is completely turning its back on Free-as-in-Speech, in favor of Free Beer. What's wrong with expecting companies to pay a nominal developer fee for use of an excellent API for proprietary software? They should be used to that, and I think they would understand and accept the value of the investment. By all accounts, Qt is a far superior toolkit to Gtk, and you get commercial support to boot. Plus, there's the incentive for the companies to actually contribute back to the community by GPL'ing their apps (since they would then avoid the Qt fee). Gtk may be free beer, but you get what you pay for.

    This issue really clearly demonstrates the difference between the "Open Source" and "Free Software" philosophies. I generally respect and admire Mr. Perens, but I can't help feeling that he is selling out here, and selling the rest of us short, in a way.

    --
    Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
  129. Different business models by infolib · · Score: 1

    KDE vs. Gnome (QT vs. GTK) is really about two business models competingAE:
    KDE: TrollTech pays for library development, but for proprietary software it'll cost you.
    Gnome: No (direct) profit from libraries, but they can be used in commercial apps freely.

    Both business models make sense, but Perens has chosen his favourite. So have I - and it's KDE. No need to flame Perens for that reason though, if he wants to do something stupid it's not my problem ;-)

    --
    Any sufficiently advanced libertarian utopia is indistinguishable from government.
  130. Why KDE would be a better choice... by KewlPC · · Score: 1

    First of all, the argument that GNOME is the better choice for multi-platform shops due to the lack of licensing issues is missing a crucial point: the Windows and Mac OS X ports of GTK suck hard. Just ask the CinePaint developers.

    Second, if GNOME is so much faster and so much more stable then why are major VFX studios like Digital Domain and ILM using KDE?

    Thirdly, the API for QT is 10x better than GTK's API. GTK can't even do MDI-style interfaces, for crying out loud. All of GTK's problems can be traced back to the fact that it was designed with The GIMP in mind (which in and of itself is no miracle of GUI or API design).

    Fourthly, the documentation for QT is superior to GTK's barebones "documentation."

    Fifthly, the KDE user interface is much more consistent. Virtually all KDE apps have the same basic interface. The same cannot be said of GNOME and programs that just use GTK.

    1. Re:Why KDE would be a better choice... by damiam · · Score: 1
      GTK can't even do MDI-style interfaces, for crying out loud.

      GTK can do tabbed-based MDI, as found in gedit and friends. Microsoft-style window-in-window MDI is not supported by GTK because it's generally considered to be bad for usability. Note that even new releases of MS Office have moved away from window-in-window MDI in favor of multi-window SDI, and that MacOS has never supported MDI in any form.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    2. Re:Why KDE would be a better choice... by Ricin · · Score: 1

      Partly reply to TP, mostly general comments...

      I agree with the Win (and Mac?) ports of GTK sucking. Ppl who want crossplatform support usually go for wx instead I guess.

      And (diffent subject, but related to what TP said last) I'm quite fond of GTK but I'm having a bad time with so much of GTK2 apps/functionality being tied into gnome. Guess what, I use xfce, not gnome but I get 3/4 of gnome nonetheless if I want a nice gtk2/AAfonts/themes desktop.

      I've used GTK through py-GTK and wxPython (latter has better docs) and now that I'm using xfce as a DE for a while I have to say it has prettied up a lot. Having said that, qt/kde are leading here still and that's good for them.

      You might have noticed I like python and unfortunately I've not managed to get py-qt/py-kde to build yet (FreeBSD) but I'm sure I'll have a look at that again soon once kde3.2 gets final and I want another DE to play with.

      In case you're wondering, I've used mostly kde but also (on and off) blackbox, IceWM+ROX, xfce as DE. I never could stand gnome, but perhaps I should try that again too now everything (well almost, no? ;-) is GTK2.

      I don't like some of the FSF'ish zealots that seem to associate themselves with gnome either. And I can't but help to stress once more that the prime reason to start gnome was... kde. Slashback if you like but that was it.

    3. Re:Why KDE would be a better choice... by be-fan · · Score: 1

      Windows-style MDI is bad, but KDE doesn't do only Windows-style MDI. The newest version implements a mode called IDEAL (I think its derived from IntelliJ). Its a huge leap over traditional MDI.

      --
      A deep unwavering belief is a sure sign you're missing something...
    4. Re:Why KDE would be a better choice... by Anonymous Coward · · Score: 0

      ILM uses GNOME.

    5. Re:Why KDE would be a better choice... by KewlPC · · Score: 1

      Care to back that up with screenshots? I distinctly remember seeing on the Pirates of the Caribbean DVD extras a shot of an ILM artist's workstation, and it looked like KDE to me.

      At any rate, Digital Domain and others (such as Rythm & Hues) use KDE.

  131. UserLinux ? A massive Contradiction ? by phoxix · · Score: 1

    They say that by removing GNOME, the business is given less of a choice, and somehow that is supposed to be better.

    So you remove the KDE/GNOME issue. But now add the LSB/UnitedLinux issue. Whats the point ? I think the KDE/GNOME issue is much smaller than choosing between LSB/UnitedLinux

    Additionally LSB is already backed by Redhat, Mandrake, Novell/SuSE and many others, *AND* Debian itself is a participant of the LSB project (its even on LSB's front page

    As a non-debian user ... I keep looking at UserLinux and wondering "Whats in it for us non debian using majority?"

    Additionally, Bruce has yet to respond to this comment

    I'm not going to deny it, I for one think that UserLinux is going to fail, and rightly so.

    Sunny Dubey

    1. Re:UserLinux ? A massive Contradiction ? by damiam · · Score: 1

      Bruce Perens founded the LSB. I don't think he's planning on competing with it. Presumably UnitedLinux will attempt to implement the LSB, just as Debian does.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
  132. WOOPS!! s/UnitedLinux/UserLinux by phoxix · · Score: 1

    sorry mates,

    I messed the two up. I mean to say UserLinux and NOT UnitedLinux

    Sunny Dubey

  133. Show me the "KDE is more Robust"ness! by bjarvis354 · · Score: 1

    I am really curious now. I have been using GNOME since before QT went GPL. I was opposed the KDE back in those days, but I have since used KDE a few times, but I have to say that I didn't really like it that much. Am I wrong?

    GNOME seems like a logical choice for something like UserLinux. Licensing issues aside, GNOME 2.4 is simple, elegant, fast and very easy to use. But is is also powerful for the end users.

    Why is GNOME being beaten up so much here on Slashdot?

    1. Re:Show me the "KDE is more Robust"ness! by nagora · · Score: 1
      I have to say that I didn't really like it that much. Am I wrong?

      No, you're right: you don't like it much. Glad to help.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
  134. bogus choice confusion argument by Anonymous Coward · · Score: 1, Interesting

    The idea that Joe User will be confused by choices of desktop is somewhat bogus. He'll use whatever the default is. The reason for including both is that they can run each others apps. If the default is Gnome and he wants to fire up this konqueror browser someone told him about, he just does it and it works. He doesn't even need to know that KDE is a desktop environment.

  135. kde and gnome both suck.. by Suppafly · · Score: 2, Interesting

    Honestly not trying to troll here, but both kde and gnome, as they are installed by most popular distros atleast, suck. I've seen a lot of linux systems that boot into windows faster than they boot linux and start up gnome or kde.

    KDE and Gnome are not good examples to use if you are against bloat of any kind. It'd seem wiser, albeit harder, to take a simpler window/desktop manager and build upon it to make something that was halfway useable and consistant in design.

    1. Re:kde and gnome both suck.. by The+One+KEA · · Score: 1

      That's what XFce 4 is supposed to be. I've switched from KDE 3.1 to XFce 4 and am amazed at how much faster logins are now - it used to take six to eight seconds to log in, and now it only takes two!

      The best thing is that the Red Hat 9 RPMs integrate with the XFree86 graphical login manager, so when you reach the login screen you can select XFce 4 in lieu of KDE and switch back if you wish!

      Check it out here.

      --
      SCREW THE ADS! http://adblock.mozdev.org/ Proud user of teh Fox of Fire - Registered Linux User #289618
    2. Re:kde and gnome both suck.. by Anonymous Coward · · Score: 0

      That's what XFce 4 is supposed to be

      It's still based on the crap GTK+ toolkit, though. For developers that means no improvement over Gnome.

    3. Re:kde and gnome both suck.. by advocate_one · · Score: 1
      "I've seen a lot of linux systems that boot into windows faster than they boot linux and start up gnome or kde."

      Rather irrelevant when you consider the uptimes of Linux vs windows... currently I'm at 20.7 days uptime on this new SuSE 9.0 install and that's since first reboot from install and I've spent some ten days in this KDE session... oh and I've got a gnome session running on the other desktop (Ctrl Alt F8) as well as an XFCE session going as well (Ctrl Alt F9)... oh and my Mandrake 9.2 box has got some 25 days solid in one KDE session...

      So reboot and KDE/gnome startup times become irrelevant when measured against how long those sessions actually stay up...

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    4. Re:kde and gnome both suck.. by Anonymous Coward · · Score: 0

      They not only suck from the users' viewpoint, they also both suck from a technical viewpoint.

      Gnome is based on the GTK+ toolkit, which is a C toolkit. C was a good language in its day, but has been superseded for application-level projects by C++. C++ fully supports modern object-oriented programming.

      KDE at least is a C++ toolkit, but it was developed before the Standard Template Library came into common use, so "does its own thing" in a lot of places where it shouldn't. It is also not particularly well designed; there was a convincingly devastating critique of it by Al Stevens in Dr Dobbs Journal a few years ago (not freely accessible on the web, unfortunately). What we really need is one good toolkit, not two half-assed piles of crap.

  136. Time for a Fork already? by nurb432 · · Score: 1

    Seems they are setting themselves up to be fragmented even before they get off the ground.

    Regardless of the "better" choice, making any choice like this will cause that.

    Personally ill go for the KDE fork.... but that's just me, as I think KDE is a the more consistent, businesslike environment.

    --
    ---- Booth was a patriot ----
  137. There will be a KDE UserLinux. It has started! by a.ameri · · Score: 5, Interesting

    A few days ago, when I read Bruce Perens response (or rather defence) on his choice of GUI, there was one part of his response that caught my eye: He said that individual support companies can add KDE and support it if they want. "It's not that we are removing KDE from Debian" he said.

    I contacted the UserLinux mailing list on behalf of a group/company that is considering becoming a support company for UserLinux in Iran. We badly need an Iranian distro with full support for the Farsi language, in Iran and as far as I can see there is a good market here for such a product. For months we have been thinking about wether we should roll out our own Debian-based distro, but haven't yet made our decision. (Well we have made Shabdix, which is a Live CD distro based on Knoppix). As everyone knows, maintaining a Linux distro is not a trivial task, and there is not enough financial incentive in it. UserLinux with it's proposed structure would have made an excellent choice for us.

    The problem is, during the past 1.5 year, our small group of Linux enthusiasts translated KDE to Farsi. Currently it has (near) full Farsi support, and right now offers something which Windows does not: a Farsi Graphical User Interface. KDE is the only environment which has been translated to Farsi, and as far as I know no one is planning on translating Gnome to Farsi, anytime soon. The situation here, is that if people are going to use Linux in Iran, the only player here is KDE. Gnome (currently) lacks Farsi support.

    Bruce's decision on GUI has made life hard for us. I Contacted UserLinux discussion mailing list to ask a couple of questions and to make things clear for myself (namely to ask how I as a support company will be able to add KDE, and still be considered UserLinux). Unfortunetely I didn't get a single reply on the mailing list. What actualy surprised me was that on UserLinux's only mailing list, most people were just trolls, engaging in endless flame wars. I didn't saw a single developer there, nothing cunstructive, just flame wars. Bruce Perens loudly speaks everywhere of UserLinux' more than 200 posts a day. What he doesn't speak about, is that these are mostly just flame wars.

    However Aaron Seigo, a respected KDE developer took the time to address some of my questions, and he made me aware of the other side of the coin: what KDE developers are doing. I am posting some parts of his mails, so that the slashdot community can also use his thoughts.

    He Wrote:
    "I've cc'd the kde-debian list on this, since doing User Linux but with KDE is what this project is about! there's no need to sacrifice KDE, or deal with putting KDE into User Linux on your own. simply join our efforts and we can all work together on this solution. we have dozens already involved and code is being written.

    After congradulating on his work I also wrote:
    " However I should note that while I will look with greatinterest to your project, it is a shame that such an old issue (GnomeVs. KDE) has seperated the community in this way.

    His responded:
    "please note that this old issue was not raised by us (people interested in KDE) but by Bruce Perens and some random GNOME fanatics. my position was and is based on market realities and inclusivity that does not suffer from choice proliferation (e.g. the "10 CD players, 20 text editors" problem) nor from economic drags on support (as Bruce tried to submit).

    I don't think GNOME should be excluded from User Linux, and i feel the same way about PostgreSQL vs MySQL as I do about GNOME vs KDE in User Linux, despite note liking MySQL as a RDBMs solution very much ... so you see it isn't so much a "KDE passion", but a realism."

    I also wrote:
    "UserLinux was/is a great idea, but it's strengh lies in the power of it's core organization,and how much it will be successful in getting IHV and ISV support Having two such projects competeing with each other will only damage both of these projects, as we all know that ISVs (and to so

    --
    -- /* Those who don't underestand Unix, are condemned to reinvent it poorly */
    1. Re:There will be a KDE UserLinux. It has started! by Anonymous Coward · · Score: 0

      You quoted Aaron Seigo:

      "in fact User Linux is, right now, on a path to release a technically flawed product..."

      If KDE isn't the default desktop environment, then the product is automatically technically flawed, according that view. Geez, get over yourselves already, OK?

      (Note the following is not aimed at Aaron.)

      The flames from KDE proponents on the UserLinux mailing list were absolutely disgraceful. Of course, flames from either KDE or Gnome partisans toward the other are old news.

      What makes this situation different is that these weren't just Slashdot monkeys or forum trolls, the hate and vitriol directed toward UserLinux, and Bruce Perens personally, actually came from fingers of important KDE developers who really should know better.

      I'm glad that the emphasis is now shifting back to where it should be: getting work done.

    2. Re:There will be a KDE UserLinux. It has started! by be-fan · · Score: 1

      Bitch about politics and flamage all you want, and espouse the virtues of just "getting work done" all you want. That doesn't change the fact that throughout the history of computing, technologies have lived or died based not on technical considerations, but political ones like these. Too often, technically inferior solutions have been adopted because they were politically more viable. Us engineers would like it to be different, but such is the way of the world.

      --
      A deep unwavering belief is a sure sign you're missing something...
  138. The picked the wrong toolkit by Anonymous Coward · · Score: 0

    What are the requirements they used to pick the toolkit? If they want a toolkit that's easy to use, portable, and well known by lots of people already, they picked the wrong one.

    They should have used GNUStep.

  139. Re:KDE is not to be ignored (but vi is) by Anonymous Coward · · Score: 1

    FWIW back when my programming class included a shell account for compiling ada and fortran emacs took a couple of days to use quickly and well. Vi caused this painful throbing in my head and visual hallucinations cosisting primarily of brilliant flashes of colors. I thought it was a tumor, but a grad student saw me passed out, and waved his hands and spoke an arcane spidery language before clicking on the keyboard and managing to quit.

    It only took a couple of minutes for someone to show me how to run the big brother data base out of emacs too.

    Face it, emacs rules. Even more brilliant than guiness in a bottle.

  140. Unless you want to make proprietary software... by Enucite · · Score: 1

    The Qt Free Edition is provided under both the Q Public License ("QPL") and the GPL. This specifies that you may freely use the Qt Free Edition for:
    Running software developed by others (e.g. KDE)
    Development of open source/non-proprietary software

    The Qt Professional / Enterprise Editions are available for development of commercial/proprietary software. If you wish to evaluate Qt/X11 for commercial use, please contact sales@trolltech.com.

  141. That was a brilliant troll by RevMike · · Score: 1

    I salute you! Kibo # 66

  142. Employee Choice Produces Cost, No Benefit by reallocate · · Score: 1

    No mistake. This distro targets the bunsiness community. It'll be lucky if potential customers recognize the word "Linux", much less KDE and Gnome.

    If you're paying for IT support, choice equals cost.(If you aren't paying for support, you're in trouble.) If you let your employees decide to use either KDE or Gnome, then you must train your support staff in both, and you must ensure that someone versed in both is always on duty.

    No financial benefit here, just downside. Pick Gnome or KDE and be happy.

    --
    -- Slashdot: When Public Access TV Says "No"
  143. KDE or GNOME fork.. by msimm · · Score: 1

    I'd rather see a someone take either project and standardize and codify it into a cleaner and more consistent environment. Neither Gnome nor KDE offer the consistency or utilitarian usefulness available with OSX or Windows and as totally unsexy as it is I think once its done we can get a lot more use out of Linux on the desktop. I think this should be considered our primary goal and instead of funding multiple separate projects I'd like to see Linux backing corporations backing a serious, unsexy one-size-fits-all desktop environment and until we have that we should not be considered a serious contender for the corporate or home desktop.

    I'm not trying to start a flame war and I'm not saying that neither environment has its merits (I believe they both do). I am saying that basic standardization is on a level of importance that should supercede the unique benefits of having Linux distro's depend on a multitude of drop-in desktop environments.

    Once we have a default standard in place interoperability between all window managers can be achieved, instead of programmers having to chose between one or the other themselves (not to mention the standard behavior of the applications!) they can focus on developing 'Linux' applications and fans of Gnome or KDE will have the benefit of being able to run them all, right in their native environment. That seems like something that would be worth focusing on.

    Merry Christmas! Happy Hanukkah!

    --
    Quack, quack.
    1. Re:KDE or GNOME fork.. by nthcolumnist · · Score: 1

      Mac OSX okay, Windows? Ugh! If ever there was an anti-argument. Personally I don't like the KDE look but in the past have found the KApplications to work better than the GNOME stuff. I like to mess about with the window managers, being able to choose. If you wanted one-size fits all then you'll disappoint one or the other camp. I wouldn't miss KDE but some might and eventually end up on MacOSX. I understand the developer's argument but must we choose? Isn't there a way you can develop without worring about the presentation layer?

  144. Perens should fix what he has started. by Anonymous Coward · · Score: 0

    Perens wrote the installer for Debian. It has to be the worst installer I have ever used. I am not talking about eye candy but functionality. Why doesn't he fix what he started and not inflict us with another distro.

  145. The white paper by Anonymous Coward · · Score: 1, Interesting

    In Perens original white paper he writes:
    "There are a number of Debian-derivative distributions that are naturals for this project. Notable are Skolelinux ("School Linux"), a project supported by governments and educational institutions of several European nations, the non-commercial projects Knoppix and Morphix, and the commercial Debian derivatives Progeny, Xandros, Libranet, and perhaps Lindows."
    Well most of these are KDE-centric so how likely is it they are going to follow his path of dumping KDE. Not a chance

  146. Re:wtf? by johnny+cleanshave · · Score: 1

    Have A Nice Day.

  147. Re:wtf? by drinkypoo · · Score: 1

    You just assigned the value of wet to water. You need to know your operators if you want to be modded up. And it doesn't hurt to be logged in, either.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  148. Re:Don't dodge the issue / Non issue by toga98 · · Score: 3, Informative

    The cost of a license for commercial development is not a valid argument. If a company develops an application for sale, the cost of a license is a fraction of the overall cost to develop, market, and maintain a product. As far as development kits go, the decision on which dev kit that gets chosen is based on quality, which will drive the cost of development in the long run, and company politics.

  149. YAY! by Anonymous Coward · · Score: 0

    They can base thier stupid distro around gnome, it will only make it easier for Mandrake to get people to help them out.

  150. And why don't you buy a clue by Anonymous Coward · · Score: 0

    Listen, GNOME 1.x was a dead end. I don't think anyone is going to dispute that. But the 2.x branch has been and is truly promising, with great things to come in 2.6.

    Have you actually used GConf? Why don't you fire up GNOME 2.4 and take a look at it right now.

    It is NOTHING but a standardized advanced option configuration interface just as is KDE's control center:
    - Options are seperated by application
    - Application options are further broken down in usually a coherent manner
    - Most options provide a sentence or two long DESCRIPTION of their function, and use DESCRIPTIVE names.
    - Most options are simple boolean checkboxes.

    How in the hell is this better or worse than KDE's control center? Heck, it's even the same visual layout: tree on the left and options for selected node on the right.

    At least GConf has a reasonably consistent interface. It would be interesting to count the number of options available in GConf vs. KDE control center. I wouldn't be at all suprised if it turns out that GNOME is actually MORE "configurable" for those that for whatever reason want to be hassled with that.

    1. Re:And why don't you buy a clue by Sunnan · · Score: 3, Interesting
      Yeah, I like GConf from a UI point of view, but how is it implemented "under the hood"? I heard MS are moving away from having the registry as one big clunky file and I just hope the gnome folk have had the forethought to do it right from the start.

      Some random opinion on GNOME vs KDE that I really ought to shut up about since noone's listening but hey, it's saturday morning:
      • GNOME 1.x sucked, 2.x is hmm, better, but has a long way to go
      • I'm aesthetically displeased with KDE all versions. This is a personal quirk of mine but it's strange.
      • The usability progress in Gnome is interesting and it makes me curious.
      • I honestly find zsh+ the gnu fileutils a lot easier to use and figure out than Konqueror.
      • Nautilus is still slooow.
      • KDE seems haunted by bad luck - everyone with a name (contrary to the polled masses, maybe) picks Gnome over them.
      • I never liked the TigerT-icon-fashion of gnome fame, even though I like some of his other art. (Though I hate rubbish "crystal" KDE icons where the folders just look like square blobs instead of folders. Eazel had some good shit going in the art division, and KDE's Slicker looks ok.)
      • The war between them is harmful and I wish they could merge. Like seriously merge. Like having qt use gtk. Like choosing gconf. And kwin. Or whatever. I have no preferences, I just think that they're both horribly incomplete when compared to each other. We have plenty of competition from non-free shit already. Time to drink each other's peace-kool-aid.
      • Like using the same widget tool kit and share subsets of each other's HIG. No need to share philosophy (like the number of options) yet, but things like button placement and other mundane non-hot buttons.

    2. Re:And why don't you buy a clue by be-fan · · Score: 1

      GConf is *not* easy enough to use to be a normal interface. There is a registry-style duplication of the key hierarchy that makes it difficult to find what you're looking for. Also, there is a lot of stuff in there that the user should not be messing with.

      --
      A deep unwavering belief is a sure sign you're missing something...
    3. Re:And why don't you buy a clue by be-fan · · Score: 1

      Heh. Button placement *isn't* a mundane issue. The GNOME camp decided to reverse the layout, and not use the "Apply" model anymore. I don't think that was a bad idea, but it has some major usability issues without having some sort of "undo" feature desktop-wide.

      --
      A deep unwavering belief is a sure sign you're missing something...
    4. Re:And why don't you buy a clue by Sunnan · · Score: 1

      You are correct - one of my friends stayed for the longest time from Gnome 2 because of the reversed layout.

      Though I meant in a more mundane sense like "how many pixels from the edge", that kind of stuff.

      Not that that should be specified in pixels, literally, but eh. I don't know. It's not a mundane issue, you win. I'm just so saddened because the two camps can't get along.

    5. Re:And why don't you buy a clue by be-fan · · Score: 1

      Don't know how it is in the GNOME camp, but KDE mostly uses auto-layout, so apps don't really specify how many pixels from the edge buttons are. KDE and GNOME are really a lot more different than people think. For example, a lot of people said that KDE should adopt something like the GNOME HIG. Well, much of the stuff in the GNOME HIG is not applicable to KDE. KDE's GUI framework operates at a higher level than that. For example, the XML-GUI mechanism automatically adds the standard actions ("Open/Close/etc") when appropriate.

      --
      A deep unwavering belief is a sure sign you're missing something...
    6. Re:And why don't you buy a clue by Anonymous Coward · · Score: 0

      GConf != Control Center you idiot. Do you always repeat what other people stuffed up your ass ?

      GConf is a configuration system. It was invented because Havoc Pennington believed that the old gnome-config sucked. Not to mention that the entire pain with schemas files sucks even more than going back to old gnome-config. I think you should first know what you are talking about.

    7. Re:And why don't you buy a clue by Anonymous Coward · · Score: 0

      "I just hope the gnome folk have had the forethought to do it right from the start."

      Why did Havoc Pennington recently changed the entire backend if it was 'forethought' and 'do it the right way from start'. I assume it wasn't that forethought and right as they make you belive. Otherwise these changes wouldn't have been necessary.

    8. Re:And why don't you buy a clue by Sunnan · · Score: 1

      I never said it was right from the start, I just said I hoped they'd done it right from the start.

      It seems like they at least had the forethought to separate the various interfaces so he could change the backend.

      I don't speak for Havoc, he has done a lot of quirky stuff and mistakes over the years, but I'm still a fan. Some of his stuff has changed the way I look at free software for the better.

    9. Re:And why don't you buy a clue by Sunnan · · Score: 1
      Don't know how it is in the GNOME camp, but KDE mostly uses auto-layout, so apps don't really specify how many pixels from the edge buttons are.

      Most modern GUI toolkits I've seen work like that. It was a truly bad example, and I'm sorry. (Someone told me that the original Mac HIG specified that and I thought that that was something the toolkit should take care of, so I couldn't drop that from my brain and it snuck in as an example, more like a simile than an actual example.)

      HIGs, though great, are much less valuable than usability testing by people of all kinds.
    10. Re:And why don't you buy a clue by prockcore · · Score: 1

      Yeah, I like GConf from a UI point of view, but how is it implemented "under the hood"? I heard MS are moving away from having the registry as one big clunky file and I just hope the gnome folk have had the forethought to do it right from the start.

      I'd say they did, instead of one big clunky file.. gconf's backend is stored as multiple xml files.

    11. Re:And why don't you buy a clue by 10Ghz · · Score: 1
      KDE seems haunted by bad luck - everyone with a name (contrary to the polled masses, maybe) picks Gnome over them.


      Such as? If we look at who has picked GNOME, we'll have Red Hat, UL (which doesn't have anything to show yet) and Sun. If we look at who has picked KDE we will have SUSE, Mandrake, Conectiva, Lindows, Lycoris, Xandros, Knoppix etc. etc.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    12. Re:And why don't you buy a clue by Anonymous Coward · · Score: 0

      Let us know when Qt finally gets layout containers that GTK has had from the beginning, will you? Aren't they prepetually "in the next version."

      Qt is one of the most overrated bits of software ever.

    13. Re:And why don't you buy a clue by Anonymous Coward · · Score: 0

      Under the hood, gconf isn't a single file, thankfully. It's actually a directory tree under ~/.gconf containing a bunch of XML files. (the directory structure matches the tree you see under gconf-editor). Unfortunately, gconf-editor doesn't produce very human-readable XML, but otherwise, you can just skip the skin-crawly regedit-like interface of gconf editor and take a text editor to the files.

    14. Re:And why don't you buy a clue by Elektroschock · · Score: 1

      * KDE seems haunted by bad luck - everyone with a name (contrary to the polled masses, maybe) picks Gnome over them. *

      In the USA perhaps because of RedHat. For desktop usage KDE has no alternative. Gnome 1.x was a hacker desktop. gnome 2.x became a "conservative corporate" de.

      BTW: KDE will also include gtk support.

    15. Re:And why don't you buy a clue by Sunnan · · Score: 1
      BTW: KDE will also include gtk support.

      What does that mean? In what sense?
    16. Re:And why don't you buy a clue by Sunnan · · Score: 1

      I guess you're right.

      Just goes to show that now matter how unbiased I try to be, I'll forget about stuff that happens in the KDE world.

      To me, and this is looking/talking subjectively, the gnome world seems to be a world of rock stars like Havoc, Nat and others.

      Maybe KDE looks that way for a KDE-head?

      I actually use neither at the moment. Both desktops are annoyingly bad. Though I use a lot of apps from the gnome/gtk world.

    17. Re:And why don't you buy a clue by Anonymous Coward · · Score: 0

      Considering that Novell has recently purchased Ximian (think Gnome), and is working on purchasing Suse, I would be surprised if we didn't see a change in the Suse distribution upcoming.

      Regardless, I think that there are very few people who have ever really used both Gnome and KDE. I don't mean "I installed KDE once, and didn't like it, so I switched back to Gnome the next day", I mean people who have really installed and thoroughly tested both desktops for extended periods of time (a month or more). Mostly I think this hast turned into an arguement between people who have only used (or programmed for) one desktop extensively (for me that's Gnome), and have barely touched the other (I've only used KDE for a few hours at a time a year or more ago). I'm sure there are people out there that are educated in both UIs, but I bet those people number in the dozens, not the hundreds.

    18. Re:And why don't you buy a clue by inc_x · · Score: 1
      > KDE seems haunted by bad luck - everyone with a name (contrary to the polled masses, maybe) picks Gnome over them.

      That has nothing to do with bad luck. It just means that Ximian and people such as Jeff Waugh do a good job in painting a picture.

      E.g. Nat Friedman of Ximian told the public at the recent Linux Desktop Conference that the City of Largo had switched to Ximian, somewhat to the surprise of the people at Largo With little tricks like that they try to pretend that GNOME is much more popular than it in fact is.

      Nat has a link to a book on his blog that explains such marketing tactics.

    19. Re:And why don't you buy a clue by Whatanut · · Score: 1

      FYI,

      The registry hasn't been one big clunky file in the NT side of things. There's about 5 big clunky system files and one clunky user file.

      --

      yvan eht nioj
    20. Re:And why don't you buy a clue by juhaz · · Score: 1

      SUSE, Mandrake, Conectiva, Lindows, Lycoris, Xandros, Knoppix etc. etc.

      5 of that list are not "someone with a name". NOBODY outside Slashdot knows what the heck are Conectiva, Lindows, Lycoris, Xandros, Knoppix etc. etc.

      And even SuSE and Mandrake are LOT smaller than RedHat and Sun. Whether UserLinux will be a "name" remains to be seen.

    21. Re:And why don't you buy a clue by 10Ghz · · Score: 1
      5 of that list are not "someone with a name". NOBODY outside Slashdot knows what the heck are Conectiva, Lindows, Lycoris, Xandros, Knoppix etc. etc.


      Well, your average Joe Sixpack doesn't know what Red Hat, Mandrake and SUSE are either. Lindows does have some exposure since it's available at Wal-Mart.

      And Conectiva is huge in Brasil. Just because it's not well-known in your area, does not mean that it's irrelevant everywhere.

      And even SuSE and Mandrake are LOT smaller than RedHat and Sun.


      In USA perhaps, but Mandrake and SUSE are huge in Europe.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    22. Re:And why don't you buy a clue by Sunnan · · Score: 1

      Yeah, I definitely agree, this is a big part of the problem, and I've thought so for a long time.
      I install KDE every now and then, but remove it after a couple of hours.
      I install Gnome every now and then, and keep it for a couple of days at least. And even when I'm not running Gnome, I'm running Sodipodi, The Gimp and other GTK-apps.

    23. Re:And why don't you buy a clue by Sunnan · · Score: 1

      Is the KDE Control Center easy enough to use to be a normal interface? I find both pretty hard to grokk, but I manage. Hard for me to be objective in the matter...

  151. Does anybody else find this ironic? by Anonymous Coward · · Score: 0

    I remember when the GNU folks were leading the charge against Qt because it wasn't free. Now GNOME is picked over KDE simply because GTK+ is *less* free than Qt, and thus more convienient for businesses?

    It seems like the Trolls are damned if they do, and damned if they don't.

  152. TitanicLinux would be a good name... by Anonymous Coward · · Score: 1, Funny

    ...since it is going under without KDE technoloty built-in...

  153. STOP IT! by Anonymous Coward · · Score: 0

    You KDE people are the biggest bunch of whiney bitches ever. So a distro chose Gnome instead of KDE; big friggin deal. Don't use it.

    It case you haven't noticed, companies are going to choose Gnome over KDE every time. Who in their right mind wants to pay $1500/developer just to write commercial software when a better platform exists for free? Exactly.

  154. KDE IS NOT FREE! by Anonymous Coward · · Score: 0
    The main problem with KDE is it relies on the non-free Qt libraries which are not open source and require a VERY expensive license for commercial distribution. KDE cannot be included in binary format in a distribution for this very reason. Also, the viral GPL license would force ALL packages in the distribution to be released under the GPL, thus KDE cannot be included.

    Now, granted this was the situation as of a few years ago so situations may have changed, but I seriously doubt it anymore than Linux ever supporting journaling file systems or more than one processor.

    -Marty McFly, the back to the future troll.

  155. qt dual licensed under GPL: MOD PARENT UP PLEASE by FreeUser · · Score: 1

    Trolltech has licensed Qt under the GPL for Linux, which is the same license as Gnome. They will also sell you another license if you don't like the GPL and want to write apps that link to Qt using some other more restrictive license.

    That is correct. Commerical developers actually have more options with qt than with gnome, in that they can release commercial GPLed software under both, but if they want to release a non-GPLed version, then qt offers them this option for a price.

    Whatever Bruce's reasons are for such a flame-inviting Jihad against KDE, the notion that qt doesn't allow commercial development and gtk/gnome does is absolutely fallacious. I suspect his reasons are not those described in this thread. I also suspect that this decision (to disregard the desktop choice of roughly half the Linux GUI-using population) will relegate his distribution to little more than Yet Another Fringe Curiosity, his name recognition nothwithstanding.

    --
    The Future of Human Evolution: Autonomy
  156. They need to include both sets of libraries by Micah · · Score: 1

    It's possibly OK to choose one desktop environment (WM, panel, etc) to support, but they need to include both KDE and Gnome libraries.

    KDE apps are better in some areas, and Gnome apps are better in some.

    AbiWord and Gnumeric beat the tar out of KOffice. Not to mention Gimp, XChat, and Pan; also the best in their fields.

    Similarly, you have things like Scribus which requires Qt/KDE and has no Gnome/GTK equivalent. I also think KMail is the best mail program on Linux (every time I tried Evolution, it failed miserably).

    So they need to include libraries and some applications from both environments. As Bill O'Reilly would say, "To not do so would be ridiculous."

    1. Re:They need to include both sets of libraries by Ashcrow · · Score: 1

      The GPL'd Qt libraries and possibly some KDE basic libraries will be included.

  157. I think you ment... by Natalie's+Hot+Grits · · Score: 2, Interesting

    .. What I can't understand is that the development effort is *much* bigger [In the United States] for Gnome than for KDE"

    In fact, KDE has a larger developer and user base than any other desktop environment (besides windows) in the world.

    --
    Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.
  158. Canopy Reps are on Trolltech Board. by Anonymous Coward · · Score: 0

    Ralph J. Yarro who is Darl McBride's boss is on the the Trolltech board of directors. Read and weep.
    and here

    Trolltech should come clean on exactly what's it relationship is with Canopy and SCO.

    Karma bombing pro-KDE posts will not make this issue go away.

    If Trolltech is so independent, why don't they vote Canopy's bums off the Trolltech board?

  159. hahaha by Ender+Ryan · · Score: 4, Insightful
    Yeesh, have you ever used anything other than a Windows PC? Only the windows version of Photoshop uses an MDI interface.

    I could go on to compare QT fans to Windows users... but that would be silly trolling :P

    BTW, the #1 reason people prefer Photoshop over The GIMP is most certainly NOT the GIU. That you think that certainly is telling. The reason people prefer Photoshop is a. 99.9% of people don't know WTF The Gimp is, and b. Photoshop has loads of extremely useful features and plugins that The GIMP lacks.

    In fact, I would argue that the latest versions of The GIMP have a much saner interface than Photoshop, but that doesn't nearly make up for the features The GIMP lacks.

    --
    Sticking feathers up your butt does not make you a chicken - Tyler Durden
    1. Re:hahaha by Celerian · · Score: 0

      Agreed. The GIMP really needs to get some better features. Until then, I'll stick with photoshop (not that I'm good at either).

    2. Re:hahaha by Anonymous Coward · · Score: 0

      Personaly I find the Gimp interface horrible. But of course it's not due to lack of MDI.

    3. Re:hahaha by KewlPC · · Score: 4, Insightful
      Actually, according to one poster on the CinePaint mailing list (which I believe was actually a reposting of a comment on Slashdot):

      the reason most studios that are Linux based use GIMP as their paint tool
      is because there is NO OTHER CHOICE. I work at one of the studios listed in
      the article. The artists on my team doing texture painting will actually go
      look for a 5 year old SGI octane with Photoshop 3.0 to use because it is
      faster and easier to use than GIMP. Let that settle in for a moment. These
      kids love fast machines, they crave them like crack cocaine. However, they
      will go sit in front of a 250MHz boat anchor and use a product released 8
      years ago because it is a better tool. GIMP has a UI that that the Surgeon
      General should place warnings on for RSI risks (repetitive stress injury for
      the non acronym types.)


      I think that pretty much settles that argument.

      And, for the record, I have used Photoshop on both PCs and Macs. And yes, you're right, Mac Photoshop's interface isn't quite MDI. That doesn't make GTK and The GIMP suck any less.

      I'm constantly hearing from Photoshop users how much they hate The GIMP's interface. More specifically, they hate the fact that in The GIMP it takes 5 clicks to do something that can be done in Photoshop with 1 or 2. They hate the way The GIMP does everything in separate windows. They hate the fact that they have to right-click on their image to get the right File menu to save the image because the File menu on the main GIMP window has no Save option. One of the smartest interface changes the CinePaint team made to their inherited GIMP interface was to put the right-click menu crap in a real menu bar on each image's window so that you can access it like a regular menu if you want to.
    4. Re:hahaha by Hooded+One · · Score: 2, Informative

      Yeesh, have you ever used anything other than a Windows PC? Only the windows version of Photoshop uses an MDI interface.

      You might just as easily say that only the Mac version doesn't use an MDI interface. Wow, look at how non-informative saying either is.

      Except that that'd be more correct since Photoshop was designed with MDI in mind, then adapted to fit the Mac idea of what's "usable." Also, even the non-MDI Mac interface of Photoshop isn't as bad as the GIMP. At least when you bring Photoshop to the front on a Mac you bring the entire application to the front, which is actually useful, as opposed to just bringing the tool palette to the front and having to raise all the other windows individually.

    5. Re:hahaha by Paradise+Pete · · Score: 1
      You might just as easily say that only the Mac version doesn't use an MDI interface

      The original argument was that Photoshop on Linux couldn't happen if MDI wasn't supported. Pointing out that the Mac version does not was done to counter that argument.

      since Photoshop was designed with MDI in mind, then adapted to fit the Mac idea of what's "usable."

      Photoshop was first developed for the Mac, so it seems more likely that it was the other way around.

    6. Re:hahaha by metamatic · · Score: 1

      Actually, the #1 reason people prefer Photoshop to The GIMP is that Photoshop has color matching. Without color matching, the GIMP is useless for professional graphics.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    7. Re:hahaha by haggar · · Score: 1

      Wow, mod parent up! I thought nobody would ever notice the "Save" menuitem problem in GIMP, but you just gave me hope in humankind! So, I wasnt the only one person in the whole world to go barking mad because of GIMP's fscked up user interface?

      --
      Sigged!
    8. Re:hahaha by shellbeach · · Score: 1

      I'm constantly hearing from Photoshop users how much they hate The GIMP's interface. More specifically, they hate the fact that in The GIMP it takes 5 clicks to do something that can be done in Photoshop with 1 or 2.

      Considering you can tear off menus in GTK, any common task should be at most a single click away. And considering that you can assign keyboard shortcuts to any comand you like just by pressing the combination when the mouse is over the menu option, any commonly used task is but a key press away. Your photoshop prefering friends are simply demonstrating that they don't know the power of GTK.

      They hate the fact that they have to right-click on their image to get the right File menu to save the image because the File menu on the main GIMP window has no Save option. One of the smartest interface changes the CinePaint team made to their inherited GIMP interface was to put the right-click menu crap in a real menu bar on each image's window so that you can access it like a regular menu if you want to.

      You obviously haven't used the development version of the GIMP, have you? The menu bar in each window is the default behaviour and has been for about a year.

      If you want to criticise the GIMP, that's fine - but please make some effort to get your facts straight before you do so! (and for the record - I do almost all my image manipulation using GIMP and only rarely have to use Photoshop; I feel exactly the same aversion to Photoshop's interface that you do towards the GIMP. I hate MDI interfaces, I hate those stupid little buttons which are actually a menu of buttons, so you can never find the button you're looking for, I hate the fact you can't assign keyboard shortcuts to menu items and I hate the fact I can't right click on an image and bring up the menu bar. Disliking an interface has everything to do with what you're used to, and very little to do with the actual usability of it)

    9. Re:hahaha by Perky_Goth · · Score: 1

      so they hate it because they aren't used to it...
      that's your basic argument. it doesn't sell.
      i've used neither, mind you...

  160. Slashdot loves an underdog by Cid+Highwind · · Score: 1

    It used to be KDE that got no coverage here and was flamed to death in every story about how great Gnome was. Now Slashdot has sensed a power shift. More companies are supporting Gnome development, and fewer distros are using KDE as the default GUI. Since Slashdot interprets accepting any commercial help as whoring out the ideals of free software, it's time for them to start supporting KDE.

    --
    0 1 - just my two bits
    1. Re:Slashdot loves an underdog by bjarvis354 · · Score: 1

      I see some truth in this...But if this is true why don't we see more people touting Hurd?

    2. Re:Slashdot loves an underdog by be-fan · · Score: 1

      There has also been a shift within the projects. KDE used to be the newbie oriented/more restrictive DE. It used to have problematic license terms and be based on a non-free toolkit. GNOME, on the other hand, was built with a free toolkit and had power-user features.

      Now, the roles have been reversed. KDE is fully-free, and has the power-user features. GNOME (in 2.x) has done a huge over-simplification and has alienated a lot of existing users (though, it got tons of new users attracted to the simplicity). Now, commercial companies appear to be using the LGPL-ness of GTK+ to push it as a proprietory-friendly standard desktop.

      If anything, Slashdot has been remarkably consistent in its outlook.

      --
      A deep unwavering belief is a sure sign you're missing something...
  161. Trolling Troll Tech by Anonymous Coward · · Score: 0

    Even if every outside investor (including Borland :-) were merely a shell corporation controlled by Canopy, they'd still have nowhere near the votes to influency anything at Trolltech.

    Oh, Canopy does sit on the Trolltech board. Sorry. That's influence.

    http://www.linuxsa.org.au/mailing-list/2003-05/5 66 .html

    " Under Ralph's direction, the Canopy Group has identified and invested
    in promising open source and Internet infrastructure technologies.
    Canopy's greatest strength lies in providing the companies that produce
    these technologies a sheltered environment in which they can grow and
    develop. Canopy companies are strongly encouraged to work with each in
    synergistic partnerships.

    Ralph also servers as Chairman of the Board of Trustees of Angel
    Partners, a 501(c)3 support organization for the Church of Jesus Christ
    of Latter-Day Saints. He is also a Trustee for the Noorda Family Trust,
    the Scenic View Center, and the Worth of a Soul Foundation. He is the
    Chairman of the Board of Directors of Altiris, AP Software, Caldera
    Systems, Center 7, Coresoft, and Helius. He sits on the Board of
    Directors for: the Canopy Group, 2NetFX, Arcanvs, Cogito, DataCrystal,
    Expressware, Global Prime, The Guy Store, HomePipeLine, iBase Systems,
    Interworks, Lineo, MTI, ManageMyMoney, Nombas, Profit Pro, Recruit
    Search, Troll Tech and TugNut."

  162. Java Desktop? by Anonymous Coward · · Score: 0

    This sounds eerily similar to Java Desktop except UserLinux is based off Debian instead of SuSE. Of course, UserLinux will be free as in Debian, but technically it seems they have the same goals.

    I think the big issue here is that Bruce wants the support of all these boot-cd distributions like Knoppix, Licoris, Mepis, etc, but they rely primarily on KDE! Now, one or the other is fine as long as you agree. If you eat enough of your own dog food it's bound to get better. But getting these fast paced, highly unstable, and heavily KDE favored existing Debian desktops on your side just got a whole lot harder.

  163. Finally the right thing! by lems1 · · Score: 1

    Bah, flame all you want. This is definitely the right thing to do. In over 4 years or so using Linux, I have never like KDE. Too windows-like. Gnome is a lot better choice and a better license all around.

    --
    This sig can be distributed under the LGPL license
  164. Re:wtf? by Anonymous Coward · · Score: 0

    1). bite my ==
    2). who wants to be modded up?
    3). actually take the time to create a login? jesus, next you'll be telling me to subscribe

  165. You just looked a gift horse in the mouth by Anonymous Coward · · Score: 0

    I have to post anonymously as I'm the CTO for a Fortune 250 company. I'm going out of my way to post this in support of the linux community as a "whole." I wont get into the whole GNOME versus KDE war because, quite honestly, it's a waste of my time and the time of the linux community as a "whole." My apologies for not giving you any flame bait.

    The whole reason that the business world as a whole has "NOT" switched to linux on a larger scale is the utter confusion of what's being offered. The amount of different distributions and packages out there is overwhelming to even the most seasoned corporate CTO that has a clue. Yes, we do exist! In the corporation that I work for there has been growing talk over the past year about moving to a purely linux environment. I am wholeheartedly in support of it, but I have continually shot it down officially to middle managment and to the board for the following reasons.

    The linux community, although unified on the free software front and providing a viable and robust alternative to Microsoft, is still fragmented over several issues the first and foremost being the GUI issue. The GNOME versus KDE war being the foremost. If we are going to impliment a linux migration within the next 24 - 48 months, pay for developers to help us with our transition and possibly write proprietary applications for us, then we need to work in an envrionment that doesn't require we pay for a proprietary developer licensing fee. Two, linux is still overly geeked. It is "NOT" being developed for the idiot user. I will not recommend to my board that we spend even more money on user training and support, when many in the linux community still maintain that arrogant and snobbish attitude of "Read the FSCKING manual." Most of our computer users are going to give up after 20 seconds of having to searh for and read thru the man pages in their current form. If we impliment linux, it has to be idiot proof and easy for the average user.I realize that the last reason is going to be a big piece of flamebait for alot of you out there, so be it. I don't care, but that's the attitude of many if not "MOST" of the CTO's/CIO's out there. We realize this, you do not.

    The bottom line is money, for any company. If it's going to cost us more money in the long run, long run in the corporate world being anything more than three quarters, to impliment a new operating system along with the software development and training associated with it you can just drop the whole idea. We realize this, you do not. We'd rather keep getting bent over the barrel by Microsoft and keep paying them their money because it keeps things going, so be it. We realize this, you do not.

    Huzzah!!! Bruce for putting your foot down and saying "we're going to do it like this" and going forward. I was already considering the debian distro for deployment, but now I think our deployment of linux companywide might happen sooner than later. At the very least, this will give me the ammunition to bend Microsoft over the barrel for once and get a better deal from them until we deploy linux. Bottom line is money folks, in all the ways it's spent. We realize this, you do not.....

    1. Re:You just looked a gift horse in the mouth by CryBaby · · Score: 2, Funny
      If we are going to impliment a linux migration within the next 24 - 48 months, pay for developers to help us with our transition and possibly write proprietary applications for us, then we need to work in an envrionment that doesn't require we pay for a proprietary developer licensing fee.
      Hey, maybe I can become the CTO of a fortune 250 company. At least I know how to spell "implement".

      Seriously, while I'm not familiar with QT's licensing fees and I'm too lazy to go read them, there's no way in hell that a few grand in licensing fees can offset the massive savings that would be realized by ditching Windows for a free desktop OS across thousands of PC's.

      Also, if you're really the CTO of fortune 250 company (*cough*), why don't you just call up Perens and try to influence the direction of UserLinux by funding a little development that specifically addresses your requirements? Remember, it's called "open source" as in "open to everyone". That includes businesses and even you personally. I realize this. You do not.

      Most (non-tech) businesses still view open source software as canned products developed my some mysterious "other" and never even think about taking a direct role in development. In other words, they still don't realize it's true potential or advantages. Think of this situation as "under-utilization of available assets" or "failure to consider a wide array of options."

      If you want to make (or save) enough money to substantially alter a large company's bottom line, you have to exercise leadership and creativity. A brilliant, original and trend-setting IT solution will not just show up on your doorstep with a EULA and a pretty brochure. I realize this. You do not.
    2. Re:You just looked a gift horse in the mouth by Anonymous Coward · · Score: 0

      Just an FYI, you don't see corporate America embracing whole heartedly the free software mantra in as much as we'd like them to. You take a poll and you'll find that that pretty much 90+% are taking a lets wait and see approach to the whole free software movement.

      I guess you're just too young to remember the days of mainframes, custom software, and the never ending turnstile of programmers coming in and out of your door that consistantly screwed up your code. These are just a few of the reasons that we all embraced MS products for our companies. Try and give your argument to boards on the fortune 1000 and you'll be laughed out the door. Showing a brilliant, original, and trend setting IT solution by diving head first into the free software mantra doesn't prove leadership and creativity. In fact it shows prudence. Then again, your same argument was the one that was used by all the dot-commers and look what happened there. We realize this, you do not

    3. Re:You just looked a gift horse in the mouth by CryBaby · · Score: 1

      You take a poll and you'll find that that pretty much 90+% are taking a lets wait and see approach to the whole free software movement.

      Replace "free software" with "PC" and you could have easily made that statement in 1982. You can keep your head in the sand or you can get off the sidelines and begin formal feasibility studies and cost analysis regarding the enterprise-wide adoption of an OSS desktop environment. I'm not claiming that the OSS desktop is ready for prime time right now in any particular business environment (e.g. your environment), but I do claim that it's close enough to be considered a viable option in the near term. Its adoption by various governmental organizations supports this claim.

      I guess you're just too young to remember the days of mainframes, custom software, and the never ending turnstile of programmers coming in and out of your door that consistantly (sic) screwed up your code. These are just a few of the reasons that we all embraced MS products for our companies.

      That's an amusing (and incorrect) assumption on your part regarding my age. In case you haven't noticed, those "days" you mention are still here. Is your ERP/accounting system running on Windows? Probably not. Chances are, the phrase "AS/400" is uttered on a daily basis in the halls of your IT dept. Do you use custom software? Yes. Do programmers still come in and out of your door and write shitty code? Well, some things never change. I'm just not sure how relevant your points are to the large-scale adoption of OSS client PC's.

      To be fair, I'll assume you are also bringing up entirely valid (critical, to be sure) concerns over standardization and support as it relates to OSS. A big part of the answer to those concerns is that large companies will have to funnel some of the massive savings they realize through OSS adoption back into OSS development. IOW, they (or 3rd parties, see below) will have to adopt, on some level, the DIY ethic and communal aspect of OSS.

      I realize this raises the spectre of "getting into the software development business" but of course no one would have to perform this work in-house. To anyone who has a problem with the "sharing" aspect of funding OSS development I would point out that when you buy MS products today you are funding the development of future MS products which will no doubt be available to your competitors.

      I concede that concerns over standardization justify a cautious and carefully measured approach to OSS. You can't "standardize" for long on something that ceases to exist. OTOH, by the time the OSS desktop is a "safe" enough option in your opinion, you may find that you have to jump through some major hoops to adapt your company to it rather than the other way around. Or, you may simply find that you've missed out on the opportunity to save a hell of a lot of money over the years.

      Perhaps it won't be necessary for businesses to directly involve themselves in OSS development and, instead, various 3rd parties will arise to fill OSS desktop needs, much as we've seen in the server market (certainly this will be the case for small to mid-size businesses). Even then, it would not be unprecedented for a large company to take a direct role in the creation or motivation of 3rd party vendors.

      Try and give your argument to boards on the fortune 1000 and you'll be laughed out the door.

      I wouldn't give any of the arguments I've laid out here to the board of any company. I would show them a couple of big pie charts demonstrating how many millions of dollars will be saved by transitioning to OSS clients (along with a few self-centered ideas about where to direct some of the savings). Of course, long before that I would have done my homework to see if OSS can meet our business needs. If you were an enterprising CTO, you would be in this phase right now. If you were a brilliant and ambitious CTO, you would have already i

  166. The mantra also applies to itself. by Draxinusom · · Score: 1

    There is more than one way to make a distro. Some distros are about choice, others are about easy of deployment, administration, and development. UserLinux is intended for corporate desktops, and in that situation you don't want to have to support two desktop environments, one of which uses a toolkit you have to pay money to use in commercial development.

  167. Open etter to Bruce Perens by Capt.+Beyond · · Score: 2, Insightful

    Bruce,
    You say you are trying to "advance Free Software in business", yet choose and promote a license who's entire existence is to provide closed source, proprietary software for a free, open source operating system.

    To me, this is hypocritical. You are not advancing Free Software in anyway when you choose to use the LGPL (i.e. GNOME). You are advancing closed source software.

    Qt is GPL'd, and as such does not allow closed source applications to be developed for free.

    Which toolkit advances Free Software more?

    --
    -- "Perceptions create reality. By changing your perceptions you change your reality."
  168. Bad bad bad by Anonymous Coward · · Score: 0

    I just started KCalc on my system and it took less than three seconds. I thought you might doubt it so, I restarted from the command line with time. Note that time counts until after KCalc is shut back down.

    $ time kcalc

    real 0m2.081s
    user 0m0.910s
    sys 0m0.060s

    The system is a:

    Compaq Deskpro EN
    PII 400
    128MB RAM
    Red Hat 7.3
    KDE 3.1.1
    KCalc 1.3.2

    Your system or its configuration is severly broken.

  169. VHS and Beta by tepples · · Score: 1

    it might just mean that GNOME "wins" by virtue of commercial forces rather than technical ones.

    So does that make KDE the Betamax to GNOME's VHS?

    1. Re:VHS and Beta by be-fan · · Score: 1

      I hope I'm full of shit and it never comes to that, but that's what I'm afraid of.

      --
      A deep unwavering belief is a sure sign you're missing something...
  170. if your package pool doesn't have kio fish... by Anonymous Coward · · Score: 0

    ...then I'm not swimming. Both gnome and kde are great gui environments, but kio fish makes KDE a better choice for my multi-machine navigation. If that drops out of the picture (has the new gnome file system widget come out yet?) then I'm back on the fence preference-wise.

  171. GNOME has better apps, PERIOD by Ars-Fartsica · · Score: 1

    Abiword and Gnumeric are much stronger than their KOffice counterparts. Mozilla/GTK2 and its variants (Epiphany etc) destroy Konq. From an end-user app selection, there is no comparison. KDevelop is the only KDE app I know that destroys its GNOME competition.

  172. It's his attitude, not his goals by omega9 · · Score: 2, Interesting

    Some quick quotes:

    I am interested in seeing the GUI argument end, as I've just read all of the postings in it and didn't learn much during those several hours.

    That's what happens when you make up your mind before you even start the conversation. It's common in people who think they're smarter then everyone else and believe they know what's best.

    But the most ludicrous aspect of the Fedora project is that with Fedora, Red Hat seeks to achieve what Debian did long ago.

    Fedora is a fellow Linux distribution, worked on by people like you and me, hackers with ideas. There's no reason to call them ludicrous. It's rude and uncalled for.

    The goals of UserLinux are compatible with Debian's Social Contract, which I created.

    I'm starting to get numb to you tooting your own horn. Your achievements are impressive, but they're soured by all your boasting. Yeah, yeah.. you're great... blah blah blah

    Mandrake sent an inquiry and we don't yet know how they'd fit. .... There are a number of Debian-derivative distributions that are naturals for this project.

    This is interesting, as you're basing merit on whether or not a distro is Debian based. The initial mention of Mandrake could possibly have been from a corporate standpoint, but it's followed allmost immediately by the Debian reference, which assumes their worth simple because of their distro heritage. Clearly, being a Linux advocate/hacker isn't good enough unless you're a Debian advocate/hacker. This attitude is given more weight by the following line.

    There have been suggestions regarding Linux platforms other than Red Hat and Debian, which I have classified as partisan.

    Considering the previous, I guess this is no suprise.

    You've got good goals Bruce. I don't think you'll find an arguement concerning you're overall idea. But you've got to stop being so self-centered and treat your fellow community with a little more respect, else you'll be dancing alone with your ego. Even if you do help to construct "billion dollar contracts", money can't buy you love, happiness, or my respect.

    --
    I'm against picketing, but I don't know how to show it.
  173. Have you tried Ximbiot? by tepples · · Score: 1

    but they still hated CVS, one of the arguments used against it is that there's no support.

    The thing about free software is that any firm is free to sell support for it, creating a free market in support. For example, here's a firm that sells support for CVS.

    1. Re:Have you tried Ximbiot? by NDPTAL85 · · Score: 1

      Good luck with a business model of trying to sell software that some 3rd party has to support instead of the company thats selling it in the first place. Corporations would be REAL comfortable with THAT setup.

      --
      Mac OS X and Windows XP working side by side to fight back the night.
  174. KDE on RH9 by benjamindees · · Score: 1

    KDE is *very* poorly integrated on RedHat 9. I've spent the last month picking it apart to try to make it faster. You should ditch GDM (why is that the default with KDE?); that would at least prevent a few Gnome libraries from taking up memory and maybe make KDE start up faster. Add DISPLAYMANAGER="KDE" to /etc/sysconfig/desktop.

    --
    "I assumed blithely that there were no elves out there in the darkness"
  175. Gnome sucks by codepunk · · Score: 1

    I think Gnome is a hideous ugly desktop compared to KDE but for architectual reasons I think it is best to stick with GNOME. The best thing about GNOME is that the libs are based on C vs C++. Not all languages can deal very well with a C++ based library, which hurts integration capabilities with KDE. I think someone needs to go back and get corba out of GNOME. Corba was cool buzzword technology but is a bitch to program against and a pain in the arse dealing with compiled interface crap. Base the integration capabilities on something that can be hit easily from any language on any platform like XMLRPC. As much as I like KDE it pains me to say sticking with GNOME is a good idea for the long haul.

    --


    Got Code?
  176. VMware configuration has a GUI by tepples · · Score: 1

    VMWare has a GUI? Maybe I'm missing the whole point of what VMWare is.

    VMware is a dynamic recompiling[1] x86 emulator for the x86 PC. The program consists of the emulator plus a set of GUI forms used to configure the characteristics of the emulated chipset, and I'm assuming based on previous comments that these GUI forms use GTK+.

  177. That's what the KDE Help Center is dumbass by Anonymous Coward · · Score: 0

    If you had actually used KDE, you would see that there is a big happy crystal themed ship life-ring thingy. This gives you access to KDE help, unix man pages, and IIRC the special Gnome wacko documentation.
    "The KDE team welcomes you to user-friendly UNIX(R) computing"

  178. True, but not entirely. by mindstrm · · Score: 4, Insightful

    Do people *really* demand choice? Did everyone DEMAND a big choice of window managers and desktop systems? No.. they really didn't... that's just how things evolved.

    I use OSX all the time, and I'm traditionally that guy who uses linux and whatever window manager currently catches my eye.

    It's not just about lack of choice.. it's about stability of the target. A developer can know clearly what his target audience has when developing applications for OSX. That's hard, with linux.

    Though you may feel the classic MacOS environments were about lack of choice, and confining the user to an unchanging experience, that's not the case anymore.

    I don't NEED to mess around with every aspect of my GUI.. I know it can be fun.. but if it was well designed in the first place, we would have a lot less people worrying about skinning it. Go look at a room full of OS X users.. most of the desktops look the same. Any one user could quickly make use of any other user's desktop.. and believe me, it's not because skinning and manipulating the GUI is any harder than it is with X (though I"m sure someone will come up with examples of things)

    More important is the fact that the OS X Gui is designed *well*. IT's open; you can write apps for it easily. IT WORKS.. if you have never really sat down to use it, and spent an hour or two getting to know it, you don't know even know what a good GUI *IS*, because you've probably never used one. Windows is pale by comparison, KDE as well (it's on par with windows in my books, in terms of usability). Some GNOME setups I've seen are better... more well thought out, not just copying windows... but still a far cry from what Apple has achieved.

    If the desktop is well designed, yet extensible, there is no reason to hvae 20 totally different versions floating around.

    Also, it's not because the end user doesn't want choice.. tis' because the developer needs a stable target.

    Ask yourself: If you want to write a state of the art gui app for linux, that interoprates with the OS properly, drag and drop, print menus, cut and paste, etc... how will you do it? what toolkits and libraries will you choose? KDE? Gnome? Neither, just use TK? Do it totally self contained, so it looks like a uniqe app, sort of like xmms?

    That choice is clear with Apple, and clear with Microsoft.

    1. Re:True, but not entirely. by Elektroschock · · Score: 1

      But why does he chose Gnome? Gnome is not suited for the user desktop right now. I understand that he likes gnome, but it is not ready yet. In Europe Linux on the desktop means Linux/KDE. You cannot sell Gnome to the enterprises. Gnome seems to look like a conservative corporate desktop environment. So it is no fun anymore, but users don't want a grey dressed desktop.

    2. Re:True, but not entirely. by jeremyp · · Score: 1

      I assume you mean Bruce Perens. So why don't you *read* his article? His one and only reason for going with Gnome is because you don't have to pay the developers a royalty if you develop a commercial solution with it.

      --
      All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
  179. I hope this means by xutopia · · Score: 1

    that the installation CD will be only one and not 6.

  180. You don't have to pay extra thanks to GNU by tepples · · Score: 1

    If I buy Solaris I have to pay extra for the compiler

    Or use GCC and Lesstif.

    If I buy Windows I have to pay extra for the compiler

    Or use GCC and the w32api package.

    1. Re:You don't have to pay extra thanks to GNU by alienw · · Score: 1

      Or use GCC and the w32api package.

      GCC doesn't support even basic Windows things like resources. It's not possible to make a production-quality program with GCC on win32.

    2. Re:You don't have to pay extra thanks to GNU by tepples · · Score: 1

      GCC doesn't support even basic Windows things like resources.

      The MinGW version of Binutils includes Windres, which is a free Win32 resource compiler. Which other "basic Windows things" do you claim GCC does not support?

    3. Re:You don't have to pay extra thanks to GNU by Brandybuck · · Score: 1

      Or use GCC and Lesstif.

      I said development for the Solaris desktop. Currently that's still CDE. Will Lesstif apps transparently link to Motif libraries? I'm not sure, but I could be wrong.

      --
      Don't blame me, I didn't vote for either of them!
  181. Human interface guidelines by tepples · · Score: 1

    Making a specification that says quit is "CTRL+Q" is. Making a specification that says "this is how you handle a clipboard" is. Making a specification that says "this is how to handle drag-n-drop" is.

    But by the time you've given a hundred such rules, you've reproduced either the GNOME human interface guidelines or those of KDE.

    1. Re:Human interface guidelines by Dalcius · · Score: 1

      Which is why you only cover the basics to keep the interfaces generally the same. The point is to allow choice but to allow a user to learn one desktop and be able to deal with others and not be a geek. None of this requires picking a single web browser or desktop.

      The community can't decide on a favorite distro, so picking applications isn't going to work here. What we CAN decide on is how things should work on a general level, and I think THAT is what will help companies embrace Linux.

      Windows is a homogenous environment, so it's easy to train folks who have used it before. If we can give Linux a little consistancy, I think we'll gain much of the benefit that Windows has.

      --
      ~Dalcius
      Rome wasn't burnt in a day.
  182. puuh by Anonymous Coward · · Score: 0

    kde is only even NEARLY usable unix desktop environment and youre including 100000 years obsolate Gnome? good luck...

  183. Re:But how good is GTK+'s Windows support? by Anonymous Coward · · Score: 0

    Application support, you fuckwad.

  184. KDE Maturity by Anonymous Coward · · Score: 0

    KDE has a better set of technologies underlying it, I think. And businesses don't care as much about liscense fees. That's what geeks care about. Free Software as in beer is a geek thing. People don't hoard to Linux because it's free; they do so because it's functional. If it costs more to have greater functionality, so be it. Free with lesser underlying technologies isn't any good.

  185. Re:UserLinux == Great Idea (not!) by Anonymous Coward · · Score: 1, Insightful

    This seems to me to be one man's idea's of what linux should be. Throwing out support for KDE on
    such a grandious project is simply throwing away half of all linux users. UserLiniux seems to me to be a great way for one man to toot-his-own-horn at
    the expense of the linux community. We've lived with KDE's (QT's) License for a while... it doesn't seem to stop people from using and developing for KDE. It's obvious with limitations imposed as a base distro; this is going to be a micro distro with alot of software limitations. I'll never use it.

  186. Slashdot personals by lewp · · Score: 1

    Did I just see an ad for Slashdot personals? I'm sure that'll go well...

    Haha.

    --
    Game... blouses.
  187. Religious/political? Try "Economic" by tepples · · Score: 1

    Begun, the flame wars have.

    Bingo.

    I think the inclusion of one [major free X11 desktop environment] over the other should NOT be made primarily on Religious/political grounds, but on Technical ones.

    Issues that some might characterize as "Religious/political" may more precisely be "economic." Perens would have one believe that it's less expensive to build and deploy an in-house GTK+ app than an in-house Qt app. If an app contains trade secrets, then GTK+'s weaker copyleft lets the app stay in-house, whereas Qt Proprietary costs four figures per developer per version, and Qt Free gives your employees the right to leak anything produced using it. In addition, even for apps that don't bear trade secrets, GTK+ is ported natively to a particular immensely popular proprietary operating system, whereas Qt Free needs the heavyweight Cygwin layer.

    1. Re:Religious/political? Try "Economic" by fault0 · · Score: 1

      > GTK+ is ported natively to a particular immensely popular proprietary operating system

      Erm, the gtk+ windows port is still _very_ raw.

      > whereas Qt Free needs the heavyweight Cygwin layer.

      Qt-win32, which is the port of Qt/free from X11 to win32, _barely_ requires Cygwin at this point. Over the past few six months or so, it has matured to a point where all X11 classes have been ported to GDI. The next step is to port the three or four remaining classes that require Cygwin to native windows. If you chose not to compile in Qt's networking classes (actually, only the DNS classes aren't ported right now), you can likely build Qt/free on Visual C++.

  188. Not on Windows it doesn't by tepples · · Score: 1

    Developers can write commercial apps to their hearts content using QT with complete freedom (beer & speech) as long as your apps are GPL'd.

    True, but deploying those apps to users of a particular immensely popular proprietary operating system currently requires an additional heavyweight API translation layer, which can eat performance when deploying an app in a heterogeneous computing environment or to users outside a company.

  189. Nope. by mindstrm · · Score: 1

    It really stands for:
    Escape-Meta-Alt-Control-Shift

    which should be obvious to anyone has ever used it.

    The name also rang true for a long time, back when memory was a bit more expenisve, as:

    Eight-Megs-And-Constantly-Swapping

  190. We don't have to choose.. by msimm · · Score: 1

    That would be the advanage of having a standard. KDE and Gnome would be able to work with it seamlessly, it would just be that there would be a basic underlying principle at work underneath. I agree with you that we do need choice and it would be silly for me to advoce from anything that would stip that away. Think of the idea of a default 'standarized' DE as a basic starting point for new users or users that can't be bothered with their desktop's specifics (read: business). This way you end up with a standard they can use and compatability between YOUR paricular favorite DE and the defacto should be seamless (open standards, available source code, documentation). Until we have this we are basically just forming desktop factions.

    --
    Quack, quack.
  191. FSF: GPL better than LGPL by DVega · · Score: 2, Informative
    According the Free Software Foundation, the GPL (the one used by Qt) is better than the LGPL (the one used by GTK+). That's why LGPL means "Lesser General Public License".

    The GPL promotes Free software development, because you are only allowed to create Free applications with it.

    --
    MOD THE CHILD UP!
    1. Re:FSF: GPL better than LGPL by 0x0d0a · · Score: 1

      The GPL promotes Free software development, because you are only allowed to create Free applications with it.

      Conclusion does not follow.

      I could say that the LGPL promotes Free software development, because it lowers the barrier to use for a lot of people and software, and means that more people get brought into the Linux fold (where divide and conquer allows OSS to tear up closed source).

    2. Re:FSF: GPL better than LGPL by Elektroschock · · Score: 1

      My personla opinion is that most system software shall be GPL.

    3. Re:FSF: GPL better than LGPL by cduffy · · Score: 1

      I know perfectly well what the FSF thinks. I think they're wrong.

      The best way for Free libraries to take over the world is to make them useful everywhere. Free applications will follow. Doing otherwise simply leads to extra work in the form of 3rd parties reimplementing the functionality of GPLed libraries with *BSD- or proprietary-licensed code.

  192. Other Distros by Artifakt · · Score: 1

    UserLinux can't possibly be the first distro to drop one of the two environments, can it? There are Linux distros that fit in 10 Mb (Dragon Linux, for one), or even on a pair of floppies, and others that come on 4 CDs. Surely somewhere in that range is a distro that decided to include only one of the two, KDE or Gnome?

    --
    Who is John Cabal?
  193. Free Software eclipsing shareware by tepples · · Score: 1

    If you need to invest $2000 to write an app you want to sell for $15, you won't even write the $15 app.

    For one thing, the point is to make it up in volume. For another, a typical developer's computer hardware itself probably cost four figures. Finally, if you need to invest sweat to write an app you want to sell for $15 but for which others are going to sell replacements for $0, you won't even write the $15 app.

    1. Re:Free Software eclipsing shareware by steveha · · Score: 1

      a typical developer's computer hardware itself probably cost four figures.

      So what? You can write useful software on Linux using a $200 computer from Wal-Mart, or a used computer. Some people get a computer free as a going-away-to-college gift.

      an app you want to sell for $15 but for which others are going to sell replacements for $0

      A well-written app for $15 will make a few bucks. Some people would be content with that. Even now, with lots of free software around, you can find people selling their own programs. All I really need or want is gFTP, but there are still a whole bunch of FTP applications for sale.

      Look, I guess you are comfortable with making sure that there will be no cottage industry associated with UserLinux. Bruce Perens isn't, and I agree with him. With Qt, you either get free software or else you get professional proprietary software, and nothing in-between. With GNOME, you can get the whole continuum between free and professional.

      Heck, I'll be happy if we get a few $15 shareware games for Linux out of this deal.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
  194. Usability - KDE is better by Anonymous Coward · · Score: 0

    While I think the default KDE is a bit raw compared to a default GNOME, the customizability of KDE allows distros to make it *very* usable. I'm a beta tester for Xandros Desktop 2, and with their base of KDE, they managed to make something far more usable than any version of GNOME I've found. It likely didn't take a large amount of work.

  195. Accessibility and KDE by arunkv · · Score: 1

    I didn't see any one else comment about this. Just today we learned that KDE has full accessibility support. Reading about accessibility in GNOME it definitely appears as if the KDE offering is much more comprehensive. (Please correct me if I'm reading this the wrong way.) Shouldn't accessibility support play an important part in the selection of a desktop?

    1. Re:Accessibility and KDE by fault0 · · Score: 1

      GNOME also has full accessibility support. What's exicting is that KDE and GNOME's accessibility is fully compatable with each other. Great step in the advancement of the UNIX desktop.

  196. I just don't like C++ by r6144 · · Score: 2
    Actually the C used in GTK is quite OO-ish. It looks similar to C++ code with Qt, except with longer function names (which is just some typing, doesn't matter much). Such C code looks almost as good as well-structure C++ code, while improperly structured C++ code (where relationships between classes are not very natural) can look absolutely horrible. There are some things that I really dislike about C++. There is just too many ways to do a certain thing. A simple structure can be manipulated by functions (C style), or you can encapsulate them in objects (can enjoy some C++ benefits but writing getters and setters are really not interesting). A method can be public, protected or private, where the boundary is not always easy to draw, espectially between protected and private if I haven't imagined any use for inheriting from that class (which is true in most cases). The other problem is that it is hard to extend some one else's class if they happen to miss a small bit of functionality because of access control, while in C you do have some quick-and-dirty choices. Although you have the choice of whether or not to use certain functionality in C++ such as access control, templates and RTTI, the decision is hard to make. Also, it is messy to mix STL stuff and custom String and List classes.

    Of course, all these problems can be addressed somewhat if you take enough time to architect the software carefully, it takes too much time for hobbyist-sized (several thousand lines) projects. Improperly architected C programs are not that far from good C programs (as long as good coding practices are used), but C++ programs will be very messy if some parts are put together ad hoc.

    For object-oriented programming, I prefer simpler languages such as Smalltalk, Java and C#, if they suit the job.

  197. Re:Perens is a Gnome Zealot(tm) by alienw · · Score: 1

    I guess you don't want commercial apps like Photoshop then for linux?

    Ah yes, Adobe will just LOVE the buggy, unstable, undocumented, and ugly GTK+ toolkit. They will really appreciate spending twice the time understanding, fixing and extending GTK than developing their software. All to save a measly $1k per Qt developer.

    You might as well suggest to them moving all their programmers to a crumbling, rat-infested condemned building that's missing a roof. After all, it would save on rent, no?

  198. Cough..well.. by msimm · · Score: 1

    You know it could be argued back and forth about which is 'better'. Gnome has some stong points too (like its 'open file' dialog). I like them both, but I find them about equally frustrating to use as a DE or a tool kit (I'm a Blackbox man).

    What I think is important is that the underlying standards get some serious attention, and I don't think it matters so much which DE is used to do this. I would definately say choosing *one* would be a very important first step.

    Once the standards have been hashed out why wouldn't KDE be able to use them? Linux based applications should be DE independant and I'm hoping this is the direction business will take us. In another 3 years I'd like to be able to use KDE with its fancy Karamba screen candy or the Slicker kicker replacement and have it work seamlessly with my favorite *Linux* applications. Down to the error dialogs and open file boxes. Someones going to have to step on some toes to make it happen, but I think in the end all camps win.

    So basic Windows style functionality might not be the final goal, but there are some basics I think we forgot about in our excitement (and our freedom). Sexy standards aren't, but I'll bet with a solid foundation we can really show our stuff!

    --
    Quack, quack.
  199. Read the mailing list. by benjamindees · · Score: 1

    If you read through the 'User'Linux list archives, you'll see that the way it happened was:

    1) Bruce released his whitepaper.

    2) People began discussing the possibility of a standard DE, including the benefits/downsides of each and the benefits/downsides of supporting both.

    3) *One* person stated that a $1500/year developer license for QT was cost-prohibitive.

    4) After a week of discussion, Bruce *declared* that Gnome would be the choice because of this undue burden on proprietary developers and that the discussion was "over".

    5) Lots of people pointed out that this only makes sense in comparison to the slave-wages of offshore development. They also pointed at the fact that KDE has a better IDE, better documentation, commercial support, and a larger developer following, even among commercial developers. Trolltech people said that they were willing to work with commercial developers who *seriously* couldn't afford their licensing fees.

    6) More than a few complained that Bruce was dictatorial in his decision.

    7) Bruce defended his decision by disclosing that, among his prospective clients, 4 out of 5 were leaning towards Gnome.

    8) The KDE proponents realized what was going on began to talk of a split.

    9) Most people generally realized that *users* had no bearing on 'User'Linux and talked of a name change.

    --
    "I assumed blithely that there were no elves out there in the darkness"
  200. Good choise Bruce by internet-redstar · · Score: 1
    Maybe my responce is a bit late for the slashdot reading people to notice, but I write it for you Bruce.

    Gnome is a good choice when you have to choose only one.
    KDE is with qt an interesting option when you want to create a simply ported multiplatform application with GUI. But if you look at the currently available important (from target population market share point) applications...
    You have to conclude that at this present moment most important Windows applications ARE NOT developed with qt and if they want to port to Linux, they have to choose a new GUI toolkit for their new 'Linux porting department' anyway.
    They have to choose for an entirely new GUI toolkit anyway!
    Would they choose for a crammy, not as widely used qt-toolkit with some commercial ties (to trolltech in one way or another - at least that's the perception). Or should they choose for an entirely free based, completely new GUI toolkit and different looking from Windows where they wanted to move from away?

    The answer is clear. And more importantly the result: all the new 'important' applications are written in GTK and not in QT. The KDE people have written perfectly good QT equivalents. Congratulations. But if you have to choose only one...

    It's only the GUI toolkit, not more...

    It's more efficient to target your programming differences into other fields! If you look at it from an efficienty point of view!
    So, ideally: the qt-designers should move forward to integrate the gtk toolkit into their own. Integration should be the ultimate proof that the OpenSource model works into a level which matches beyond the absurdity level of corporate software development.

    Probably I'm dreaming. And probably I used too much drugs...

    But what would happen if the KDE-core developer mailinglist and the core GLib mailinglist would suddenly merge into a new LinLib mailinglist....

    But I'm probably dreaming out loud...

    I would in any case send them a bottle of champaign to celebrate the move!

    By Jasper Nuyens.
    Founder Life - the linux company
    Former GM Europe Linux Services VA Linux Inc.
    CEO LinuxBe
    CEO LinSpot

    1. Re:Good choise Bruce by Anonymous Coward · · Score: 1, Interesting

      > But if you have to choose only one...

      But the problem is that UserLinux _isn't_ picking one. It's picking at least three: GTK (for GNOME), XUL (for Mozilla), and VCL (for OpenOffice). His reasoning seems broken at that point.

    2. Re:Good choise Bruce by Capt.+Beyond · · Score: 1

      since when is Qt not as widely used? Qt is shipped on the Sharp Zaurus. Qt is used by a number of heavyweights, including IBM, and Motorola smart phones.

      Opera web browser uses Qt.

      I have yet to hear about any strategic alliances between real businesses and gnome. and I can't buy any cool devices using gtk.

      --
      -- "Perceptions create reality. By changing your perceptions you change your reality."
  201. In 1 year none of this will matter. by Mustang+Matt · · Score: 1

    Amazing prediction. Call my pyschic.

    Both window managers are improving. Strike a point up for Gnome and let the game continue.

    --
    The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
  202. This does not matter by lpontiac · · Score: 1

    I develop on QT. My company has a commercial QT license, and we distribute an application on Win32 using QT.

    Qt is not supported by Microsoft. Qt is not supported by Windows. Windows doesn't come with Qt.

    This doesn't stop us from putting a Qt-based application on the Windows desktop, and UserLinux's choice of GNOME won't stop anyone from putting a Qt-based application on UserLinux.

  203. From a UserLinux Participant by Ashcrow · · Score: 1

    The UserLinux project is mainly about creating a standard distribution for clients and ISV's with standards. One thing that we can not do is support GNOME and KDE and a slew of apps in each without passing the support on to the projects themselves making a Enterprise Debian project useless. One of the misconceptions is that KDE won't work with UserLinux .... it will, but it will not be on the standard desktop installation. Any person can install KDE via apt-get or, if an ISV wishes, have it installed by default.

    The UserLinux project also is not going to be shipping with qmail, or exim, or sendmail, or bluecurve, or yast2, etc.. Unfortunately, a small few people have raised a major stink over the decision to use GNOME even though the majority of the list wanted GNOME. Those few also personally attacked Bruce saying that he picked GNOME because of pride which is a groundless and nonproductive attack.

    KDE is a great Desktop Environment, and no one is doign a thing to get it removed from Debian, but it is not shipping with UserLinux. If it's a problem to the clients, KDE will emerge.

    1. Re:From a UserLinux Participant by Anonymous Coward · · Score: 0

      > Unfortunately, a small few people have raised a major stink over the decision to use GNOME even though the majority of the list wanted GNOME.

      Hm. looking over the archives, I don't really see that the majority of the list wanted GNOME. There seemed to be a deadlock between supporters of either one, and Bruce picked the one he wanted, based mostly on license reasons. Which is fine, of course, it's his project, and he can set what projects are fine for whatever.

      Bruce also said that he expected to be flamed for his choice, which is expected, desktop environments I guess seem to be more holy war-rish than mail UAs or themes, for whatever reason. Probably because of the history of the KDE and GNOME projects in the first place.. massive mud throwing was performed between the projects back in 1997-1999 if you don't remember :-)

      I personally think that both KDE and GNOME are ill-adviced for such a project. Both are much more bloated than alternatives. Of course, that's my personal choice; I would have said KDE a year ago, GNOME two years ago, Enlightenment three years ago, and fvwm five years ago. I guess Bruce's choice varies as well! :)

    2. Re:From a UserLinux Participant by Anonymous Coward · · Score: 1, Informative

      "KDE is a great Desktop Environment, and no one is doign a thing to get it removed from Debian"

      Really? I'm sure everyone forgot the nearly two year period that KDE wasn't included in Debian.

      June 1998 - KDE removed from Debian. Thousands of unofficial apt sources crop up.
      September 2000 - KDE readded to Debian. People rejoice.

    3. Re:From a UserLinux Participant by Ashcrow · · Score: 1

      "Really? I'm sure everyone forgot the nearly two year period that KDE wasn't included in Debian."

      That obviosly has nothing to do with UserLinux or with a problem in Debian. During that time Qt was not open and it went against Debians ideals.

      To learn more about why KDE was taken out years ago read the Debian archives, or click here as Debian legal is a good place to start.

      I guess I should clarify my comment to avoid confusion. KDE is a great Desktop Environment, and no one from UserLinux is trying to get it removed from Debian.

  204. KDE and Gnome are for wimps anyway! by sheldon · · Score: 1

    If you really want to grok the true Unix experience, you use twm. tvtwm if you're feeling extra randy.

    Anything else is training wheels.

  205. Why not let the users decide what gui to be used? by Anonymous Coward · · Score: 0
    It's called "User Linux" so why not let the users decide which GUI they want? My suggestion:

    Include both

    Set up a poll and let users vote which one should be the preferred GUI.

  206. Preferring Photoshop by Fred_A · · Score: 2, Insightful

    The #1 reason people prefer Photoshop over the Gimp is that they already know how to use Photoshop and don't have a clue how to use the Gimp.

    The last time I used Photoshop was when it was an Apple only application. As a result I'm absolutely incapable of using it today while I'm fairly comfortable with the Gimp. So of course I prefer the Gimp. Most people reason the same way.

    Absolutely nothing to do with MDIs...

    --

    May contain traces of nut.
    Made from the freshest electrons.
  207. Where are your stats by Anonymous Coward · · Score: 0

    "In fact" or "in your head"?

  208. BETTER APPS. NO ARGUMENT by Ars-Fartsica · · Score: 1
    AbiWord and Gnumeric destroy their KDE counterparts.

    The Gimp has zero competition in KDE land.

    Mozilla/GTK2 destroys Konq (although this is arguable, maybe).

    KDevelop is the only app for KDE that I know of that kills its GNOME parallel.

  209. Choice between vision and scent by henrypijames · · Score: 1

    Obviously a lot of people, including Perens, are right about less choice being better in some respects. But in this specific case choice is actually not the issue. Why? Because Gnome and KDE are too different, so much that many people do not see them as "alternatives" to each other. There is actually no "choice" here.

    Why isn't there a discussion about a "choice" between Mozilla and wget? Because they obviously cannot replace each other, although a lot of what they do are common. Putting softwares into "categories" is the misleading step here, since it implies one program can do roughly the same thing as another one from the same category. But "roughly" is vage, and when programs grow in their complexity, they become more and more unique, unreplacable.

    Just by the amount of users defending KDE one can say that too many people don't feel Gnome is an alternative to KDE (although I'm personally not sure if KDE may indeed be an valid alternative for Gnome, if you consider the license fee for Qt to be negligible as I do). You cannot "choose" between two programs if they are not alternative to each other. It would be like choosing between vision and scent.

  210. GTK has numerous bindings, gtkmm for C++ by Ars-Fartsica · · Score: 1

    Why are you presuming that GNOME apps must be written in C?

  211. Obligatory K joke by Pinky3 · · Score: 1

    Itch? Scratch!

    Voila: KuserLinux!

  212. Tempest in a teapot by Anonymous Coward · · Score: 0

    Add Farsi support to GNOME or get another business model. From what I can see you are basically saying you want to pull in easy suport money but would prefer other people do the real work.

  213. I just cant agree with this by bflong · · Score: 3, Interesting

    I'm not really a developer. I've compiled and configured an entire network of free software, but I could not code "hello world" without looking at a "{programing language} for dummys" book to save my life. I've used Gnome 2.4. I used if for a month both at work and at home. At the end, I was *so* happy I could go back to KDE. KDE just works. Now. I couldn't even get printing to be uniform in Gnome. I wish OpenOffice and Mozilla would have the option to use KDE's dialogs, but at least I have a consistant printing system with kprinter. KDE is lightyears ahead of Gnome. Gnome has no consistancy whatsoever. Things don't mesh well at all. It feels like a bunch of parts just thrown together. I have dabbled in programing. I've thrown together little bits and pieces to see how they go together. Never really gotten anywhere simply becouse I don't like programing enough. However, I do know that if I ever wanted to make an app, I would use QT. And it wouldn't matter if I wanted to use the GPL or make it commercial. The fee for a commercial license is pocket change for a commercial project. I would be able to call TrollTech for support. I have easy to read documentation for every single funtion in QT. I have no one to call for gtk support. Also, I have the assurance that if TrollTech ever went under, I would have the QT code since they have agreed to release it under a BSD style licence if that were to happen.
    Here's a quick test using google seaches:
    QT toolkit Technical Support
    GTK toolkit Technical Support
    Now, if I were a comercial company, which toolkit would I want to use? One with full technical support, excelent documentation, and a contract that assures I'm never left without the code that costs money?
    Or a toolkit with no technical support, inferior documentation, no guarantee that development will continue thats free?
    Using Gnome for a distribution geared toward business is a bad idea. Mark my words: This will end badly, even if the distribution is successful.

    --
    Why is it so hot? Where am I going? What am I doing in this handbasket?
    1. Re:I just cant agree with this by vidarh · · Score: 1
      You miss the fact that using QT for proprietary apps means you'll have to pay, whereas that's not the case for Gnome. For most small or medium sized software companies that's no big deal.

      As for support, I'm sure you'd find hundreds of people who know Gnome ready to enter into a support contract with you, including a significant amout of companies.

    2. Re:I just cant agree with this by LMCBoy · · Score: 1

      You miss the fact that using QT for proprietary apps means you'll have to pay, whereas that's not the case for Gnome.

      You miss the part where you get what you pay for (clearly superior API, documentation, and tech support).

      For most small or medium sized software companies that's no big deal.

      Exactly! The Qt commercial license is pocket change for development companies. Glad you agree.

      --
      Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
  214. Never used your neighbor's stove did you? by bluGill · · Score: 1

    You obviously have never had opportunity to use a bunch of different stoves, because if you did you would soon notice that the user interface is terribal and requires reading the manual. Fortunatly the manual is printed right next to each knob, because otherwise there would be no way of knowing which knob controled what. On my stove the far left knob controls the left front burner, while on my mom's the far left knob controls the left back burner (or is it the other way around? I've lived here for 2 years and cook all the time yet I often mess this up).

  215. Lesstif/Motif SO binary compatibility by tepples · · Score: 1

    Will Lesstif apps transparently link to Motif libraries?

    Perhaps. From the FAQ:

    Compatibility can have several degrees, the ultimate one being binary compatibility. This is the one we're aiming for. This can be tested even today on most platforms on which shared libraries are supported : if you also have Motif(R) shared libraries, you can choose which library to use by setting an environment variable such as LD_LIBRARY_PATH prior to executing an application.
  216. Oh the irony... by achaudhary · · Score: 2, Insightful

    This is especially ironic considering the circumstances of the GNOME Project's foundation. Funny how GNOME is now being chosen since it is more 'accessible' to corporate developers because of its 'less Free' (in the spirit of Free software) nature as opposed to the GPLd KDE/Qt, while the initial argument against KDE/Qt was that it was non-Free and we needed a completely Free alternative. 'Lesser' GPL indeed.

  217. How many forum members does it take... by revividus · · Score: 1
    How many forum members does it takes to change a light bulb?

    1 to change the light bulb and to post that the light bulb has been changed
    14 to share similar experiences of changing light bulbs and how the light bulb could have been changed differently
    7 to caution about the dangers of changing light bulbs
    1 to move it to the Lighting section
    2 to argue then move it to the Electricals section
    7 to point out spelling/grammar errors in posts about changing light bulbs
    5 to flame the spell checkers
    3 to correct spelling/grammar flames
    6 to argue over whether it's "lightbulb" or "light bulb" ... another 6 to condemn those 6 as stupid
    2 industry professionals to inform the group that the proper term is "lamp"
    15 know-it-alls who claim they were in the industry, and that "light bulb" is perfectly correct
    19 to post that this forum is not about light bulbs and to please take this discussion to a lightbulb forum
    11 to defend the posting to this forum saying that we all use light bulbs and therefore the posts are relevant to this forum
    36 to debate which method of changing light bulbs is superior, where to buy the best light bulbs, what brand of light bulbs work best for this technique and what brands are faulty
    7 to post URL's where one can see examples of different light bulbs
    4 to post that the URL's were posted incorrectly and then post the corrected URL's
    3 to post about links they found from the URL's that are relevant to this group which makes light bulbs relevant to this group
    13 to link all posts to date, quote them in their entirety including all headers and signatures, and add "Me too"
    5 to post to the group that they will no longer post because they cannot handle the light bulb controversy
    4 to say "didn't we go through this already a short time ago?"
    13 to say "do a Google search on light bulbs before posting questions about light bulbs"
    1 forum lurker to respond to the original post 6 months from now and start it all over again.

    -------

    Heh. I didn't write it, it came from here.

  218. Mod parent up by Anonymous Coward · · Score: 0

    Mod parent up

  219. Wow, what INCREDIBLE irony. by mcg1969 · · Score: 5, Insightful

    So let me get this straight. From the very beginning, Qt and KDE has had non-free (beer) commercial licensing requirements; and initially it did was not considered free (libre) by Richard Stallman and GNU, at least until their licenses were modified.

    And it was precisely because of this non-free status that Mr. Stallman and other free software advocates heavily encouraged the development and use of GNOME over KDE, despite KDE's initial head start.

    And yet now we find that GNOME is the choice for UserLinux because it better supports the development of proprietary software on Linux!

    Oh excuse me, GNU/Linux.

    I get it!

    Actually don't get me wrong, I understand the logic, it's just a funny twist on an old rivalry.

    1. Re:Wow, what INCREDIBLE irony. by oconnorcjo · · Score: 1
      And it was precisely because of this non-free status that Mr. Stallman and other free software advocates heavily encouraged the development and use of GNOME over KDE, despite KDE's initial head start.

      And yet now we find that GNOME is the choice for UserLinux because it better supports the development of proprietary software on Linux!

      Actually it is still the same arguement which is that many in the open source community do not want to be dependant on the "goodwill" of one company alone (even if it is just for others to write "proprietary software"). TrollTech could be bought by Microsoft tommorow and a comercial license for Qt could go up to a $100,000 or more. It is one thing to prefer open source solutions and another to give up control of "comercial" potential. TrollTech controls key elements to "comercial development" on KDE.

      Of course I am personally biassed because I believe that "he who writes the code, chooses the license" and for that reason alone, KDE leaves a distaste in my mouth.

      --
      I miss the Karma Whores.
    2. Re:Wow, what INCREDIBLE irony. by Christ-on-a-bike · · Score: 1
      TrollTech controls key elements to "comercial development" on KDE.

      True but not strictly true. Using Qt GPL edition you can still sell your GPL'd apps. So commercial but not proprietary software can be made.

      I might be wrong, because Trolltech themselves are a bit confusing about it. But the GPL explicitly states that commercial selling is unrestricted.

  220. fluxbox is 0|\| teh 5p0k3! by oddtodd · · Score: 1

    i'm totally sold on teh flux, i'll never use Gnome again, unless i do :/

    --
    I have plenty of common sense, I just choose to ignore it. -- Calvin
  221. Why is everyone opposed to making a living? by hansreiser · · Score: 2, Insightful

    Maybe part of the reason KDE is better is because they manage to make some money. Taxing proprietary software when they want to take advantage of your labor so that THEY can make money seems pretty reasonable to me. If THEY can make money charging users license fees, why not KDE?

    1. Re:Why is everyone opposed to making a living? by Anonymous Coward · · Score: 0

      It's not KDE, it's Qt. And if TrollTech can make money from a KDE desktop... why can't Linux kernel contributors make money from forcing anyone building closed-source apps to pay a $3000 per developer. See where this is going?

  222. Enough already! by zalm · · Score: 1

    Go to your respective corners and take a time-out! KDE this!...Gnome that!... How about a compromise, Free User Linux for Gnome, and Commercial User Linux for KDE. List the advantages of each and let the developer and/or end user choose, they will anyway. Two different default distributions for two different markets. Now someone get me some aspirin :-)

    "We must be the change we wish to see in the world." Mahatma Gandhi

    --
    If at first you don't suceed, try RTFM or Man pages.
    1. Re:Enough already! by Capt.+Beyond · · Score: 1

      But you are mistaken. GNOME allows proprietary, non free non GPL applications. KDE does not. It is KDE that is really more free, and progresses Free Software.

      Using UserLinux that ships only GNOME, you will see more and more non free, closed source software.

      --
      -- "Perceptions create reality. By changing your perceptions you change your reality."
    2. Re:Enough already! by Graspee_Leemoor · · Score: 1

      "GNOME allows proprietary, non free non GPL applications.
      KDE does not.
      It is KDE that is really more free, and progresses Free Software."

      Reading that I think you've re-defined freedom. "Gnome allows ... KDE does not". Sounds like Gnome is more about the freedom to me.

      graspee

  223. Doing it the hard way. by BiggerIsBetter · · Score: 1

    Maybe if Ximian released a Debian version of XD2, all of this would just go away...

    --
    Forget thrust, drag, lift and weight. Airplanes fly because of money.
  224. Week's salary by benb · · Score: 1

    As mentioned before, that's what an external developer costs per week. I bet that the great Qt API, docs and tools save many weeks per year.

    1. Re:Week's salary by AstroDrabb · · Score: 1
      I do agree that the QT docs are very good and better then GTK+. Though saying that the API is great is a personal opinion. I personally don't think it is great and prefer wxWindows. By the way, wxWindows is FREE to use under MS Windows, Mac and Linux. I don't like the Meta Object compiler for QT required to do signals/slots. It is old cruft left over from the need for older C++ compilers. Gtkmm is a C++ toolkit for GTK that uses signals and slots and has no need for an aditional precompiler. According to QT's docs, there are a bunch of Limitations with QT's signal/slot implementation:

      class templates cannot have signals or slots

      Multiple inheritance requires QObject to be first

      Function pointers cannot be arguments to signals or slots

      Friend declarations cannot be placed in signals or slots sections

      Signals and slots cannot be upgraded

      Type macros Nested classes cannot be in the signals or slots sections nor have signals or slotsacros cannot be used for signal and slot parameters

      Constructors cannot be used in signals or slots sections
      www.wxwindows.org, IMO is better then QT and can be used to develop Open Source as well as closed source, propreitary applications. There is an impressive list of people using wxWindows including commercial companies such as AMD and Xerox who uses wxWindwos. The feature set is impressive as well.

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    2. Re:Week's salary by benb · · Score: 1

      > Though saying that the API is great is a personal
      > opinion. I personally don't think it is great and
      > prefer wxWindows.

      I was merely comparing with GTK+/glib. Qt is also not my fav toolkit.

      I like wxWindows in general, but from a quick look at the API, it looks awfully like Windows APIs. (I may be wrong, though)

    3. Re:Week's salary by benb · · Score: 1

      > wxWindows ... looks awfully like Windows APIs.
      > (I may be wrong, though)

      Seems like I wasn't:
      "Porting from MFC is particularly easy due to its similarity" wxWindows Intro.

  225. GNUStep... by Lord+of+the+Fries · · Score: 1

    ...was mentioned. This fascinated me. I thought it was below most's radar. Too bad UserLinux doesn't go with that. True GNUstep may not be as caught up as the other two, but it's vastly superior IMO. If they ever wanted to build anything that approximated OS X, GNUstep is the place not to start, not with the bloated Windows Knock Off known as KDE or the "we're all free, but we have no Human Factors direction" Gnome.

    --
    One man's pink plane is another man's blue plane.
    1. Re:GNUStep... by root+66 · · Score: 1

      I guess you meant: GNUstep IS the place to start.

      And you're right. Especially for business development GNUstep is superior. Why?
      Because it has a standardized API which does not change from release to release.

      With KDE and GNOME you have to rewrite your apps everytime a new major revision comes out...

      --
      -- I love the smell of Blue Screens in the morning.
  226. Not trying to flame, seriously. by Enahs · · Score: 3, Insightful
    I use KDE, but have used GNOME in the past. I like both, but at this time, I prefer KDE. In fact, no matter what I used, say, one and a half years ago, I have eventually ended up back with KDE.

    The only argument Perens makes that makes sense to me is that GTK+ can be used in a proprietary product without paying a licensing fee. Again, not trying to flame, but that more or less confirms that Bruce doesn't give a damn about Free Software. If he did, that wouldn't even be a point of contention for him.

    Seriously, why do we keep seeing these heavy-handed tactics to kill KDE long after the licensing issues have been resolved? Other than the possibility of holding a grudge (and though I can't find it now, I swear I saw an RMS essay about continuing to treat KDE as a GPL-violator) I can't understand it.

    You see, it's very simple. If you release your code under a GPL-compatible license and link against Qt, you're fine, since Qt is available under the GPL. If you want to release proprietary software, all you have to do is pay the licensing fee.

    I know; I know. Someone's going to argue "but what about Joe Shmoe who wants to sell a text editor? What if he doesn't have the two grand?" Well, then, he can do what any other startup does: borrow money, and pay back the loan when the money starts coming in.

    In no other business that I'm aware of is there the possibility of getting your tools for free, and then use those free tools to turn a profit. LGPL-using developers, you are aware, are you not, that your choice of license means that people are writing derivative works without giving back to you? You might as well be releasing your code under the BSD license (not a bad idea, IMHO, especially if you're not terribly interested in pursuing legal issues, though the BSD license isn't without strings, either.)

    Couple the barely-valid cost-of-licensing complaint with the fact that GNOME is currently in a state of flux, the choice of GNOME is iffy at best. Where have all the features gone, and after usability work is done, when will the features come back? Why is the default GNOME 2.4 CD ripper incapable of allowing me to set a default MP3/Ogg Vorbis bitrate? If it's because it's assumed that the average GNOME user would become confused, is it really safe to assume that the average GNOME user is stupider than the average MacOS user? iTunes, at least, allows for some tweaking of settings; they're just not right out in the forefront, and limited to only a couple of important features.

    I could go on for days, but to tell you the truth, had someone proposed this in the GNOME 2.0/2.2 days, I'd just have nodded my head; GNOME was a wee bit more bloated and had an ugly API, but if it became something of a standard, so be it. Now? Why are we burdening ourselves with this dumbed-down version of a UNIX desktop?

    --
    Stating on Slashdot that I like cheese since 1997.
    1. Re:Not trying to flame, seriously. by Anonymous Coward · · Score: 0
      The only argument Perens makes that makes sense to me is that GTK+ can be used in a proprietary product without paying a licensing fee. Again, not trying to flame, but that more or less confirms that Bruce doesn't give a damn about Free Software. If he did, that wouldn't even be a point of contention for him.

      This is a little much, considering that Perens defined the term you accuse him of not caring about.

      The Debian Free Software Guidelines (which he wrote) state very explicitly that you're not allowed to discriminate against classes of users based on whether they're proprietary or not.

      TrollTech just as explicitly charges a fee to develop commercially for Qt -- a fee which is not charged for open-source software. That's not a resolved issue, it's just an issue that people gloss over because they like KDE and don't like license flamefests.

      The problem is that the specific issue of desktops is a corner case of the GPL. Say that tomorrow a commercial developer decided to come out with a program of moderate complexity for the KDE desktop -- say an email client of about the same size/feature set as Evolution. That program "derives" from the KDE desktop only in the trivial sense of using its widgets, but TrollTech is still there to collect its fee.

      The problem you have with Perens isn't that he doesn't care about free software, it's that he does -- and managed to see the issue more clearly ten years ago than you do today.

  227. makes sense but by oohp · · Score: 1

    I think KDE has a too cluttered interface. In that sense Gnome looks cleaner. On the other hand, KDE is actually more usable, just that you get lost through the plethora of options. Oh yes and Nautilus is still tooooo sloooow.

  228. Re:KDE is not to be ignored (but vi is) by punkass · · Score: 1

    See, you just flawed your argument right there with your "Guiness in a bottle" quip. It's not natural, and neither is EMACS.

    --
    "Nobody owns the fucking words man." - James Dean
  229. Which company do you work for? by iamacat · · Score: 1

    And do they really let you order $2K software just because you say so? For me it takes several month to get "non-standard" software and if my purchase order has 4 digits it will likely be rejected. I tried to order $5K ARM BREW builder once and could never get any response.

    Maybe it makes sense for the company to license Qt, but it doesn't make sense for me, as an individual developer, to fight for it. Easier to just suck it up and write a Java UI with JNI plugins for the existing C++ code. This way I still get an application that runs everywhere, modern OO toolkit and a profusion of RAD tools.

    On the other hand, I would use LGPLed GTK+ if it was a nice programming interface. But both GTK+ and Qt suck compared to Cocoa.

  230. My $0.02 by mcrbids · · Score: 3, Insightful

    Well, it's late in the game, there are a million other comments, and if there were points I was after, this would not be the time or place to write.

    However, I feel I have to add my $0.02.

    I recently wrote a mid-sized application using PHP-GTK. Reasoning being that it was to be a semi web-based product, it would be best to leverage the PHP code on the client and server sides, and the GTK toolkit can be used to write the UI.

    It works well, and is achieving high acclaim in the marketplace in a way that the previous product based on VB simply didn't.

    That said, GTK 1.x, which was bound to PHP 4, is a horrible mess.

    1) Documentation is very spotty at best. I've at times had to query an object directly with get_class_methods() in order to find out what methods I can call, simply because there was no documentation for it.

    2) The widgets are terribly inconsistent. For example, GtkCList (a table of text values) doesn't contain child widgets, even though portions of the widget are selectable! Thus, you cannot use something like tooltips (which creates a popup yellow text widget when you hover over a widget) for anything but the whole table!

    3) Things that should be easy, like creating menus, are simply a pain in the rear.

    4) The API for GTK is transient - what works in 1.3 largely won't work in 2.0. Thus, when PHP5 is bound to GTK2 (which is the official plan, AFAIK) I know there will be a *huge* porting effort just to get the application to recompile.

    5) GTK objects don't have consistent means to access variables. Most of the time you use $object->Set_Data(). But, sometimes you use $object->Set_Row_Data(), or $object->Node_Set_Row_Data(). This is largely because of #2 above....

    So, does it work? Yeah. Was it the best available at the time given our resources and needs? Yeah.

    But there's a HELL of a lot of room for improvement. (I left a zillion notes in the online gtk.php.net documentation website as my contribution since I am not a c coder)

    --
    I have no problem with your religion until you decide it's reason to deprive others of the truth.
    1. Re:My $0.02 by _xeno_ · · Score: 1
      Here's a question for you: Are there any Qt bindings available for PHP?

      One of the impressions I've gotten between the two environments is that GTK+ being written in C means that it's easier to write language bindings for it in other languages. You don't need to worry about name mangling and the like, for the most part. Various other enivornments can more easily map directly to it since C dynamic libraries are better-defined than C++ created dynamic libraries.

      I'm not sure if this is still true, I found Qt bindings for Perl and Python in a quick Google search. But I'm not sure how mature they are. I know that three years ago when I wanted to write a GUI Perl app, I wound up using GTK+ bindings for Perl and that from what I've heard the various Mandrake tools are written for GTK+ because the Perl bindings were available and not the Qt bindings.

      Doesn't really matter to me, since I do mostly Java work under Windows. Although from briefly using the GTK+ toolkit, I can say without a doubt that it is one of the worst APIs I have ever touched. (Although I'm still debating about whether the Windows GUI API is worse. It's a toss-up.) The Perl bindings made it slightly easier to use, but trying to use it in C was just God-awful. I kind of hope it has changed since then. (Also didn't help that there was no documentation.)

      --
      You are in a maze of twisty little relative jumps, all alike.
  231. the obvious answer by ForsakenRegex · · Score: 1

    FVWM2

    --
    "A man talking sense to himself is no madder than a man talking nonsense not to himself."
  232. GTK "only" Apps in User Linux by Anonymous Coward · · Score: 0

    That will surely cure the cluttered menu problems people have been complaining about.

    Also, in light of the recent defections of certain distros who had previously claimed to be committed to FOSS principles. Then after using the community for beta testing, user input, and help with support. Once their distros got to a point where they think its close to final, stable code, they've gone "paid for" only.
    If I were a free code writer, I would filter my contributions to make sure this kind of thing won't happen in the future. Writing GTK only code, and moving toward Debian, would seem to work towards that end.

    "Fool me once, shame on you. Fool me twice, shame on me!"

    1. Re:GTK "only" Apps in User Linux by Elektroschock · · Score: 2, Insightful

      Troll. You cannot exclude qt based environments. This will never succeed.

  233. we must not progress! by t0ny · · Score: 1
    Heaven forbid they try to standardize on anything!

    --

    Manipulate the moderator system! Mod someone as "overrated" today.

  234. You know what? I certainly will! by Anonymous Coward · · Score: 0

    But it's still not nice to call that thing the "standard" distribution for enterprises and then exclude half of its potential users!

  235. No support... by Anonymous Coward · · Score: 0

    Well, guess what. I once bought Windows, think it was 98. Then I found a bug in MSIE. And I reported it. I got yoyoed around between the head office and the office of my home country. Nobody cared. There's no support there, either.

  236. Genuine concerns for the future of KDE by bizcoach · · Score: 1
    The KDE folks are cranky because they want the money that is to be spent promoting and developing UserLinux to be spent on their project and not on Gnome.

    No, there's absolutely no reason to think that such greed motivated their protest.

    First of all, they would wouldn't be working on KDE if they didn't believe in KDE. From this perspective, it's only natural if they think of KDE being the best choice.

    Secondly, they is reason for genuine concern about the future of KDE. As GNU/Linux becomes mainstream in the enterprise, very soon the vast majority of application development for GNU/Linux will be done by profit-oriented businesses. If all major "GNU/Linux for the enterprise" distros are focused on GNOME, it'll become very difficult for KDE to keep up. There used to be two major "GNU/Linux for the enterprise" distros, one with a focus on GNOME (Redhat) and one with focus on KDE (SuSE). Now with Novell having acquired both Ximian (so they're effectively leading GNOME now) and SuSE, chances are that the SuSE distro will switch to GNOME sooner or later. If also UserLinux decides to use GNOME, that might suffice in creating enough momentum to make GNOME the de-facto standard. When something is Free Software, and good enough for my needs, and it's the de-facto standard at my workplace, why would I want to use something different at home?

  237. A different angle on the controversy by njdj · · Score: 3, Insightful

    There are Gnome zealots and there are KDE zealots, and then there are the people who say, "They are both OK and neither is clearly better."

    At risk of losing all my karma, I have to say that I disagree with all of the above. Both Gnome and KDE suck. In a world which has seen Windows, both UIs seem half-finished. For the developer, KDE's API is unsatisfactory (see Al Stevens' articles in Dr Dobbs in Sept/Oct 2001 - AFAIK they're not on the web, unfortunately) for details. And actually Gnome's is too, because Gnome's base is in C, not C++. Development is bogged down by being based on an obsolete language. True, there is now a C++ API glued on top of Gnome, but it's exactly that, with the inefficiency implied.

    So we have two unsatisfactory UIs instead of one satisfactory UI. The quicker we pick one of them and run with it and fix it, the better.

    1. Re:A different angle on the controversy by vidarh · · Score: 2, Insightful

      Heh. Mentioning Windows and criticizing KDE and Gnome's API's in one paragraph without truckloads of sarcasm is quite impressive.

    2. Re:A different angle on the controversy by ptr2void · · Score: 1

      Criticize whatever you want, but the fact that GNOME has a C API actually is an advantage. C is the lowest common denominator. C is easy to wrap around (and thus to have C++, Python, whatever $LANGUAGE APIs). What inefficiency are you brabbling about? Numbers? Oh, you have none? Then shut up.

  238. This is quite frankly wrong by fozzmeister · · Score: 1

    Bruce Perens said he was going with GNOME from the off (Perhaps the customer who is funding the development wanted GNOME, I don't know). Then you get a load of KDE people screaming and shouting like stupid little kids, I read KDE's proposal to try and get in and it was very good, and also mature. however the decision was already made, Most of immature flamewar on the list has died down now, but you still get KDE people saying "I want to be able to RMB in XMMS and then it write a CD in K3B".

    Don't like the way this one is forming, Form your own, or just add bits of Debian to it (it's debian based)

  239. I for one.. by Soothh · · Score: 0

    FULLY support this choice to leave kde out.
    It's an excellent move.

    --
    We have seen that living things are too improbable and too beautifully "designed" to have come into existence by chance.
  240. Commercial Gtk Apps ??? by fritmebufstek · · Score: 1

    Have you ever actually seen a commercial Gtk app ? Because the world abounds with commercial Qt apps, like you can see here:
    http://www.trolltech.com/success/index.html

  241. Where is the GNOME enterprise vision? by DF5JT · · Score: 2, Insightful

    I very much appreciate Bruce Peren's activities and believe that we need people like him who want to promote Linux as a serious contender in the market of enterprise systems.

    Having said that, I was quite surprised to read Bruce's reply to the KDE-group. Nowhere does he address the real issue, which in this case is not the question of providing for another desktop solution, it is the question of providing for an enterprise Linux as a worthy contender to other "solutions" on an enterprise level.

    In that respect GNOME loses big time for the simple reason that no one in the GNOME foundation seems to have a clear vision of where their development is going, in particular with respect to these points:

    - Central administration of large scale desktop deployments
    - Enterprise level printing administration
    - Enterprise level Resource Planning

    and many others more which can be read in detail on http://desktop.kdenews.org/strategy.html

    KDE provides its user base with a clear and focussed vision of where enterprise Linux is going.

    Where are the GNOME visions in this regard? There are none.

    If UserLinux (What a bad name, it should be called Enterprise Linux or Debian Enterprise, whatever) wants to reach its intended audience, it has to provide a stringent concept for usability, scalability, support and enterprise features and commitment to care for the development.

    All of this is missing from GNOME and this makes the licensing argument rather moot.

    Either UserLinux wants to reach enterprises on a comprehensive level, in which case it has to provide for a framework enterprises need, or it wants to deploy some servers and some desktops without the technical merits of a real enterprise solution. The latter case is fine, if you want to show people that Linux is not bad and works fine in an enterprise environment.

    However, if we are talking real enterprise level, GNOME cannot come up with the necessary features and the long term vision to compete with the large solution vendors.

    As a technical salesman I would have a hard time making decision makers understand why the GNOME-UI is of real merit to their enterprise. The different licensing scheme is of only marginal interest for large scale deployments of a comprehensive framework.

    Given the KDE strategy and the nonexistence of such in GNOME, one can only wonder, why UserLinux thinks it will make a difference in the corporate world.

  242. wtf.. by Anonymous Coward · · Score: 0

    Why in the world is this modded to "+4, interesting"? Has Slashdot gone insane? Qt is released under the GPL, for $DEITY's sake. Just because Trolltech also licenses Qt under more restrictive and expensive terms for those who do not wisth to follow the terms of the GPL does not mean that Qt is not free.

    1. Re:wtf.. by Graspee_Leemoor · · Score: 1

      "for $DEITY's sake"

      If you were trying to cater to all people, you missed me. I don't believe there are deities, you insensitive clod. You could let me set $DEITY to "fuck" I suppose.

      Or if you were just trying to look geeky for the sake of it, then BLERG. Excuse me while I am sick.

      graspee

  243. Qt Licensing Myths by fritmebufstek · · Score: 1

    Hi, You should get your facts straight. First of all, there is no Qt license per installed user. The license is per developer using Qt per year. Secondly, if you search google, you'll find a hell of a lot more commercial Qt apps than commercial Gtk apps. This must mean that companies looking for a toolkit for their apps don't care about the money they'll have to pay. They are indeed willing and able to pay for quality software. Third, the Qt license encourages free software development. If companies want to keep their code proprietary, and sell their software, I don't see why they wouldn't be able to pay for that, especially given the quality of the Qt toolkit.

  244. it's the license by mattyp · · Score: 1

    it's the license, it's the license, it's the license. you didn't mention the license: KDE has no plan or vision for the license, except it's proprietary.

  245. Not expensive... by morzel · · Score: 1
    Choosing KDE would practically have forced the companies that want to ship closed source software to buy a expen$ive license for Qt
    A $1500 expenditure for a QT licence is not expensive at all... Compared with the development cost and the cost of commercializing the application it is peanuts.
    When companies want to have their own applications in-house (ie: not distributing the app to external parties), they just use the GPL. Whenever they have an application that they want to sell to third parties, the QT licence costs will probably be less than 1% of the total cost of developing the bloody thing. The licence cost is not an issue for 99.9% of the businesses out there.

    --
    Okay... I'll do the stupid things first, then you shy people follow.
    [Zappa]
  246. Bruce Linux by inc_x · · Score: 1

    Bruce Linux would be a better name to reflect clearly that this effort has little to do with Users or Community and everything to do with Bruce being able to cash in on his name.

    Ask Bruce about the companies that have promised him money to fuel this GNOME vs KDE flamewar.

  247. This seems as good a place as any.. by iantri · · Score: 3, Insightful
    ... to ask about the appearance of GNOME and KDE.

    As a desktop environment, I think KDE is better, but for applications, GTK based apps tend to be more mature, it seems. The included KDE apps (Konqueror, Kmail, and so on) seem unfinished and feature-lacking.

    I signifigantly prefer the look of GNOME to KDE, though. KDE's window decorations are about twice as tall as they should be, and Keramik is so god-damned ugly that it could blind a person.

    What I want to know is why, in KDE, can I not click one button (like in Gnome) to set ALL of the related styles? Unless I am missing something, in KDE you have to set the style and the colourscheme and some other things seperately, it is not grouped together as a 'theme' as in GNOME.

    Am I missing something here? Also, where can I find a nice, clean (not ugly) looking theme without over-large decorations for KDE? (I consider Windows 2000/XP to be a relatively decent looking in Windows Classic mode).

  248. Leadership by DuncanE · · Score: 0, Troll

    Bruce Perens has displayed excellent leadership here. Which is what many open source projects lack.

    I just dont understand why various comments try to defend KDE. QT has at its core a model that is not open. If you can accept this then why arn't you using OSX or Windows?

    The mailing list had a great discusion amongst some highly knowledgeable people on this topic and then the leader made "the right choice". It makes me thing that UserLinux may really be the desktop linux distribution it has set out to be.

    I dont why we feel we can comment at all really. But then I dont know why Im reading the comments either!... or why I'm making this post!!.... oooohhhh head .... exploding.....

  249. Shame but classic Perens by Performer+Guy · · Score: 2, Insightful

    This simply ingores the realities of making a useful distro.

    Many developers need KDE, plain and simple. Unfortunately it has caught hold, but that's because it is a well written functional GUI.

    The desktop is less of an issue but the current user base has it's preferences, for many developers it means userlinux will be ignored as a development platform I for one want a one stop distro I can use for development, ignoring key components means that for some it won't be UserLinux. The claims about downloading the components yourself is nonsense, the whole point of a distro is that you don't have to download the key packages separately.

    Yes the desktops and GUIs are complex, but that's the current situation. That these are large major components is a reason to include both, not ignore one, that's just crazy.

    When I first heard about Perens' plans I thought 'great' something to save us from RH's abandonment, but I had my concerns. Now it looks like I was right to, Perens has managed to stuff this up royally with one decision "by fiat".

    A lack of consensus should have told the guy something, but he completely ignored the message and is now claiming it doesn't restrict anyone supporting it themselves, rubbish! You could make ths same case about Fedora.

  250. Why so much trouble?? by GNUALMAFUERTE · · Score: 0

    This is not Propietary Software, this is GNU.
    And here we do things really different. If m$ says "We will remove this feature" lusers using m$s abominations has only two options: Keep the old version and keep the feature, or upgrade and loose the feature. But here, if you don't like the GUI that cames with that distro, just download and compile!, i don't see the trouble. As is said in the article: "Applications from KDE and GNOME run reasonably well together today", so you will be able to run the soft and specific config tools and stuff that comes with the distro from your hand-added KDE. Even, if you don't know how to compile KDE or just feel lazy, i am sure that someone will make a binary KDE pack for that distro, or even that an rpm, deb, tgz or whatever package made for other distro that uses the same glibc should work just fine. Besides, even if they don't include KDE; they should include QT Librarys, since there are lots of apps, many of them not KDE specific, that relys on them.

    --
    WTF am I doing replying to an AC at 5 A.M on a Friday night?
  251. Windowmaker! by Anonymous Coward · · Score: 0

    Really, why don't you KDE users admit that GNOME is just cooler? I mean, we've got a foot as our logo, and all you have is a fuckin' letter K? That is soooo weak!

  252. Work together eh? by SmallFurryCreature · · Score: 1
    Well by that reasoning the KDE developers should just accept that this has happened and get over it. Spend a month learning gnome and make that better. It happened recently when Linus choose one virtual disk system over the other.

    Instead all I see is a lot of KDE users bitching that they rule and gnome is the sucks. Having read all the links in the post I think Bruce Perens is the adult here. He has a very difficult project to do that so far noone else has come even close to accomplising. A standard linux.

    Is it needed? Well maybe. I use gentoo so have the choice of 2 dozen desktops/windows managers. I can deal with it. I don't really like either Gnome or KDE. HOWEVER I am not a big business looking at the choice between Microsofts windows, Suns Java Desktop, Mac OS X or Userlinux. Now tell me. How many desktops do the first three have? Good. Now tell me how many desktop should the last one have?

    I think Bruce Perens is making the right choice to limit the default install to 1 desktop. I even think the choice for gnome is a good one. The KDE letter is crap as it completly fails to address the issue Mr Perens has with KDE. The license for qt.

    However userlinux coming with gnome does not exclude KDE from being used with it. Nothing will stop the KDE team, least of all Bruce himself according to his post, from making their own debian packages to install KDE with Userlinux.

    Anyway I think my sig really says it best. KDE vs Gnome arguments are totally pointless and the only thing I will tell all the KDE posters, please try to back up your arguments. I seen to many posts saying "KDE is better" without any evidence. No doubt if this was a story about gnome losing gnome users would do the same and it would be just as meaningless.

    Oh and as a side note. I use virtual desktops to seperate my activities. KDE allows different backgrounds making it easy to identify where I am. However gnome is far faster in updating my transparant windows (yes I am graphics whore) but has only 1 wallpaper. Make of that what you will.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

  253. Different group of posters. by SmallFurryCreature · · Score: 1
    The 1 program to bind them all are windows users who either are trying to prove windows is better for having no choice. Or windows users that want to turn linux into windows.

    The posters today are mostly KDE users most of who can't read or just can't understand why someone does not choose their obviously superior desktop, it is ofcourse so obvious that no ones needs to link to any evidence.

    So your comment is incorrect. Different people are allowed to have different ideas you know even if they post on the same forum :)

    Oh and you might notice that most of the "KDE is better, bruce is a moron, gnome sucks" posts don't mention the license issue or get it totally wrong.

    Of course there are exceptions and it is those that still make it worthwhile to read all the way to the bottom.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

  254. When you mess around with shady people by Anonymous Coward · · Score: 0

    you don't have to wonder when your image goes down the drain. Right thing for Troll Tech would be to separate from Canopy and SCO. As long as Canopy has a seat in Troll Tech's BoD, TT's image will be hurt.

    Separating from Canopy will send a message to the industry.

  255. KDE phreaks dont get it. by Anonymous Coward · · Score: 0

    KDE phreaks will wiggle and whine but the bottom line is that Darl McBride's boss, Ralph Yarro, sits on the Trolltech Board of Directors.

    KDE users must pressure Trolltech to get with program and resist SCO and Canopy. It means voting them off of the Trolltech board. Only KDE Zealots waking up and smelling the coffee and giving some grief to Trolltech will make the take action.

    KDE Zealots denial in this situation is NOT helpful.

  256. Re:UserLinux == Great Idea (not!) by chundo · · Score: 1

    And I'll never use RedHat. Ain't choice great?

    Perens doesn't have the ability to dictate the direction of open source. But he does have the prerogative to make his own decisions for his own company ideas. If you don't like it - I fail to see why he should care.

    The fact is, to gain widespread acceptance, he had to standardize. That means choosing one desktop - as many have said, there are very few casual users who care what a "desktop environment" is. They just want a computer. He chose GNOME. Had he chosen KDE, we would have seen just as much outrage from GNOME users.

    You may not agree with the choices, but if his idea works, it will greatly increase the acceptance of desktop linux. And that will perhaps open doors for another user-oriented linux distro that is KDE-centric. In any case, it will benefit the entire community in the long run, so we would all do well to support his efforts.

    -j

    Disclaimer: I have no favorites. I use both GNOME and KDE daily.

  257. Non inclusion of KDE by Anonymous Coward · · Score: 0

    This is one distro that I will not buy if I know at the
    outset that the only window manager available will
    be the Gnome. Most distros include several
    window managers, including the ICEwm and
    Enlightenment as well as KDE. I know that Gnome
    has a long history going back into the late 80's in
    the old century, but the developers did not solve
    some of its irritants. For one thing, there is the idea
    of icon placement on the desktop. I have distros
    using Gnome that don't seem to be able to see all
    the hard drive partitions, or duplicate them again
    and again. Madeningly, the duplicates can't be
    erased without root use....sigh..n out and go back
    in as root...may as well toot....more and more icon
    duplicates appear and when you try to get rid of them ...oh boy....your linux x server crashes! This problem
    was repeatable as well. Some later versions seem
    to have ameliorated this somewhat, but there are
    other irritants. You have to double click on the icons
    just like windows. You cannot get rid of pop-ups
    or cookies or javascript or other mal ware in the
    nautilus browser. X(s)imian is just like naughtylust
    in this regard; it leaves you open to victimization
    just like you were a window$$ computer.
    Are you sure that ole bill gates isnt funding
    gnome to use its foot to stamp out linux independence and computing freedom from
    unwanted spam?!

  258. KDE is superior because... by MrNerdHair · · Score: 1

    ...It's shiny!

    (No, really, KDE is shinier. Every new user I've talked to as a tech has preferred KDE because it's more shiny.)

  259. Ximian threat by G3ckoG33k · · Score: 1

    Isn't Gnome's own, independent, development near being trifled since Ximian took on? And, then, where does Ximian lead us for Free Desktops?

    See this:

    The suggested retail price is $99 (U.S.)

    In addition to the Bitstream fonts bundled with GNOME 2.2, Ximian Desktop 2 includes MS-Windows compatible fonts from AGFA*, so your applications, documents and web pages look their best. AGFA fonts available only with Ximian Professional Edition - Buy it now!

    Access virtually all print, media, audio and video web content with the bundled Adobe Acrobat Reader, Real Audio Real Player, Macromedia Flash Player 6, and Java 2 Run-time Environment. Available only with Ximian Professional Edition - Buy it now!

    In my view there are a lot of "By it now"s, being based on a "free desktop". When did a Windows user pay for Acrobat Reader, Real Audio Real Player, or Macromedia Flash Player 6; apart from the fancy versions?

    Where is the incentive in opening the gates for Ximian hell here?! Who is duped? Perens?! Aren't Ximian just like any other money drainer?! To me, it sure looks like that. But, as always, I may be wrong again...

    Adobe payed for using Qt and they can probably afford it. How many Mexicans can afford Miguel de Icaza's Ximian? 99$ for a desktop(!) with Acrobat Reader, Real Player, and Flash Player?!

    How many Mexicans can afford Miguel de Icaza's Ximian, apart from Miguel himself?

    Here are some brave words:
    "Ximian is offering a complete, low-cost productivity solution for Linux."
    Mike Rogers, VP and General Manager
    Desktop and Office Productivity Software
    Sun Microsystems

    Hrmmmm... Somehow, my thoughts are in the direction that this LGPL talk is a setup for giving Ximian a get-go start harvesting all the multimillion dollar berries. But, I may be as wrong as many a time before.

    Yes, sure: ftp://ftp.ximian.com/pub/xd2/redhat-9-i386. But, the one who has the copyright on the code does set the agenda to a large extent, and that may be what all this is about.

    I have no idea who is pushing the LGPL agenda besides Perens, but Ximian seems to me being a likely candidate. Maybe, I should RTFA... ;)

  260. try 1.3 by Ender+Ryan · · Score: 1
    Give Gimp 1.3 a try. It's the development version, but it is pretty stable. The interface is much nicer.

    Opinions about GTK

    --
    Sticking feathers up your butt does not make you a chicken - Tyler Durden
  261. woops... by Ender+Ryan · · Score: 1

    Opinions about GTK

    --
    Sticking feathers up your butt does not make you a chicken - Tyler Durden
  262. /me tries one more time... by Ender+Ryan · · Score: 1
    goddammit...

    Opinions about GTK < 2.x and Gimp < 1.3.x are pretty much worthless at this point.

    --
    Sticking feathers up your butt does not make you a chicken - Tyler Durden
    1. Re:/me tries one more time... by KewlPC · · Score: 1

      1)The last time I tried GIMP 1.3 it didn't have (or I couldn't find) a curves tool. This automatically renders it a non-contender.

      2)While better than GTK 1.x, GTK 2.x still sucks.

    2. Re:/me tries one more time... by Anonymous Coward · · Score: 0

      1)The last time I tried GIMP 1.3 it didn't have (or I couldn't find) a curves tool. This automatically renders it a non-contender.

      You know, these sorts of conversations always annoy me. Let's attempt to sort this one out.

      For starters, I use the Gimp once in a while. In the past, I have used Photoshop once in a while. I'm not an "expert" in the tool. So, if I can find this feature easily, I think anyone can.

      First, I wasn't sure what photoshop's "curves" tool was you were referring to. Was it a bezier curve tool? A gamma curve tool? A tool for tracing the curvy nature of naked women's bodies? I wasn't sure. So, I googled for it. Aha, it's a gamma curve tool.

      Now, I start up gimp-1.3. Now, I load up an image. Now we're cooking.

      So, now let's see if there's a curves tool. Now, I have used the Gimp in the past, so I know that the convenient way to get to everything is by right clicking. But, I'll play dumb. Really dumb. I go to the Gimp main window and pull down the window.

      Let's see...

      File->Dialogs...

      Hmm... Layers, Channels, Paths, ... Not there.

      Wait, "Tools"

      I select Tools.

      This gives me a big list of tools. Let's see...

      Rotate... Blah blah blah paint... Shear... Levels... Curves. Well, lookit that. OMG, there is a curves tool.

      Well, that was astonishingly hard wasn't it. Must have taken me ten seconds. Let's see how you do it in the regular popup menu...

      Lesse...

      Tools->Color Tools->Curves

      OMG, nobody could possibly find that!

      Did you use it for more than 5 seconds? What? Hmm, how do you find it in Photoshop? Let me check that google page again... Image->Adjust->Curves.

      You know, "Color Tools" sounds a bit more understandable to me. But then maybe I just don't have the mind of a Photoshop weenie. Or maybe you were mad that "CTRL-m" in the gimp brings up the "Merge Layers" dialog, and not the so much more intuitive Photoshop "Curves" dialog? Because, there's definitely an "m" somewhere in "Curves"

      Of course, since GTK2 sucks so bad, it must be impossible to set the keyboard shortcut to be the same as Photoshop. Er, oh wait, all I have to do is turn "Dynamic Keyboard Shortcuts" back on (funny, that used to be on all the time in GTK1 - I guess it scared people), and then just bring up the menu, put the pointer on "Curves" and hit CTRL-m. OMFG does GTK suck!

      Whatever.

    3. Re:/me tries one more time... by KewlPC · · Score: 1

      You're right. There is, in fact, a color curves editor in GIMP 1.3.x. I didn't think to look under the Tools->Color Tools menu. Chalk that one up to stupidity.

      The rest of my arguments remain valid, however. GTK 2.x sucks, it just sucks less than GTK 1.x. GIMP 1.3.x's GUI still sucks, it just sucks less than GIMP 1.2.x.

    4. Re:/me tries one more time... by Ender+Ryan · · Score: 1
      GTK 2.x sucks, it just sucks less than GTK 1.x. GIMP 1.3.x's GUI still sucks, it just sucks less than GIMP 1.2.x.

      Would you care to substantiate that a little bit more? What exactly makes them suck.

      Previously you trashed GIMP because of the interface - yet in newer versions all your arguments against the interface have been addressed. There is a menu for each image window, much saner menu layout - granted, it still sucks that the windows are still independent(ie. bring one to the front doesn't bring them all to the front - however, i just use GIMP on a separate desktop, as *nix nerds are wont to do). MDI is a mis-feature in many peoples' opinion, and if you want MDI, I assume you also think Photoshop on Mac sucks. Just saying it sucks is pretty offensive to those that have done so much work on it. Saying it sucks compared to Photoshop would be true, however. The GIMP is great for people who don't quite need everything Photoshop has.

      And I have no idea why anyone says GTK 2.x sucks, especially when comparing it to QT. GTK 2.x has had much better font support than QT 3, and it has been far more stable. QT 3.x had problems with Xft2 and fontconfig for a long while, and in many cases was quite unstable. Also from a user standpoint, GTK 2.x is *much* "cleaner" looking; much more attention is payed to details like positioning text in widgets properly, whereas with QT text is often positioned flush on one border. From a developer standpoint, I like that I can use GTK 2.x, with all its new features, with plain vanilla C. I also like that I can use it for proprietary development without spending over $2k. I have a game project in the works, which I'll probably never make money on(I'm 99% certain of that), so I can't afford to use QT.

      Also, I think it'd be a shame if the community did ever standardize on QT, as QT is owned by one single company that holds the key to any proprietary development. Not that I really care too much about proprietary software... just that that could slow adoption of Linux, and/or one company would reap all the benefits of all proprietary development for Linux.

      Heh, I'm done blabbing :) I'm interested to hear why you think GTK 2 sucks.

      --
      Sticking feathers up your butt does not make you a chicken - Tyler Durden
  263. au contraire, mon frere by Anonymous Coward · · Score: 0

    The *are* partners. Ralph Yarro, leader of Canopy, is on the Trolltech Board of Directors !!!!

    Major Partner if you ask me.

    The sad moderation in this thread is the Pro-KDE zealots who refuse to deal with the truth.

    It's like you can't handle it.

  264. Re:Don't dodge the issue / Non issue by ingenuus · · Score: 1

    The cost of a license for commercial development is not a valid argument. If a company develops an application for sale, the cost of a license is a fraction of the overall cost to develop, market, and maintain a product.

    I disagree:

    1) Trolltech has to make a profit. The only way their product can be cheaper than creating it yourself is if they have a large enough userbase (as compared to your projected userbase) to account for their profit and then some.

    2) UserLinux is not being created by a single company, nor for a single product. It is being created by a consortium for many products. IMHO, it is likely that the per-company expense is greater to maintain perpetual Qt licenses than to share in the improvement of a pre-existing solution.

    That said, quality is also a key issue. If Qt is truly technically superior to GTK+ (and GTK+ is too damaged to "fix"), perhaps it would be in the consortium's best interest to buy Trolltech outright, re-licensing the code as they see fit.

  265. Re:Don't dodge the issue / Non issue by phug · · Score: 1

    The cost of a license for commercial development is not a valid argument.

    Doch! Perhaps not for large software companies, but for small time developers, a free SDK is obviously a huge plus.

  266. Try saving the planet some time (n/t) by Christ-on-a-bike · · Score: 1

    n/t

    1. Re:Try saving the planet some time (n/t) by advocate_one · · Score: 1
      try running that comment past me again... I live in a cold climate... the heat from the computers contributes to my heating budget for my flat... saves me from putting other sources of heat on.

      Oh and I've got stuff in use that most ms-windows users would have tossed out into the skip long ago cos the latest and greatest from One Redmond Way ran like a sloth on it... so the energy/raw materials/resources used to manufacture the components in my machines is not wasted in a landfill. My way is a heck of a lot greener that that of those users locked into the constant upgrade cycle to keep their stuff running at a usable speed with ms-windows latest and greatest versions...

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
  267. bzzt, wrong :P by Christ-on-a-bike · · Score: 1
    If you give something away, you give it away for good.

    You give beggars money to buy crack?

  268. KDE is DEAD!!!! by Anonymous Coward · · Score: 0

    KDE is better than GNOME. I know. But does it matters?

    What matters is that KDE and QT were created and is owned (I'm mean mainly designed and developed) by european developers. GNOME is owned by USA developers.

    Remember: Suse was bought by Novell (an american company).

    I guess the americans companies are telling Bruce Perens they want to use a framework developed by americans and for americans (cynical slant added). Why? Imagine those companies trying to sell an application/system to the USA government and telling them its based on a foreign framework written by people who opposed the IRAQ invasion (cynical slant added again).

  269. Just a few KDE's significant advantages: by Moritz+Moeller+-+Her · · Score: 1

    Hmm, just a few things I miss in GNOME, whenever I try it.

    Is written in an OO-language. Fewer developers achieve more. Consistency is much easier to achieve in KDE than in GNOME.

    kwin is much more powerful than metacity.

    kioslaves are used everywhere.

    All relevant apps are scriptable using DCOP. You can control KDE from a bash prompt.

    Toolkit is faster and available commercially but natively for MacOsX and Win32.

    Much better integration of all applications.

    Has a scanning framework for all apps (kooka).

    Has an extremely powerful and helpful printing system on top of CUPS (and also lpr,...) kdeprint rules. It is easier to add (network, usb, parallel, port) printers in KDE than in Windows.

    Has a desktop wide encryption scheme used by all KDE apps.

    Has a desktop wide addressbook used consistently by all KDE apps.

    Has a GUI to configure all details of the desktop.

    Every single feature can be locked, overridden and set centrally for users using the incredible KIOSK system. Don't want users to change the background? Lock the settings. It's easier than changing the bash prompt.

    --
    Moritz
  270. Maybe I'm missing the point by Anonymous Coward · · Score: 0

    But really, who cares? Isn't this just one of way too many distributions getting stuck up the old Slashdot "arguing over licenses" backwater?

    If you absolutely, positively have to stick with whatever comes supplied with one distribution (KDE is laughably easy to install from source) move to one of the thousand or so distributions that include it, and shut up.

    Really, get a grip and start doing something instead of just warming over the stupid "QT isn't free as in speech" argument for the millionth time.

    I like everything about linux except the pathetic infighting.

  271. More free -- for whom? by steveha · · Score: 1

    Richard Stallman is all about freedom for the users. He likes the GPL because it guarantees that the users will always have source code -- he despises proprietary code because the users don't get the source.

    Thus the GPL has the restriction that you must release the source to your code if your code uses GPL'ed stuff. This restriction does not make GPL code more free, but is intended to promote free code.

    BSD-licensed code is almost completely free of restrictions... but that means there is nothing in the BSD license to compel people to share their code. Some people claim that BSD is the "most free" license since it has the fewest restrictions; others feel that GPL is "most free" since it compels the free release of source code.

    So, if you want to help promote the free software ethos, GPL is the best choice. If you are interested in preserving options for the authors of software, you might choose another license, such as LGPL or even BSD.

    Even RMS admits that there are times when LGPL is appropriate, which is why he created it. I agree with Bruce Perens that LGPL libraries are better for UserLinux. I would love to see the "cottage industry" of small shareware programs that Bruce Perens has talked about. (And no doubt some of thse shareware programs will in time be released as free, GPL software.)

    steveha

    --
    lf(1): it's like ls(1) but sorts filenames by extension, tersely
  272. What a bummer by Sunnan · · Score: 1

    Trix are for kids.

    Commercialism breeds lies, perhaps? Or just competition.

    I still which the two camps could just merge.