Slashdot Mirror


Qt Going GPL

summer was the first to note that it looks like Qt 2.2 will be released under the GPL. This removes the licensing problem that is central to the age old (and very boring) KDE/GNOME flamewar. There's still nothing official appearing on Troll Tech's site, but this looks reasonable.

268 comments

  1. Re:Another GPL victim... by Nerds · · Score: 1

    Why does *every* OSS need to be GPL? I thought OSS was about *freedom*, freedom of choice.

    Stop confusing the Open Source movement with the Free Software movement, there is a difference.

    --
    My other .sig is 'The Art of Computer Programming'
  2. Re:GPL not LGPL by Phill+Hugo · · Score: 1

    Not by halves. Free as is Free for everyone.

    The "Free but for a price you can have non Free" isn't quite on the money, don't you think. If it were 100% GPL and nothing else, that'd be another matter.

  3. Quality and Freedom - What could be better? by neurocrat · · Score: 2

    This is the best tech news I have heard all year.

    Like every other developer in my acquaintance, I believe QT stands head and shoulders above the competition in terms of its technical merit. It is one of a very few libraries that is beautifully designed, combining elegance, efficiency and full support for reusable components.

    I believe even those who are strongly committed to the principles of Free Software (as defined by FSF) have long been enamoured with QT's high quality - but until now we/they have been prepared to forgo its benefits for the sake of Free Software ethics. At last, the release of QT under the GPL will relieve many a frustration for those of us who believe in the ethics of Free Software, but also want the highest quality tools available. This is truly excellent news!

    Although I wish Gnome all the best (two high quality desktop environments can harm nobody), I strongly believe that QT and KDE (esp KParts) offer a much more technicaly sound platform for developers to build the fast and robust desktop systems of the future.

    With KDE2 we'll have a visually appealing and functionally useful desktop environment. We'll have a web browser that has much better potential than Mozilla. But best of all, for developers, we've now got an advanced (but easy to learn and use) component architecture, a high quality free GUI toolkit, visual GUI development tools, language bindings for Python - and now we've got a community of talented AND committed people who can use all of this without reservations or uncertainties. For mine, this is almost too good to be true. The best technology is now free to win, and I sincerely hope it does.

    Great work Trolls.

    --
    ---- Ends are ape-chosen; only the means are man's.
    1. Re:Quality and Freedom - What could be better? by frantzdb · · Score: 2
      I strongly believe that QT and KDE (esp KParts) offer a much more technicaly sound platform...

      In what way is KParts especally superior to Bonobo?
  4. Re:dept: its-about-frigging-time by asmussen · · Score: 1

    Let's say instead then that it's going 'Free Software', which is not the same as 'Open Source', which has unfortunately obfuscated the free software movement.

    --
    Shawn Asmussen
  5. Re:That's just your sick imagination by nchip · · Score: 2

    It uses viral effect to protect our software (Yes, our, not your or mine), by being viral. You can modify/extend/embrace GPL'd code, but the result will always be GPL'd. So you can't hide GPL'd code inside propierty code. (Unfortunatly, this hasn't been court tested yeat.)

    What I ment to say, is that GPL's viral effect is a good thing, and we have just seen another victory of it. QT is brilliant piece of code, a fact that has been overseen while we have been fighting over the licences.

    --
    signatures pending - ansa@kos.to - (dont mail there)
  6. Re:Now GNOME code can be copied to KDE! by Kenelson · · Score: 1
    Quick note. The Gtk+ C++ bindings are called gtkmm and are included in GNOME. The Redhat project called Inti is to create a C++ framework and is not at this time part of GNOME. Neither Inti nor gtkmm can copy Qt code, because you may not shift the license from GPL to LGPL without permission. Also as both the C++ bindings have more modern implementations than Qt, the bulk of Qt code wouldn't be all that much use.

    --Karl

  7. Re:Porting QT/Unix by Per+Abrahamsen · · Score: 2

    I don't know a lot of this stuff, but the "easy" port would be to Cygwin + Xlib, and using one of the existing win32 X servers. I doubt this would compete with Troll Techs own native Win32 port.

    If you want to make a native win32 port of Qt Free Edition, Cygwin would probably not be of help.

  8. Re:yay by johnnyb · · Score: 1

    Have you ever tried to use C++ for object-oriented development? It's a piece of crap. It takes more time to work around C++'s idiosyncrasies than it does to do the same stuff in C. Also, GNOME _is_ object-oriented. Yes, you _can_ do OO stuff in C. In fact, writing a library in C++ is terribly stupid, because there is no binary compatibility specifications. Having the library in C and a C++ wrapper is a much, much better solution. If you want a better language than C, go with Objective C. C++ definitely sucks as far as OO goes.

  9. Too late? by dwalsh · · Score: 1

    Now that Qt is GPL'd Sun can do what I said they should in my previous post and switch to KDE.

    --
    ${YEAR+1} is going to be the year of Linux on the desktop!
    1. Re:Too late? by MarkHewitt · · Score: 1

      If Sun were to adopt KDE with QT under GPL they would prevent commercial application development on Sun Solaris which is not their intention (I expect). They would have to negotiate a license for QT commerical edition and ship a copy of that with each Solaris license, if they wish to allow commercial application development on solaris. Alright they would get huge discounts because of the volume they ship, but it would still impact on the cost of a Solaris license.

  10. Re:How long before KDE/(QT 2.2) will be out? by Nerds · · Score: 1

    I guess we might be up to the next Debian release before a "completely un-QPL-dependent" KDE is released - anybody know more about timescales?

    Yeah, the end of this month. KDE2 is based on Qt 2.2, which is officially released under the GPL now. KDE2 was written with the beta versions, so it's ready to go.

    --
    My other .sig is 'The Art of Computer Programming'
  11. Re:My e-mail to TrollTech. by Znork · · Score: 1

    The QPL has always been 'opensource', the problem has been that it wasnt GPL compatible, rendering KDE undistributable together with Qt. Changing it to the GPL changes very little for Troll Tech, it just makes KDE entirely OK from a licensing point of view (just the two points of disclosing internal source code to Troll Tech and distributing changes to Qt as patches).

    Most of gnome (as in almost all libraries) is under LGPL.

    You wont likely see any flamewar between GPL and LGPL 'supporters', because there is no real rift there, they're good for different things.

    Of course, GNOME with its LGPL infrastructure will be more palatable for proprietary developers, but then it always has been.

  12. Re:yay by Field+Marshall+Stack · · Score: 1
    C is deeply integrated with UNIX and POSIX. C++ is not. Your claim that if the kernel had been developed in C++ it would be more robust is quite ridiculous. That would turn out to be something like BeOS, which has completely different project goals from Linux. Linux is a Minix clone. Minix was written in C. End of discussion.
    Actually, IIRC BeOS's kernel itself isn't written in C++ either.


    --
    "HORSE."

    --
    "HORSE."
    -Flaming Carrot
  13. Re:Bad news for C coders and Ada coders. by mw · · Score: 1

    I don't know about ADA, but for C there are bindings, still a bit older. Porting should be easy and will probably done by interested people

  14. Re:Nothing Changes by Znork · · Score: 1

    If they already want to use KDE (not to mention Linux) as the foundation for their applications, how likely are they to want/care about commercial support of one library? The model only works for developers using only Qt, who could concievably have an interest in commercial support.

  15. Re:yay by lubricated · · Score: 1


    yes, why don't you retire your obsolete enlghitenment code base. It is written in that obsolete language of C.

    jackass

    --
    It has been statistically shown that helmets increase the risk of head injury.
  16. Good going TrollTech by Ur@eus · · Score: 2

    It is nice to see that TrollTech finally comes around and GPL's Qt. Thumbs up to TrollTech for this move.

  17. Re:If this is true... by decaf_dude · · Score: 1

    I think this may be the best thing to have happened to Linux desktop development. Now the choice between the two best desktop environemts will be solely on quality, not ideology.

    Who knows what might have happened if this decision was made just a month earlier (wrt GNOME Foundation)

    Thank you, Troll Tech! You have just done what nobody could have done to push Linux further on the road to desktop domination.


    -----

  18. wohoo! by abelsson · · Score: 1

    Sorry, contentfree post ahead. Please disregard. (most sensible ppl read at +2, so this shouldn't bother too many)

    I just have to add my wohoo!! to the crowd. this rocks! [/me dances a happy little dance around his box]. Qt is a very nice toolkit, and *finally* all the licensing gripes are gone! It seems to me most of the OSS community spends far to much time griping over licenses instead of coding. Imagine if all the time and energy spent depating licenses had been put to good use coding.

    Again: Wohoo!! Qt rocks! Trolltech rocks! KDE Rocks! (Gnome rocks too - just slightly less, today.)

    -henrik

  19. Re:Oh, DEBIAN GOOD! by tolonuga · · Score: 1

    It was possible for debian to include the kde libs
    and other stuff since kde 1.0 beta 3.

    for the libraries, there was never ever any issue.
    so, why didnt debian include kde ?
    and why should they do now ?

    i have no reason to think, they ever will.

  20. gnome is language-neutral by mattdm · · Score: 3
    Sure, most of the gnome core is C. But the whole environment is designed to be language neutral -- you can write Gnome applications in Python, or Perl, or whatever.

    --

  21. If the flamewar's boring... by chadfowler · · Score: 1

    Why do you always a) mention it and b) report on it.

    1. Re:If the flamewar's boring... by sluggie · · Score: 1

      Sorry I'm pretty new to this (in terms of writing comments, not in terms of reading), so I was really excited when I had the chance to make the first post. I apologize for this , and will not do it again. Sorry

  22. Re:Too little too late by Macka · · Score: 1


    What do you mean catch up? KDE is still 12 months ahead of Gnome on the development front, and has a much bigger user base. You're basing your statements on marketing rhetoric from the Gnome spin-meisters instead of looking at the facts.

    Macka

  23. If this is true... by MartinG · · Score: 2

    .. then it is fantastic news.

    At last these two great products, GNOME and KDE can compete on their merits alone. That's surely in everyone's interest.

    --
    -- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz .@adgimnoprstu
  24. Re:We have a level playing field by Me2v · · Score: 1
    You are incorrect. Gnome libraries (i.e., the stuff you link against to make nifty applications) are not GPL. They are LGPL. This means I can compile a commercial app against Gnome libraries (and gtk+, et al), and release my app under whatever license I please, because LGPL does not try to limit people/companies in this respect.

    IMNSHO, Qt should either be LGPL, or it should be for-profit. What the Qt team is doing with their licensing fiasco serves only to confuse developers and obfuscate the situation. "Hmm, which version of Qt should I link with today". With GNOME, you always know where you stand. With Qt, it's a mystery.

    I don't mind commercial software, or paying for a license to use libraries. And Qt is definitely a decent package. But Trolltech needs to decide one or the other how they want their libraries used--for profit totally, or always under a free license (i.e., never charging for it).

    Besides which, more relevant to this issue, the license has never prevented GNOME and KDE from going head to head, based on performance, appearance, and ease of development and use.

    --
    Matthew Vanecek For 93 million miles, there is nothing between the sun and my shadow except me. I'm always getting i
  25. Re:Except Qt is copylefted. by bockman · · Score: 4
    QT Professional Licence costs are not a big issue for proprietary development, since the cost of one developer for a few days covers more than enough for it. So all Trolltech shall do is to convince managers that they can reduce work costs choosing QT over alternative free-as-in-beer toolkits.

    IMO, big companies will still prefer GTK+, however, because they wouldn't like depending on Trolltech for strategic issues like a GUI toolkit.

    --
    Ciao

    ----

    FB

  26. dept: its-about-frigging-time by Karma+Sucks · · Score: 5

    Good attitude, Commander. Troll Tech should be praised and thanked for bending backwards and forwards for the community like this. We really do not need your snide remarks here. Will GPL'ed Qt improve KDE acceptance by the community? I certainly hope so. I've always been a KDE fan and user regardless. Now I hope that KDE can compete with GNOME on purely technical grounds and not depend on who can shout louder in the PR wars.

    --
    (Please browse at -1 to read this comment.)
    1. Re:dept: its-about-frigging-time by PiMan · · Score: 3

      Qt has, since 2.0, been Free Software and Open Source. The issue is not Qt alone, it's that KDE and Qt's licenses are seen to be incompatible.

      Unfortunately, a significant number of people have obfuscated the issue to say Qt is not free, which unfortunately hurts the free software and open source movements.

      --
      Windows 2000: Designed for the Internet. The Internet: Designed for UNIX.
    2. Re:dept: its-about-frigging-time by HarpMan · · Score: 1

      "KDE and Qt's licenses are seen to be incompatible."

      Soon that will be "were seent to be incompatible",
      since they'll both be GPL. Yeah!

      --
      Stephen Molitor steve_molitor@yahoo.com
    3. Re:dept: its-about-frigging-time by GrafZahl · · Score: 3

      Even more so: Is this not a prove that commercial interests and pressure can lead to an Open Source Development?

      To me it seems that Troll Tech will take this step because they see that some big commercial players have decided to go Gnome rather than KDE for the reason of being Open Source.

      The good and right reaction is to go Open Source as well. Because 'proprietary' pieces of software will in the long term not be able to compete with OSS.

      So let's celebrate this as a success fpr Open Source!

      May the best Desktop Manager win!!!!

      Graf Zahl

    4. Re:dept: its-about-frigging-time by Karma+Sucks · · Score: 1

      Qt has been Open Source for how many years now already? Don't believe what you hear.

      --
      (Please browse at -1 to read this comment.)
    5. Re:dept: its-about-frigging-time by On+Lawn · · Score: 2

      I think the issue is rather `Non-Threatening' rather than `Free'. Its been free for many uses since it became noticed by the community many years ago. The real fear however is just that it threatens our guild socialism, are community values and sharing system. But its pretty darn ego-centric to say what we consider freedom(tm) is truely freedom.

    6. Re:dept: its-about-frigging-time by pblanton · · Score: 1
      The problem with KDE acceptance was originally the license issues with QT. Those issues have already largely been removed.

      I have been using both Gnome and KDE for about two years now and my personal opinion is that KDE is by far a superior product. Where Gnome is one big kluge, KDE is thoughtfully designed and expertly developed from object oriented C++ as opposed to procedural C. As a developer, I would much rather write for KDE than for Gnome.

      KDE's charter was to create an excellent desktop environment for Linux. Gnome's charter was to be a "KDE Killer." Although I understand the desire to kill that which you don't like, the product that was spawned from this vitriolic hatred toward all things proprietary is not what I would consider the best design possible.

      Don't get me wrong, I like the fact that I have a myriad of desktop environments to choose from, I just feel that until the Gnome folks get their head screwed on straight, they will be too focused on killing KDE instead of on creating a robust, user friendly desktop environment. Many of you will go on and on about choice when it comes to MS vs. other OS's but when it comes down to Gnome vs. KDE, you spout off about how KDE is evil and must die.

      And that's the most ridiculous item of the day.


      With Regards,

      Phillip H. Blanton

  27. Re:Nothing Changes by Znork · · Score: 1

    You're wrong. The gripe in the free software community has been that KDE had a serious license problem since the QPL wasnt compatible with the GPL, which KDE is licensed under, effectively preventing KDE to be distributed together with Qt.

    That Qt cant be used in a proprietary fashion without paying TrollTech is another matter entirely and not in any way a problem or anything to gripe about. Of course, it likely means that KDE wont be accepted by proprietary software makers as a standard, but there is no problem from a free software point of view.

  28. Re:QT/Unix only by gorgonite · · Score: 1

    I don't care about this particular caveat. You give Bill cash for Windows and whine about paying the trolls? You support Windows by porting programs to windows and whine about things being nonfree? Come on.

  29. Trolls by tooth · · Score: 3
    Does this mean that people trolling in the KDE vs GNOME posts will have to get a bit more imaginative? Gawd, I hope so...

    Well, I guess we're going to be forced to rate each one on it's merits now. What a strange concept! It feels... kinky :)

  30. QPL is still an option by Per+Abrahamsen · · Score: 2

    which mean you can release your software under any free software license you want.

    If you want to make your software unfree, you won't get Qt for free either. Basically, you choose the rules (free or non-free), and they will apply to both your software and Qt. What you cannot choose, is to play by different rules for Qt and your own software. Somehow, this fair to me.

    1. Re:QPL is still an option by be-fan · · Score: 2

      So, basically, GPL is freedom with provisos?

      --
      A deep unwavering belief is a sure sign you're missing something...
  31. Re:We have a level playing field by Chalst · · Score: 2
    Not quite identical: GTK+ is LGPL, and I think this may be preferable
    to many corporate developers. There is of cource the anti-competitive
    advantage of GPL to corporate developers: it can't find itself in a
    commercial offering by a rival.

    I have to say the whole QPL vs. GPL spat has me disillusioned with
    the GPL: the GPL doesn't just ensure that it can only find itself in
    free software (no-one disputed that the QPL license guarantees this),
    it also ensures that it can only find itself in software that conforms
    exactly to RMS's conception of free software. This reeks of
    ideological intolerance, though I suppose one shouldn't expect
    anything else of RMS.

  32. Oh, DEBIAN GOOD! by Lonesmurf · · Score: 2

    The obvious and immediate repercussions of this is that Debian will be able to include an option for KDE now that the liscensing issues with QT being non-free are solved.

    Excellent.

    Rami
    --

    1. Re:Oh, DEBIAN GOOD! by xelah · · Score: 3
      When QT becomes GPL, KDE won't be able to be put in debian only because of this. Before this can be done, any program has to fully under the GPL or fully under QPL.

      I don't think that's true. You can quite easily have a program which uses Qt (under the QPL), an LGPL library (eg, the KDE libraries) and is itself licenced under a variety of other possible licences (eg BSD, GPL with exception caluse for linking to Qt, etc) and remain definitely legal.

      Programs which main-code is qpl and using libraries under gpl are still illegal, until the program itself is gpl.

      Such programs might infringe the GPL author's copyright, so there may indeed be a problem if he chose to sue. Assuming, that is, that dynamic linking produces a 'derived work' which I personally don't think is true. Since the only significant code out there under the QPL is Qt which is now dual licenced I don't think this is a problem anyway...

      KDE itself is a mixture of licences. The libraries are LGPL, so you can link a BSD licenced program to the KDE libraries and Qt with no problems. Much of the rest of KDE is GPL with some portions BSD licenced. Since anything which is BSD licenced satisifies the conditions of the GPL (in fact, the BSD licence is such that I believe you can relicence code under the GPL (or a closed source licence) if you want to) that doesn't present a problem either.

      There shouldn't now be any problem with Debian including all of KDE now, as far as I can see. Previously there was no problem with including KDE libraries anyway, but they didn't all the same.

    2. Re:Oh, DEBIAN GOOD! by bockman · · Score: 1

      Now the KDE project should be able to claim this money.

      --
      Ciao

      ----

      FB

    3. Re:Oh, DEBIAN GOOD! by nosh · · Score: 1

      When QT becomes GPL, KDE won't be able to be put in debian only because of this. Before this can be done, any program has to fully under the GPL or
      fully under QPL.

      Programs which main-code is qpl and using libraries under gpl are still illegal, until
      the program itself is gpl. And changing a licence of a program with more than one or two developers
      last many time. (If it can ever be done)

    4. Re:Oh, DEBIAN GOOD! by cjwatson · · Score: 1

      No, it's OK. Qt 2.2 will be dual-licensed, so you have the option of using either the QPL or the GPL, depending on whether your licence was QPL- or GPL-compatible. See the first paragraph of the announcement.

    5. Re:Oh, DEBIAN GOOD! by cjwatson · · Score: 1
      As soon as Qt 2.2 appears, it'll be rock-solid legal as far as debian-legal's concerned. Debian's ftpmasters won't argue with something that can be completely GPLed, at the risk of being laughed at. :)

      Given that, it only takes one interested Debian developer. There's no grand strategic plan about what to include and what not to include, beyond the DFSG. As far as I know, simply nobody could be bothered to deal with kdelibs while the rest of the KDE flamewar was up in the air.

      Anyway, Krusty (the guy who's been running kde.tdyc.com) has already uploaded a kdesupport source package to Debian incoming.

    6. Re:Oh, DEBIAN GOOD! by uhlmann · · Score: 1

      KDE was always licensed under the GPL.
      Now KDE 2.0 will be linked to the GPLed Qt 2.2
      So there is no non-GPL code in any KDE 2.0 program.

  33. Story is now on the Trolltech page. by Anonymous Coward · · Score: 1

    Story is now on www.trolltech.com

  34. ...then kill it. by yerricde · · Score: 1

    Because the flamewar has finally died down to epsilon (BSD vs. Linux; both are Free) levels.
    <O
    ( \
    XGNOME vs. KDE: the game!

    --
    Will I retire or break 10K?
  35. Re:My e-mail to TrollTech. by clacke · · Score: 1
    RMS would be pleased indeed if they released it exclusively under the GPL. Since there is an alternative license allowing closed source he probably doesn't give a flying rat's ass about TT choosing GPL over LGPL.

    Like so many others have commented, if you use QT22 in your program you can either open up or pay. Not very evangelistic, just plain old financial interests.

  36. Re:Doesn't solve all the problems by Abreu · · Score: 1
    Now, the KDE libraries are LGPL, but if Qt is GPLed, that makes no difference. Anyone who wants to write non-free software in KDE will still have to pay for the Qt Professional License.
    Otherwise the whole lot will have to be GPLed, or released under a GPL compatible license.

    True, but as it has been stated above, the price of the pro edition of qt is insignificant if you are serious on making a closed-source app with the intention of making money.

    If you think about it, with this arrangement everybody wins: Trolltech, KDE, independent developers (both closed and open), and especially users...

    --
    No sig for the moment.
  37. Re:Not _JUST_ GPL. LGPL still prefered by Enahs · · Score: 1

    /*
    Its a risky, but perhaps rewarding move for Troll. On the bad side (from their view) the GPL base would permit a better, seperately
    maintained
    variant with GPL code they cannot add to their commercial option - it wouldn't be all their code at that point.
    */

    Absolutely true. They'll run into the same problem the Harmony project ran into: how do you incorporate changes without being sued? They'll have to have someone write e spec for the coders.

    --
    Stating on Slashdot that I like cheese since 1997.
  38. Re:GPL not LGPL by Enahs · · Score: 1

    As long as they add a clause to the GPL, it'll be fine.

    If you believe the folks at Debian, that is.

    --
    Stating on Slashdot that I like cheese since 1997.
  39. Professional Edition by ivan4th · · Score: 1

    So what Trolls are going to do with their Qt Professional Edition, including Windows version? It seems that it will become completely separate product now, as there will be no easy way to keep it in sync with GPL'd Free Edition. Even APIs may become different.

    1. Re:Professional Edition by Captain+Pillbug · · Score: 1

      It's becoming positioned as a development environment, and you still need to buy it if you want to deploy QT apps on Windows (for now, until someone ports the free edition) or use QT in proprietary apps.

  40. Re:If it ain't broke, don't fix it! by Chris+Johnson · · Score: 2
    Ironically, if in this case they _did_, it would have better survival value.

    Just a thought...

  41. Re:GPL not LGPL by update() · · Score: 1
    Going for the full GPL pleases the extremists, but it also has the side effect of allowing Troll Tech to protect their revenue stream.

    At least I hope so. On the one hand, I'm thrilled to see this news because I really want to see Qt and KDE rise or fall on their technical merits. (Is that going to happen? Not likely, IMHO. Troll Tech has already moved to a certified free license, and it's still one of the arch-villains of the English-speaking free software world. The new GPL vs. LGPL issue is shaping up to be the next round of FUD.)

    On the other hand, Troll Tech deserves to make money. They have a superb toolkit, and equally superb developer tools, documentation and tutorials. I'd hate to see them forced into unprofitability to keep pace with the dubious business plans of their media-darling competitors.

    ---------

  42. Re:MODERATORS: sucked in by reverse psychology! by jilles · · Score: 1

    I think any post containing the words moderate, moderator or moderation should be marked as offtopic automatically. Now karma-whoring is something of the past since you can't get your karma above 50 anyway (I'm at 113 now, down from 114). Personally, I think that's a pitty since it removes a reward for posting insightfull or interesting posts.

    In any case, when I said "and now for some flamebait", I fully realized that with the licensing issues out of the way, the next topic for the flame wars will be technical differences between gnome and KDE. One notable difference is the use of C in Gnome and the use of C++ in KDE. Hence my remark.

    BTW. If you don't agree, feel free to risk your karma by adding to the discussion (which is why we have a moderation system in the first place). Also I'm in favor of a separate, thus on topic thread about moderation and how it can be improved. Particularly the way new threads are initiated is very much open to discussion IMHO.

    Since I feel that this reply is a bit off topic (not entirely) I have toggled the no score checkbox which you forgot to do.

    --

    Jilles
  43. Re:Red Hat covets non-free software? by Per+Abrahamsen · · Score: 2

    It wasn't meant as an attack on Red Hat, I believe attracting unfree software is good for Linux. For example, it means I can play some cool games under Linux, which would probably not be released under a free software license.

    Using the LGPL rather than the GPL for key libraries, is one way to attract unfree software.

  44. Re:Reasons from GPLing from the authors by Znork · · Score: 1

    Very interesting article. If they've changed their opinion on what the GPL says do they agree with Debians analysis on the distributability of KDE together with QPL Qt now?

  45. Re:NT isn't C++ by phutureboy · · Score: 1

    Actually, the original NT kernel was written in Pascal

    MacOS was at one time written in Pascal also. I was programming in C then, and all the interfaces and examples in the Inside Macintosh references were for Pascal. If the 8,000 redundant API functions didn't get you... the Pascal calling conventions would. Drove me nuts.



    --
  46. Re:Another GPL victim... by Pinball+Wizard · · Score: 2
    Not speaking for any other software, but I feel TrollTech did this at the right time, and for the right reason. I was just thinking the other day that in all likelihood, KDE would die if it did not change to 100% GPL software. With IBM, Red Hat, Sun, and others recently supporting GNOME primarily because it was GPL'd, it would be only a matter of time until they built up GNOME to the point that it would make KDE irrelevant.

    The QT framework was the only thing making KDE not qualify for being GPL'd, since it was proprietary software.

    QT has several advantages over the GTK - it is written in object-oriented C++, and the libraries are cross-platform between UNIX and Windows. IMHO, if you want to build a cross-platform GUI in C++, QT is the best way to go. Supposedly it offers better Windows support than MFC, although I haven't confirmed this myself. However, it was becoming unpopular with Linux developers because it wasn't GPL'd, and having all the industry giants unite behind GNOME looked like the kiss of death for KDE and QT development on Linux.

    My hat is off to TrollTech. Now I can feel comfortable using QT, knowing it will be around for years to come because of their wise decision to GPL the code.

    --

    No, Thursday's out. How about never - is never good for you?

  47. Re:Too little too late by Boolean · · Score: 1

    The user base doesn't matter for crap. It matters what the industry thinks. Looks like they're embracing GNOME and not KDE. Therefore, the user base will grow. The same thing is happening in the *nix vs MS debackle, companies are starting to realize which the better product is, embracing it, therefore the user base increases.

    IMHO KDE and GNOME are tools to interface more cleanly with your computer. Both are excellent products. In the 'one man's trash is another's treasure' view, different people want different things. This may not be a very business oriented statement, but if the companies are going for the OSS philosophy, they should allow the other to co-exist without arguement so that there will always be a choice. Neither KDE nor GNOME should be obliterated, therefore taking away the choice, therefore going against the OSS philsophy, and in kind shedding bad light on OSS. When people read that the OSS philosophy is about choice, then see flamewars like these pop up, it can not look good in the public eye.



    If you think you know what the hell is going on you're probably full of shit. -- Robert Anton Wilson

    --

    If you think you know what the hell is going on you're probably full of shit. -- Robert Anton Wilson
    jdube is who
  48. Yeah! by jlg · · Score: 1
    And there was much rejoicing.

    It's inspiring that the GPL is becoming the standard license for companies who release free software. This is great news because it removes a lot of the complications for users and developers.

    Thanks Troll Tech! I look forward to finally using KDE!

  49. Re:QT/Unix only by doctorwes · · Score: 1

    For those wishing to develop cross-platform applications, wxWindows and wxPython have been around for a long time. Much better than trying to use GTK on Windows (wxWindows uses GTK on Linux but the MS common controls on Windows).

  50. Re:Nothing Changes by Wolfkin · · Score: 1
    They GPLed it not LGPLed. Which is funny because it is a library.

    The "L" in LGPL no longer stands for "Library", but instead for "Lesser".

    If you want to wrote a closed source app you still have to pay Troll Tech!

    And this is as it should be: if you want to restrict the liberty of others, you have your own freedom restricted. Turn about is fair play.

    But I just don't want everyone who is writting for linux to be forced to pay these guys money.

    People writing freed code will not be forced to pay anyone; only those who restrict the freedom of users will need to pay, in turn. This seems appropriate, no?

    Randall.

    --
    Property law should use #'EQ, not #'EQUAL.
  51. Re:yay by jilles · · Score: 2

    Great idea, but i need a window manager and I figured enlightenment is as good as any other. In any case I wouldn't consider linux or any unix for doing desktop work anyway. I love linux as a server OS but have no use for it as a desktop OS.

    However, the release frequency seems to confirm you are right about enlightenment being obsolete.

    --

    Jilles
  52. Re:Debian by gorgonite · · Score: 1

    Yes, but only i386, as far as I can tell. I tried to compile kde2 on am alpha and failed because of the idl compiler segfault problem, which is a closed bug, but it looks like its only closed on i386. Therefore I would love to see kde2 in Debian.

  53. No, no, no! by Captain+Pillbug · · Score: 1

    As long as he doesn't distribute any modifications he makes to have it run on Windows, he isn't violating the GPL. And even then, he could release patches, as long as he doesn't distribute them with the original code. There's no bloody question about it. He could link against his ass if he wanted, as long as he didn't share it with others.

  54. Re:GPL vs LGPL by aanantha · · Score: 1

    You pay nothing to write proprietary code with LGPL'd stuff. So how is LGPL less fair? Both are "fair", it's just a question of how free they want to make it. GNOME charges no one, while Qt charges non-open-source developers. It's a choice. It remains to be seen if this choice has an impact on their success.

  55. Re:Another GPL victim... by PiMan · · Score: 1

    A license cannot be totalitarianist; you can either follow it, or not. A license cannot maliciously hurt you, nor can it make a decision to remove your rights.

    People are totalitarianist. People can make concious decisions to hurt you. However, no one's standing with a knife at your throat insisting that you license your software under the GPL.

    --
    Windows 2000: Designed for the Internet. The Internet: Designed for UNIX.
  56. Re:KDE is already GPL. by xelah · · Score: 1
    ne advantage of GPL over QPL is it's hydra-headedness.. you could kill Qt before by putting Troll out of business.. but now Qt is immortal.

    Not true. From the Free Qt Foundation announcement:

    Should Troll Tech ever discontinue the Qt Free Edition for any reason including, but not limited to, a buy-out of Troll Tech, a merger or bankruptcy, the latest version of the Qt Free Edition will be released under the BSD license. Furthermore, should Troll Tech cease continued development of Qt, as assessed by a majority of the KDE Free Qt Foundation, and not release a new version at least every 12 months, the Foundation has the right to release the Qt Free Edition under the BSD License.
  57. Re:yay by Skeezix · · Score: 2

    GNOME is indeed very object oriented. What do you think the 'O' stands for in GNOME? I get very tired of people claiming that you cannot do OOP in C. It is just completely false.
    ----

  58. Re:yay by jilles · · Score: 2

    What is obsolete is the fact that it is written in C and not in C++. More specific, it is not object oriented (as are most desktop applications these days) and probably includes some cumbersome mechanisms to make it appear object oriented to the outside world. In my opinion this has to lead to maintenance problems. In the open source world this means that perfectly good developers are spending time on maintaining a project that they could also have spent on other projects.

    Now about the linux kernel. If it had been developed in C++ from the beginning, it would probably have moved past the point the current linux kernel is at. Rearchitecting it now is probably not feasible. I wouldn't be surprised, though, if a C++ kernel took over in the future.

    --

    Jilles
  59. Re:Geez! Can we please kiss and make up already! by Bruce+Perens · · Score: 3
    I am not apoligizing for waving the red flag. It needed to be waved and the result has been excellent. When you ask people to make changes, and they make them, it's right to say thank-you and cease hostilities. What I am objecting to is that people who don't even understand what is going on have continued to fight long after the fight is over.

    Bruce

  60. Need major player to back KDE by rngadam · · Score: 1

    I've always been a fan of the quality and stability behind KDE and the license has never been an issue for me.

    But I understand why it is one for others and TrollTech changed the license too late.

    Sun and HP backing Gnome changes the whole balance and it is now HIGHLY probable that GNOME will be the _corporate_ standard (which will of course ripple thru home usage).

    The only thing that could counter this would be for IBM or another big player to "adopt" KDE has their official GUI. I doubt it however: IBM will probably switch to GNOME across their Unix product line very soon...

  61. Re:Left it a little late. by hexix · · Score: 1

    That is the most idiotic thing I've heard in a while. Trolltech's success deals a very very large amount on KDE's. Whos going to be writing programs with QT if KDE goes under? Trolltech knows that if KDE is on most linux desktops then commercial companies wanting to write closed source programs will probably want to choose KDE for more users, and hence will have to pay for the commercial license. Whos going to buy a commercial license to develop with QT if GNOME is more popular?

  62. Re:GPL by netinlet · · Score: 1

    Because if it were LGPL'd, I could take the QT lib, port it over to windows and write proprietary software (as long as I relases my QT enhancements)

    This ensures TrollTech that companies will come to them for the Windows QT library for proprietary products.

    --Doug

  63. Re:I don't think so. by jpowers · · Score: 2

    I think shareware culture is something we can live without in linux-community.

    Don't toss shareware aside so casually, especially in reference to games. First Person Shooters pretty much owe their current popularity to the shareware Wolfenstein, and the next wave (whatever it is) could come from anywhere.

    -jpowers

    --

    -jpowers
  64. Clean C++? by Anomolous+Cowturd · · Score: 1

    The license flamewars have fizzled out, but new battle lines have already been drawn.

    C versus C++ isn't much of a war, people. C is a clean procedural language, C++ is a dirty OO language.

    The only thing going for C++, when you think about it, is easy compatibility with C. That's all that stopped it losing to a cleaner OO language like Eiffel.

    --
    Software patents delenda est.
    1. Re:Clean C++? by xelah · · Score: 2
      C versus C++ isn't much of a war, people. C is a clean procedural language, C++ is a dirty OO language.

      The only thing going for C++, when you think about it, is easy compatibility with C. That's all that stopped it losing to a cleaner OO language like Eiffel.

      It is a bit of a pity that open source projects have tended to ignore higher level languages and stick rigidly to C... C++ is at least a bit better, especially if you have a need to work at a low level sometimes.

      Compatibility is always going to be an issue, though. There is a huge body of free C code out there which projects such as KDE draw on heavily (consider, for instance, OpenSSL, libjpeg, libpng and xdm). It's possible to write bindings for other languages, like the Qt bindings for Python, say, but that barrier is always going to be there and there's no guarantee that the bindings will always be well maintained, up to date or clean when the main project doesn't have the language as one of its priorities.

      Finally, I'd far rather have OO code written as cleanly as possible in a 'dirty' OO language like C++ than have OO code written as cleanly as possible (ie, not very cleanly at all) in C. I've always found trying to write OO C to be a somewhat painful and messy experience.
  65. Re:NT isn't C++ by Slothrup · · Score: 2
    Actually, the original NT kernel was written in Pascal.

    This is just not true. The NT kernel uses the Pascal calling convention because it's marginally more efficient spacewise, but the operating system itself has always been written in C and C++.

    --
    The difference between theory and practice is that, in theory, there is no difference between theory and practice.
  66. Re:More Debian-valid Software -- is this really go by be-fan · · Score: 2

    If you hadn't realized this, but Linux distros are full of redundant software. That's one of the main reasons I switched to Slackware. In RedHat 6.2, there are 3 versions of awk. Most distros come with two versions of gcc and their addandant language components (OBJC, Java, etc.) Mandrake comes with 3 Java compilers. (GCC-Java, Guavac, and Jikes.) Even Slackware has 3 versions of libc. Then there is all the redundancy that KDE and GNOME bring. Face it, if you were scared of a lot of code living on your computer, you wouldn't use Linux.

    --
    A deep unwavering belief is a sure sign you're missing something...
  67. Re:Gtk/QT use for commercial products by be-fan · · Score: 2

    Uh, I don't really think $2500 is going to be a deciding factor in software development. I mean most projects spend 10x that on pizza over the life of the project! If Qt saves just 5% development time for a dozen programmers in a medium project, $2500 will mean nothing.

    --
    A deep unwavering belief is a sure sign you're missing something...
  68. Re:Except Qt is copylefted. by eean · · Score: 1

    I'm not clear about the QPL yet. Does this mean that open-source and freeware people can port their stuff to windows without hassle? That would be nifty.

    As far as companies not wanting to pay, I'm sure that will not be too much of a consideration considering that a few thousands bucks isn't very much money for a commerical software project.

    The only people I see being put in the dark are the ms windows shareware developers (considering there isn't much shareware in the *nix world.)

    All-in-all I'm with cmdrtaco in that its about time. It would have been better for KDE and QT if they had done this earlier.

  69. Re:yay by Skeezix · · Score: 2

    Network. What's your point? I fail to see your argument.
    ----

  70. Re:Debian will have to find a new excuse by bssea · · Score: 1

    There is none. KDE will probably start carrying KDE now.

  71. Re:GPL by be-fan · · Score: 2

    Isn't that hipocracy? I mean propriatory software developers on Windows are no worse then their Linux counterparts. If Linux developers get it free, then so should Windows developers!

    --
    A deep unwavering belief is a sure sign you're missing something...
  72. Re:Increased acceptance already by Bruce+Perens · · Score: 1
    Me. I like it too. :-)

    Bruce

  73. The brave new world by Noiser · · Score: 1

    Comon, all you whiners, the license war is over! Think about the great possibilities now that Qt is completely free. First and foremost - the huge technical win: Now Qt/KDE and any other GPL application can share code and that is basically the the main goal of GPL. Example: Gnome has a new emerging i18n library codenamed Pango, which has features not present in Qt, such as complete bidirectional languages support. Now Pango can easily used with KDE and finally free the speakers of Arabic, Urdu, Farsi, Pashto, Uighur, Hebrew, Yiddish, Aramaic and a lot of other languages from Windows and Mac OS's which until now were the only ones to support them properly. And it's just one example (it happens to be quite relevant to me, as i need Hebrew and Arabic browser and office apps).

    Linux ruling the desktop? Yes, now it seems closer than ever.

    Thank you, TrollTech.

    1. Re:The brave new world by Noiser · · Score: 1

      Bidi HTML rendering is of course great, but not enough. I admit i haven't tried running it yet (don't currently have access to a Linux machine :( ), so maybe i'm just talking bullshit and correct me if i'm wrong, but AFAIK:

      1. Qt/KDE doesn't yet support true BIDI input and selection.

      2. The Hebrew po (translation) files for KDE seem to be visually ordered, which means that stuff like button/widget/dialog labels, window captions etc are not truly reordered.

      3. Again, _correct me if i'm wrong_, but it seems that in current KDE beta widget placing in a window is left-to-right and it's hard-coded. In a completely internationalized system the direction of the entire window/dialog/whatever should be localizable. Pango seems to already get it right; compare the screenshots: Pango (look at the end of the page) and KDE (notice the colons at the wrong side of the labels).

      Now i don't mean to diss KDE; the opposite is true: i love it, i just wished for a long time that they developed a complete bidi solution. Now that both Qt/KDE and Gnome/Pango are both clean GPL they can easily share code and will really speed things up.

  74. Re:Only Qt/Unix goes GPL ! by tincho · · Score: 1

    If you are interested in cross platform development, you might want to check wxWindows at wxwindows.org.

    It is a nice cross platform C++ framework that uses GTK+ under Linux, and the native API calls under win32. It also works under MacOS (I think) and has a very active developer community.

  75. Re:yay by UnknownSoldier · · Score: 1

    > Actually, IIRC BeOS's kernel itself isn't written in C++ either.

    That is correct. Only the GUI uses C++.

  76. Geez! Can we please kiss and make up already! by Bruce+Perens · · Score: 4
    OK, I'm responsible for stirring this up long ago. But I endorsed the QPL, publicly thanked Troll Tech, and called off hostilities a long time ago. Yes, we had a license conflict issue that has now been dealt with.

    Troll Tech has done everything necessary to accomodate the requests of the free software community. They have my sincere thanks, and should have yours, too.

    Thanks

    Bruce

    1. Re:Geez! Can we please kiss and make up already! by On+Lawn · · Score: 3

      Well, if I still had the URL I'd love to post the greatest KDE liscencing flame war, the one that brought slashdot to its knees for almost a week, the one you wrote. Its still a good classic read for people who think that Slashdot is only now going downhill.

      I never thought at the time though that I'd see the events that I've seen since then, let alone this post. But like the one a long time ago this seems to be like going to a charred building and screaming "Fire" with a gasoline can and a match.

      Things were settled for most people then by an excellent Freshmeat essay on how the CDE and OpenLook wars almost killed UNIX. Most everyone felt good about letting things go on their merry way until your post brought it to a new idealogical and mud slinging level. Even then the issue was more your integrity as a even handed leader after showing such childish predjudice more than the QT liscencing.

      And now that its GPLed you scream something needs to be done to make peace, and your sorry? I'm glad. Its good to see. But once again a little self important and too late.

      But most of us really are moving on with our lives quite nicely without really much concern over this liscencing issue. I do publicly thank your in your efforts that made QT liscencing more friendly to our scheme of software development. You deserve thanks, but yelling sorry for being the kid who turned the lights out when the city went dark is kind of, well, you know...

    2. Re:Geez! Can we please kiss and make up already! by wuice · · Score: 1

      I think this just goes to show that RMS isn't so much about free software as he is about his own socio-political clout. It's not enough that QT be free, it's gotta use his license or be unilaterally condemned. The most disgusting part of his rant, in my opinion, was where he demanded that they bow, scrape and beg forgiveness from free software authors, most notably from him. Sorry RMS, I personally think QT has done more than enough bowing and scraping to you for my tastes. In fact, to me, the whole debauchle read to me like:

      RMS - use our license or die
      QT - okay, here's our license, offers the same or more freedom than yours
      RMS - use our license or die
      QT - ok we're using your license
      RMS - to (sic) late!

  77. at last... by diakka · · Score: 1

    I'm very happy to hear that TT has come to their
    senses. I always believed that the GPL was the
    perfect solution from the beginning. It gives us
    the fredom we need, but still prevents non-free apps from linking and therefore does not cut off
    their revenue stream as would the LGPL. It's more
    risky from a business perspective because there is
    a danger of forking, but as long as TT does a good
    job of maintainang qt and makes enough people happy, history has shown it is not a common problem. I hope that more companies who produce libraries consider this as a viable business model.

    --
    -- Knowledge shared is power lost. -- Aleister Crowley
  78. Re:A GPL Windows/QT could fork from the free codeb by stevey · · Score: 2

    The way to bring Windows desktop users over to Free Software is to create cross platform Apps which reduce the need for Windows as a base platform in order to create a migration path for users

    Exactly, and thats why I started GNUSoftware.com.

    We should think about cross-platform issues though. I spend a lot of time trying to compile "portable" applications, which use GTK+, on Windows - and fail because people are using Linux specific calls when they really don't need to.

    Even the Qt app's I see on Freshmeat are often very Linux specific, for no good reason, and this stops me using them on Windows. (I've got a professional license).


    Steve
    ---
  79. Re:GNOME's name is pointless... by WhiteDragon · · Score: 1

    just because it is a backronym doesn't mean it is a bad name. As for being a network object model, I think you have the word grouping wrong. Think (Network (object model)) not ((network object) model).

    --
    Did you mount a military-grade, variable-focus MASER on an unlicensed artificial intelligence?
  80. Re:That's just your sick imagination by mattdm · · Score: 2
    There will just be Sun's source, IBM's source, HP's source, Helix source whatever.

    Sure, we all know of the historic fragmentation of Unix. But since then, the few examples of major forks in Open Source / Free software are notable for being rare exceptions to the general rule.

    --

  81. Re:What Miguel doesn't want you to know about GNOM by Havoc+Pennington · · Score: 2

    I'm not aware of this code, but if you post (or email me) the modules or files it's found in I'll be sure it has the proper credits on it. Unless you post specifics though I'm guessing this is a troll.

    Some factual corrections: the GNOME Foundation does not write code (and in fact is not yet legally incorporated), so it certainly should not be the subject of your sentence there. We also do not consider KDE a "bitter rival."

  82. Re:WRONG ! Re:We have a level playing field by HarpMan · · Score: 1

    Oh God! You people will never give up.

    Gnome is GPL'ed, not LGPL. So, come up with another reason why Qt is still bad.

    (Incidentally, Stallman prefers the GPL over the LGPL. So, if Qt was LGPL'ed, the Stallmanistas would criticize Qt for that. GPL is the most politically correct license.)

    --
    Stephen Molitor steve_molitor@yahoo.com
  83. Politics by jjr · · Score: 2

    Now with this released let KDE/GNOME compete on merit not politics. The sad fact is that KDE is at a disadvantage because of the Big corporate sponsership of Gnome. This does not mean that KDE can not get sponsered by these same companies. It just mean that KDE would have to have another project within the companies. Intel sponsers BEOS and Linux because it helps them sell hardware. If a company can see that they can make money of sponsering KDE they will.

    1. Re:Politics by jetson123 · · Score: 2

      Licenses aren't just about politics, they are about money and risk. And any engineer needs to think about money and risk. That's a big part of what engineering is about.

  84. Don't Get To Cocky, Chummer. by macsen_wledig · · Score: 2

    One of the great things about the free software community is the fact that it is growing. The people that compose the "mainstream" Free Software community today aren't necessarily the same ones that composed it two years ago. They sure as hell won't be the same as the ones two years from today. I am one of the new kind. A person who converted to the movement only recently. I don't have any bad blood against Qt. Neither do many of my peers. To the people that we convince to use free software in the future, the subject of the Qt license will be nothing but a history lesson. We will decide who's product we use, and whose product we contribute time, effort, and code to nased on the findings of our own experimentation. How can you be so sure that we will choose Gnome? Is it because gnome is the "standard" now. Step outside of your bubble and look around at the people using Freee Software now. If we chose something because it was the "standard" software for any given purpose, we would still be using Windows. I, and the people who switch to free software, have very little concern for standards. Take note of this and let your sekf grow.

  85. Somewhat agree by On+Lawn · · Score: 1

    I thought that the QPL was fine also, but I did respect the opinions of those that thought it wasn't good for KDE. Saying *you* raised a red flag in a sea of red flags that made a Stalin appreciation parade jealous is, well, something I've said before. Saying its all well and good, and expecting the community you think you represent to agree is, well, I'm getting tired of saying it.

    You didn't start it, you didn't finish it, but you did help. Thats the bottom line.

    1. Re:Somewhat agree by Bruce+Perens · · Score: 1
      You are correct. I am generally not the one to first see the issues, they are almost always brought to my attention by other people. What I do is write about them. A lot of hackers out there have trouble putting their feelings in words, and that's something I can do to contribute to the community. However, I'd hardly rate my response to Linus on KDE licensing as one of my better pieces. If you want to see something I'm proud of, look at the Debian social contract (and give the Debian developers who participated credit too).

      Bruce

  86. Bruce Perence's first -1 redundant. by Matthew+Smith · · Score: 1

    That is a very redundant post despite being written by BP himself. Much like this one. Off to work moderators!

    1. Re:Bruce Perence's first -1 redundant. by Bruce+Perens · · Score: 1

      Sound effect: loud raspberry. Anyway, I pushed the "No Score +1 Bonus" when I posted it.

  87. More Debian-valid Software -- is this really good? by mog · · Score: 1

    Ok. First, let me say that the only two distributions I use are Debian and Slackware. They are just what I like. My first instinct upon hearing this news was that.. "Great.. now KDE can be a real part of Debian." Then I did a double-take.
    Is this really what I want?
    What this means is that all of those countless KDE apps can be a part of Debian - for which in almost every case there is a Gnome counterpart. Package listings are already huge - they will surely go at least 1.25x by the inclusion of everything KDE. I'm not trying to knock KDE or QT - but having two of everything KDE and Gnome is not what I want in my package listing. Maybe it's time to set up three archives, instead of just one main one - one for non-aligned software, Gnome software, and KDE software (I realize that there are already KDE debian servers).
    Maybe I'm just crazy - but I don't really want to have to muck about in countless instances of duplicate software in my dselect that I'm never going to use. There must be a good solution to this.

  88. Re:A GPL Windows/QT could fork from the free codeb by Bruce+Perens · · Score: 3
    This is questionable from a GPL-compliance standpoint, until you have a GPL or LGPL Qt that runs on Windows.

    Bruce

  89. NT isn't C++ by wowbagger · · Score: 2
    Having been unfortunate enough to have worked with Windows NT (writing drivers for custom hardware my employer makes) I can tell you that NT is NOT written in C++. Actually, the original NT kernel was written in Pascal (now there's a thought to cause you to awaken screaming).

    However, the biggest problem with using C++ for shared libraries under any platform is that there is NO spec for
    1. How to mangle a name
    2. how to pass data on the stack (pure C++ linkage functions need not follow the C calling standard: it is perfectly valid for the compiler to generate them all callee-pops, or pass args in registers, or anything else. You want C style arg passing, you have to use extern "C")
    3. how to lay out structures with base classes or virtual functions

    As a result, it is not possible to guarantee that file x.so, created with g++, is linkable to y.so, created with Borland C++. It's a shame that with all the other CRAP the ANSI committee dragged into the language during standardization, they couldn't have spelled out at least how to mangle the damn names!

    As a big fan of C++ myself, I'd LOVE to see the kernel, X, and the windowing toolkit be true C++ classes: this is systems programming and that's what Stroustrup created the language for.

    However, I take exception (pun intended) at the claim that QT is C++: It isn't. It is another language, that you then must run through Qt's MOC preprocessor to make C++. If TrollTech had truly make Qt C++, they would have used virtual functions or functors to implement the connection to the windowing message system, not this mutant "Signals and Slots" stuff. That's what got me when I looked at KDE: I want to write in C++, not some mutant version of something that is almost C++. It's almost as bad as working with somebody who uses

    #define AND &&
    #define OR ||
    #define NOT !
    #define BEGIN {
    #define END }


    There. I said it. I feel better.

    me->Attire(Attire::Flamesuit);
  90. Re:Harmony? by Captain+Pillbug · · Score: 1

    It was mostly abandoned when QT was released under the QPL, and now it's dead for sure, since its purposes have been realized.

  91. Binaries are the problem. by Bruce+Perens · · Score: 1
    I'm most concerned with binaries. Even if he doesn't distribute any, someone will, and there's a real GPL problem there.

    Thanks

    Bruce

  92. GPL and internal-use software by David+Jao · · Score: 2
    I found one particular phrase from the Qt/KDE developers very interesting:

    In short, we have been convinced that the GPL does indeed protect a library from being used to develop non-free software. Non-free software, in this respect, of course, includes software developed internally in an organization.

    They seem to imply that code from Qt, or any GPL-licensed program, may not be used in any in-house software projects which are not distributed to the public. This conclusion flies in the face of the FSF's own interpretation of the rights granted by the GPL and free software:

    [With free software,] you should also have the freedom to make modifications and use them privately in your own work or play, without even mentioning that they exist.
    I'd be very interested in finding out if the Qt/KDE developers really intend to say that I have no right to make in-house-only modifications or use of Qt.
    1. Re:GPL and internal-use software by Ded+Bob · · Score: 1

      I'd be very interested in finding out if the Qt/KDE developers really intend to say that I have no right to make in-house-only modifications or use of Qt.

      They can try, but once the code is distributed under the GPL they won't be able to place this restriction on it.

      With this comment in particular, I think that they are still ignorant about how the GPL works.

    2. Re:GPL and internal-use software by Arandir · · Score: 2

      There's still great debate over the private-use issue. A recent statement by RMS says that companies forbidding their employees from distributing in-house modifications is okay, so long as those modifications remain strictly in-house. Copies given to employees (such as telecommuters taking it home) cannot have these restrictions. It all depends on who owns the copy.

      The GPL and QPL seem similar in this regard: you cannot keep an internal *product* private, only stuff in development can ignore the terms of the GPL. If you write an in-house word processor and give it to your HR department to use, you may not restrict them from redistributing it.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    3. Re:GPL and internal-use software by Zach+Baker · · Score: 2
      The GPL and QPL seem similar in this regard: you cannot keep an internal *product* private, only stuff in development can ignore the terms of the GPL. If you write an in-house word processor and give it to your HR department to use, you may not restrict them from redistributing it.

      Assuming it's only a question of copyright violation, I doubt that's true. Of course, if you're giving this GNU GPL'd software as a personal gift to members of your HR department, sure, you've distributed it. But in the situation you suggested, even though the company has copied their own (GPL'd) work, they really haven't redistributed it. The company has given copies, or access to copy, to company employees acting as such, not to a separate recipient. The HR department can no more redistribute or copy it at will than they can take home office supplies at will.

      If it's strictly a question of misappropriating trade secrets and/or violating an NDA, it gets a little confusing, but I still very much doubt it. The difficulty is that the copyright license allows a recipient to redistribute a GPL'd work, yet it may still be considered confidential. For example, software for monitoring a specialized manufacturing facility could embody many trade secrets, even if the code itself was not of particular independent economic value.

      The GPL forbids further restrictions, such as an NDA, on those who are distributed works under its terms. But even though it's improper to do so, that does not mean that the NDA has lost effect, or that reasonable secrecy measures were not taken. Therefore, the work and information in the work would still be eligible for protection as a trade secret.

      For example, let's assume such a thing happened: a company distributed a copy of GPL'd trade secret code to a third party under an NDA. The third party discloses the code publicly. Will the NDA be nullified in order to comply with the GPL? Unlikely, I think. The originating company will be at fault for violating the original work's GPL and maybe also for providing the third party with the GPL'd work under false pretenses. Meanwhile, the third party will still be at fault for violating the NDA.

      Oh, by the way, I am not a lawyer, and this is not legal advice. (Customer activation required. Cape does not enable wearer to fly. Tax-free in 49 states -- sorry, Tennessee!)

  93. hmm... by InsaneCreator · · Score: 1

    Wil this in any affect Kylix (delphi for linux) which is based on the QT lib?

    1. Re:hmm... by akey · · Score: 1

      Wil this in any affect Kylix (delphi for linux) which is based on the QT lib?

      No, probably not. People developing software can use either the GPL, or they can purchase a license from TrollTech -- Borland is probably not using the Free Edition. So, it shouldn't have any effect at all.

      ---

      --

      ---
      "Go Metallica. Die RIAA." -- Linus Torvalds
  94. Re:FSF now prefers Qt/KDE over Gtk/Gnome by Eladio+McCormick · · Score: 4
    But given that FSF prefer libraries to be covered by the GPL rather than the LGPL, they should now consider Qt preferable over Gtk.

    I don't think so.

    The idea behind the RMS editorial you're thinking about is that the GPL is preferable when you are providing functionality not available in other libraries. The LGPL is meant for situations where you provide functionality that the non-free competition already provides.

    Since there's plenty of GUI toolkits around, free or otherwise, I don't think it matters a bit. And, since Troll will sell you licenses to develop non-free software with Qt, the whole RMS anti-LGPL argument is kinda demolished in this case.

    But this is all speculation, isn't it?

  95. Great news, but I still perfer GNOME by billvinson · · Score: 1

    It is great news that KDE is finally going to loose the proprietary licensing baggage from Qt.

    It benefits everyone to having these desktops competing with each other. I hope this may spur KDE to develop C bindings like the C++ bindings for GTK. I really would rather never code in C++ (personal choice...)

    Anyway, this should be good for the community.

    Bill

  96. Re:Nothing Changes by quentinsf · · Score: 1

    Of course, it likely means that KDE wont be accepted by proprietary software makers as a standard...

    Unless those companies want commercial support. In which case this model could work quite well.

    Let's hope so.

  97. LGPL as Cinderella :-) by BryanBruns · · Score: 1

    LPGL as Cinderella, or, The Quest to Share the Source

    Her family knew she was the Lesser one.
    declaimed long lecture on the virtues of the Elder,
    and why none but the Greater one deserved
    to be your only true choice.

    As for the others,
    the unFree ones who claimed to be of Open mind,
    why they knew she was of that fervent kind,
    and so not suited in scrupulous specification their wares to bind.

    But in the latter days, minstrels told of how,
    the camp of Moz the Red came to laud the sisters' beauty.
    (And if some thought the Lesser fairer,
    why perhaps this was only whispered,
    lest such heresy disrupt the wooing.)
    And much was spoken of how all ought have license
    to wander at liberty, among the inner realms of the Open and the Free.

    And then the minstrels relayed the tale
    that even the keenest of the delving elves
    now pledged fealty to the Eldest sister of the Free,
    jousting with the gnomish usurpers for favor in each release.

    And all the while the trolls, as was ever their wont,
    found much of which grumble,
    and didst incessantly strive
    to veil the lands in fuddish confusion.

    Still, many were the requirements,
    exacting and essential,
    which inspired the quest
    to release the Source for all to share.

    Naysayers said not too narrow,
    never restricted so neatly
    as to fit only the tight confines of the Free,
    in haughty exclusivity.

    And the minstrels told of muttering that many who
    raised the banner of the ram had motives mercenary,
    pursuing plunder from lands beyond the Free,
    complaints that, in outland endeavors, aid in arms and armor
    was only advanced upon golden tribute to the few.

    Fashion flaunted its fickle fads
    against broadly styled designs,
    frowning on excesses of generosity,
    forsaking the wisdom of serpentine serendipity.

    All agreed on glass, transparency
    at the invoking of origination,
    when the glory of source
    was unveiled in splendid glare.

    And most felt clarity must bind each contributor
    in the same enchanted spell, for all who dare
    in the open to declare, to forestall foul deceiver,
    and the rise of selfish rivals who might not share.

    Many said that only a shapely vessel would do,
    no bloody chunks ripped out, to strew
    in butcherous abandon, greedily.
    No, though works might be combined,
    they should be linked entire, modulated
    with visible display of appropriate proper integrity.

    And long the searching, so many lost hope,
    falling by the wayside in baffled despair,
    with faith too frustrated to renew.
    The minstrels sang of how clashes and flames
    drove off many who might have joined the quest to share.

    Many seekers clung to clumsy convention,
    quarrelled over creaky compromise,
    or carved their own crude likenesses,
    caring little what conflict might ensue.

    But still some strove, until one day,
    after long questing, some came to see that the Lesser one,
    so long disparaged and neglected in her shabby niche,
    might be the fairest of them all.

    And thus might be told
    the tale of how she was found,
    the Lesser Princess of Gracious Liberty.

    Bryan Bruns, September 5, 2000
    originally posted at www.Nanodot.org

    Coda
    I fear in time's harsh glare she may not prove
    half so fair as I might dream,
    but in this light, for now, she outshines all others.
    And tis a pleasant tale to tell.
    For who can yet know, how far her domains might grow.

  98. GTK under Windoze by Lionfire · · Score: 1

    I'm going to have to disagree -- GTK support under Windoze is definitely quite good.

    Check out GIMP under Win95/NT/etc/blah/blah. I'll admit it used to be a little flaky, but now it works very well.

  99. Re:yay by lubricated · · Score: 1

    go to www.mandrake.net there is plenty of development going on. They are doing away with alot of their base. And I bet you they are still going to use C. Furthermore Enlightenment is not a window manager like any other. It uses more system resources than many other wm's. So yes you are wrong. What do you know about development anyway? Have you ever written anything?

    --
    It has been statistically shown that helmets increase the risk of head injury.
  100. Re:Read before replying. by Kenelson · · Score: 1
    If you decided to use Artistic license because you though it would escape problems, that I think you were misinformed. The problem at the time and always had been KDE developers borrowing code from GPL projects for a GPL project which linked to Qt without permision. The correct solution is to ask for permision or rewite the code. However, a classic response was to ignore it and try to promote the license from LGPL to LGPL with QPL. Thus the problem wasn't the LGPL, it was the use without permission problem. Switching to Artistic and the denying use of that code on a join theming project (I case I did hear about), sounded a lot like a change just to spite developers. When that happens the code just get rewritten, which is a waste. The whole point of open source licensing was to promote reuse. Now that Qt made the last pludge, I hope the infighting will die.

    As for the asymetry, I can't speek for the inconsiderate twits who may or may not be denying KDE use of gtkhtml code. I was speaking about the future and not the past. I don't know the situation, but if it was a case of license promotion then they had a right to ask it to stop. If they had taken the code originally from KDE, they are being asses. Changing the license to artistic just to prevent use in other GPL code is sinking to the same level. It hurts not just GNOME, but all GPL code which might want to use it. As soon as KDE is fully GPL complient (GPL/LGPL/BSD) licensed developer permision won't be a problem so long as people don't promote a license (GPL->LGPL->BSD). Demotion of licenses is aways allowed.

    Admittedly I am biased. I have been told in the past by one KDE developers "how dare I construct something to compete without consulting." That kind of attitude from someone who spouted "it is only about the code" and thus licensing issues should be ignore, gives me some reason to feel there are people in the KDE camp without a clue, in my less than humble opinion. But then KDE isn't immune to this. I am sure there are GNOME coders doing a tit to pay back for some preceived tat. They may well be the boneheads who flame Gtk-- from within the GNOME project just because they don't understand that some people might want to use C++. Just because both sides are engaging in license wars doesn't make either of them look mature. In virtually every case a license gets denided it results in bitterness and a denial the other way often to people who weren't involved in the first dispute. Maybe this will break the cycle. Most KDE developers and even TrollTech employees have not been bad, but KDE really should have cleaned their house up, come with their tail between there legs, gotten permision from all the people whose GPL code they borrowed and gotten themselves included in debian.

    If you do know of some code on which copyright was removed (and the source wasn't licensed in such a way as to allow that), I suggest you back the assertion up with references and campaign to get it fixed. Removal of copyright is not legal and thus unacceptable no mater which camp did it. Any KDE code which is in the Gtk-- is properly copyrighted even after the code was replaced. I won't speek for GNOME as a whole.

    --Karl

  101. We have a level playing field by tjwhaynes · · Score: 5

    At last KDE and Gnome can go completely head-to-head because they are now both totally grounded in GPL licensing. So what does the future now hold?

    Corporate take-up? Don't knock it - this is a potentially huge environment. Companies like to know where they stand, and simplified licensing is a huge bonus. Gnome already as a level of corporate acceptance as embodied by the formation of the Gnome Foundation to further the GNOME project. KDE may soon see itself in a similar position.

    Interoperability? Both KDE and Gnome are continuing to push their infrastructures forward and both desktop environments are likely to start eclipsing the competition sooner or later (already have eclipsed the competition in some areas). It's likely that Gnome programs will always talk most efficiently to other Gnome programs, and similarly for KDE to KDE, it would be nice to see the arrival of some bridge mechanism to allow the two camps to exchange and inter-embed each others applications across the divide.

    Flamewars? Almost certainly :-) At least now there won't be any (meaningful) wars over licensing ...

    Cheers,

    Toby Haynes

    --
    Anything I post is strictly my own thoughts and doesn't necessarily have anything to do with the opinions of IBM.
  102. Re:This makes Microsoft look good by Arandir · · Score: 2

    A) Microsoft indeed charges you to develop for Windows applications. Once upon a time you could get the SDK for free, but not anymore. And yes, Qt costs more than VC++, but Qt+Cygnus beats the hell out of MS for quality.

    B) You do make a good point however. Microsoft (and Sun, Borland, RogueWave, etc) doesn't care how I license my code. GPL libraries do. Qt under the QPL/GPL does as well. It's my only beef with Trolltech, but since I am already writing OSS, it isn't an urgent issue with me (so sue me for apathy :-) ). The best libraries are LGPL, BSD or freer. Although copyleft may have seemed like a good idea at the time, it absolutely screws over library users.

    C) On the other hand, if you need no restrictions on your own code, purchase Qt just like you purchased your Windows libraries. It's strange bitching about how free libraries don't give you as many rights as purchased ones do. So just go purchase it!

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  103. Hah hah, trolltech. by AFCArchvile · · Score: 1

    I can imagine the level of comments going on at TrollTech if the Troll in the name holds true to the Slashdot definition: 5u53 r0ck5!!! N0 1t d035n't! 51AcK|/|/4R3 r0k5! 5kR00 y0u, 1AM3R! (and so on, and so on, and so on.)

    --
    "Ancillary does not mean you get to rule the world." --U.S. Circuit Judge Harry Edwards, speaking to the FCC's lawyer
  104. Re:Porting QT/Unix by Arandir · · Score: 2

    It shouldn't be that hard at all. About 95% of Qt applies to either system. You only have to support the remaining 5%.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  105. Announcement on Troll Techs site. by shaka · · Score: 5

    Look again!
    There are two new announcements; Qt 2.2 released and Qt/Unix 2.2 being released under the GPL.

    --
    :wq!
    1. Re:Announcement on Troll Techs site. by Anonymous Coward · · Score: 3

      It appears to be released under multiple licenses. The Commercial license, the QPL and the GPL. Note that it is only the Qt free edition under the GPL, the windows version and Qt/Embedded are still ofcourse not under the GPL. That's still more than fair considering there doesn't have to be a free edition at all, besides which trolltech do have to make a living.

  106. Re:GNOME's name is pointless... by frantzdb · · Score: 2

    No. ``Network Object Model'' means that the object model is network transparent.

  107. Re:Wow by UnknownSoldier · · Score: 1

    > Um, doesn't this just eliminiate all philosophical reasons for Gnome?

    Yeap.

    Now, of course the debate over techinical reasons .... ;-)

  108. Now GNOME and KDE get assimilate... by ablaze · · Score: 1

    as we're waiting for releases. I think KDE2 stable is at least two-three weeks delayed. According to their release-plan it should be out...yesterday? yes: _yesterday_ :-(

  109. Re:More Debian-valid Software -- is this really go by dvdeug · · Score: 1

    It's all optional, but yes, there's a lot of redundant software.

    What the heck is OBJC? I'm fairly familar with GCC (a lurker on gcc@gcc.gnu.org) and I've never heard of it. In fact, no one ships two versions of GCJ (GCC-Java), as there has only been one released version. Most distros only keep around the C part of GCC 2.7.2, as that's the only useful part.

  110. yay by jilles · · Score: 1

    Now the debate about Gnome and KDE can finally focus on the stuff that really matters and has kept both from being a serious alternative to commercial desktop environments like windows and mac os: consistency, usability and interoperability.

    I'd say KDE has a headstart here, but not a big one.

    Now for some flamebait:

    Now that the license wars are over maybe it is time to retire Gnome's obsolete C code base. In my view only huge amounts of redundant efforts from open source developers will keep it working and up to date. I'd rather see these efforts directed at something usefull.

    Disclaimer: being unhappy with both Gnome and KDE I am now using enlightenment.

    --

    Jilles
    1. Re:yay by frantzdb · · Score: 2

      What does release frequency have to do with Enlightenment being obsolete? There is a lot of work being done on it. It progresses slowly because it is very ambitious.

    2. Re:yay by rm+-rf+/etc/* · · Score: 1


      Gnome has Objective-C bindings, which IMHO would be a much better choice than C++. It's a much cleaner and simpler language, and a much easier switch from C.

    3. Re:yay by jilles · · Score: 2

      At least C++ comes with some basic features C does not provide. Probably you can emulate them with macros (that's how C++ was originally implemented) but that most likely results in an uncontrolable mess. The only way you can enforce OO in C is by adopting strict coding standards. You can do the same in C++ and benefit from the additional features in that language.

      I agree that C++ in the hands of C programmers is dangerous stuff. Most likely they don't understand most of the features in the language. Hopelessly stuck in the sixties/seventies procedural paradigm they can do nothing but shoot themselves in the foot. But then, should these people really be implementing the next generation GUI? Me thinks not.

      Wrapping doesn't solve anything, you still need to maintain the wrapped stuff + the additional bloat (double trouble). Besides why wrap if you can implement in C++ directly (more maintainable code if done properly), or are we trying to cover up for a lousy implementation here?

      Finally binary compatibility, your apps will depend on the wrapper, not the wrapped piece of C blop.

      --

      Jilles
    4. Re:yay by Tet · · Score: 2
      maybe it is time to retire Gnome's obsolete C code base.

      OK, so it's flamebait (you even said so yourself), but I'll rise to it. What is obsolete about GNOME's codebase? Are you claiming it's obsolete purely because it's written in C? If so, do you propose retiring the obsolete Linux kernel in favour of the obviously more advanced NT kernel (written in C++)? That argument just doesn't hold any water. BTW, I too am dissatisfied with both GNOME and KDE (and enlightenment, for that matter), and am quite happily using fvwm2.

      --
      "The invisible and the non-existent look very much alike." -- Delos B. McKown
    5. Re:yay by jilles · · Score: 2

      from not having seen a major release in a few months, I drawed the conclusion that development is slowing down. Since it is far from perfect, I assumed people have something better to do. I don't closely watch development though, so maybe I'm wrong.

      --

      Jilles
    6. Re:yay by mikpos · · Score: 2

      The reason C programmers don't use C++ is because it's a complete mess and really offers no benefits over C. It is not object-oriented AFAICT; if it were, then I would be able to program generically, not suffer with these "templates". If you want an object-oriented language to co-operate with your C code, use Objective C. It's easy, it's fast, it's logical, and it allows you to program generically. If you want to a Simula-derived language that co-operates with your C code then, well, your SOOL, because C++ is your only option, and you'd have to have your headers files will be so riddled with #ifdefs as to make them near unreadable. I'm not bashing Simula-type languages. Simula is great. If you want to program in Simula, use Simula. C++, however, takes the worst features of C, the worst features of Simula, and adds a shitload of marketing on top.

    7. Re:yay by divec · · Score: 2
      It's staggering how many people think a bunch of random hackers engaged in a forum where consensus is pretty much the only unifying force can design a tight well-designed OS.

      Kernel or OS? Kernel development runs under benign dictatorship, not consensus. OTOH something democratic like Debian is a strong counterexample to your claim.
      --

      perl -e 'fork||print for split//,"hahahaha"'

  111. Re:Left it a little late. by dash2 · · Score: 1
    Why is it companies never open source stuff when things are going their way?
    Things are going Trolltech's way, no? I thought they were expanding at a rate of knots, had a new office in Australia, etc. Or have I been fooled by their PR?
  112. End of the flamewar? by Hieronymus+Howard · · Score: 1

    Could this be the end of the eternal (& damnable) kde vs gnome flamewar? Unlikely I think, though this could be a major step towards peace. At least it should reduce the amount of vitriol directed at TrollTech who are, by most accounts, nice guys. They tried what seemed to be a sensible open-source business model - make the code free for free software developers but charge people who used their toolkit for commerical (non-free) software. This seemed like a good idea to me and I still can't understand why this made them hate-figures.

    Both KDE and Gnome are good. They both have cool features and annoyances. It's pretty childish to claim 'gnome r00lz, kde 5ux" and I'm sure that a lot of the abuse comes from people who are not developers. I'm a user not a (Linux) developer myself and at the moment I'm using Helix Gnome but am looking forward to KDE 2. Good luck to both of them.

    HH

  113. Re:Another GPL victim... by Michael+Marxmeier · · Score: 1
    The QT framework was the only thing making KDE not qualify for being GPL'd, since it was proprietary software.

    Not!. QPL is a OSD compliant license which means its free software - which is the opposite of proprietary.

    Its just that some people think its not compatible with the GPL.

  114. What will happen to Debian's Joseph Carter? by Anonymous Coward · · Score: 1

    Oh man, what will happen to knightbird?! I'm looking forward to your next project, man! Take care.

    1. Re:What will happen to Debian's Joseph Carter? by Forge · · Score: 1

      I m officially signing on to blame Joseph Carter for this.

      Would QT go GPL if he hadn't been as load and vulgar about Troll Tech and KDE on kde-licensing@ ? My hat goes off to you Mr. Carter. Thanks and God bless.

      This is not a flame. As someone who has been in the trenches on this one for years now, with Knightbird and Mosfet, I can tell you it's been a strain.

      Troll Tech has up to recently been scared spitless of using the GPL for QT. They don't quite trust it. These days however they are strong enogh to fight abusers and big enogh to outrun forkers.

      --
      --= Isn't it surprising how badly I spell ?
  115. QT by l33t · · Score: 1

    Vincent
    You know what I like about Open Source Software? It's the little things.
    Jules
    Example.
    Vincent
    Well they got their own version of Windows but they don't call it Windows...
    Jules
    Well what do they call it?
    Vincent
    KDE.
    Jules
    Get out! Well what do they call a Big Whopper?
    Vincent
    Uh, I'm talking about SOFTWARE, man, not burgers.
    Jules
    Oh... rrright.

  116. It will be interesting to look back in ten years. by danny · · Score: 2
    If this had happened two years ago, we'd probably be looking at one major desktop environment desk. Now we have two of roughly equal popularity and quality... I can't say if that's a good thing or a bad thing, though.

    In ten years we'll be able to look back at this episode in the history of computing with the benefit of hindsight, perhaps in the way we can now look back at the history of Unix - there are still arguments, but they are a lot more subdued.

    Danny.

    --
    I have written over 900 book reviews
  117. Too late? by pli · · Score: 1

    If they would have done this two years ago they would have had ~90% of the Linux GUI market. However, they didn't, and now QT is just another player in the GUI-field. Bad business move.

  118. Re:Yeah C makes a poor OO language by xelah · · Score: 1
    Using plain C, structs and macros you can hack out a very inelegant version of an OO-like language, true. But why would you want to? I see - you must have way too much time on your hands and enjoy fixing mechanical mistakes that would never have appeared in a higher-level proper OO language like C++ in the first place.

    The only time I've found a reason to use C for an OO program was when I was first trying out OO design. The C compiler I had was very nice and very fast on my 33MHz proccessor. The C++ compiler was VERY slow and buggy. Oh, and I didn't know C++ very well :-)

    I suspect that the second of those is the primary reason for people doing it nowadays...

  119. A trend? by disarray · · Score: 1
    Perhaps this, along with the announcement of Mozilla being MPL-GPL dual-licensed, indicates that the commercial software industry is moving away from reactionary license creation to the use of commonly-accepted licenses.

    Or perhaps these two distinct actions should simply be taken at face value. Yeah, that's probably it.

    --ian

  120. Re:GNOME Foundation helping KDE by Chuck+Chunder · · Score: 2
    Troll Tech has produced a usable product. The GNOME foundation has produced press releases.
    Given the age of the GNOME Foundation it's a little unfair to expect them to have produced much else.

    In any case, the GNOME Foundation itself is an advisory board, to the world outside GNOME it will probably look like they do little else than release the occasional statement (or press release or propaganda if you prefer).

    It's the individual companies that make up the Foundation that we should be expecting things from and it seems to me that many of the newer companies to GNOME are coming to the table with some fairly substantial quantities of code.

    In many ways it's better that such contributions come in slowly rather than overwhelming/changing the character of the GNOME project in a massive code drop.
    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
  121. Re:Except Qt is copylefted. by InfraRED · · Score: 1

    the biggest problem is not the price IMO.. imagine the following scenerio: we have qt 2.2 GPL-d.. KDE developers (or anybody else) finds bugs is QT, fixes them and KDE uses this fixed (and obviously GPL-d version) of QT. After this nobody can ever write a proprietary application for KDE

    --
    metamoderate!
  122. GPL not LGPL by Tet · · Score: 5

    Interesting choice. Going for the full GPL pleases the extremists, but it also has the side effect of allowing Troll Tech to protect their revenue stream. If they'd made it LGPL, then people could develop and sell proprietarty (closed source) apps using Qt. Being GPL prevents that, thus pleasing both sides. Those wanting to go that route can still purchase a Qt Professional Edition license from Troll Tech (something you had to do under the QPL anyway).

    --
    "The invisible and the non-existent look very much alike." -- Delos B. McKown
    1. Re:GPL not LGPL by Arandir · · Score: 2

      It appears that it will be dual-licensed under the GPL *AND* QPL. You can still use it for your Open Source projects and never have to tell a soul which of the two licenses you are using. You won't be forced to write GPL-only applications, and you won't be forced to submit modifications as patches.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  123. It's official, from trolltech's website by Freud · · Score: 1

    Head on over to their website, and you can see on the headlines:

    2000 Sep 04 Qt Free Edition goes GPL

    --
    Blah blah blah, etc.
  124. Re:FSF now prefers Qt/KDE over Gtk/Gnome by Per+Abrahamsen · · Score: 2

    > They sold a proprietrary version of gcc to
    > Motorola (which they could only do because they
    > require copyright to be signed over to them).

    At least anonymous /. posters claim this over and over, despite having no supporting evidence, and despite the FSF having signed hundreds of counter contracts with GCC contributers stating that they will not allow proprietary version of GCC.

  125. Finally listening by Micah · · Score: 1

    I've been saying (seriously) they should do that here on Slashdot for months. Got ridiculed in the process. Glad to see them listening. This really does make sense, for everyone.

    Once again, KDE has a chance. I was starting to think about dumping it for Gnome - that will no longer be necessary. (Although I like what I see of Gnome, so I'll use it too!)

  126. Another GPL victim... by Mekanix · · Score: 1

    Why does *every* OSS need to be GPL? I thought OSS was about *freedom*, freedom of choice. But it seems that GPL doesn't allow other OSS-licenses and tries to "strangle" all of it's opponents...

    ... that's not freedom... that's totalitarianism...

    just my 2 cents...

    Bjarne

    1. Re:Another GPL victim... by divec · · Score: 2

      Why is there only one form of not kicking people in the face? I thought not kicking people in the face was about *freedom*, freedom of choice. But it seems that "not kicking people in the face" doesn't allow other violence-level paradigms.


      Seriously though, OSS does give freedom of choice. People like Sun were freely choosing GNOME over KDE, which must have been at least partly because of the legal issues with GPL+QPL. Troll, it seems, have chosen to keep themselves competitive, by going with what the market wants.

      --

      perl -e 'fork||print for split//,"hahahaha"'

  127. Wait...okay, I can still use it...whew! by Arandir · · Score: 2

    GPL'd libraries can ONLY be used by GPL'd applications. At first I was thunderstruck that I can hundreds of other developers would no longer be able to use Qt for the BSD, MIT, Artistic or other Free Software projects. Releasing Qt under a pure GPL license would guarantee that many of us long-time Qt supporters would instantly switch to GTK.

    But reading the announcement closer, there towards the end, I see that it will be dual licensed under the QPL and GPL. Whew! Thank goodness those of us who use unrestricted licenses can still use Qt.

    This appears to be a dual-license (I have sent mail to Erik to verify). In this case, using the GPL makes all the sense in the world, since now everyone who uses *any* Free Source license can use Qt.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  128. Re:MODERATORS: sucked in by reverse psychology! by jilles · · Score: 1

    Damn, the whiner got what he wanted. I'm moderated down.

    "the second half of this comment is grossly uninformed and/or just flamebait and deserved to be moderated down"

    Well enlighten me (no pun intended). Really what good is it to claim somebody is uniformed and than call to the moderators to back your unmotivated opinion up?

    "Of course, I realize I'm going to be modded down for this flamebait :)"

    Don't bother wasting valuable moderation points on this guy. Use it to moderate people up rather than down.

    --

    Jilles
  129. And about time too... by Dan+Hayes · · Score: 2

    ... because it now means that the vastly unproductive whining about the Qt license that /.ers seem to love can now finally be declared a thing of the past. KDE can now stand (or fall) on its merits rather than on the basis of an ideology devised by a man who doesn't even have to work for a living.

    I've been using KDE for a while at home now, and it's slick, especially compared to the lumbering dinosaur that is GNOME. For an operating system with a set of tools designed to be small and modular, it's amazing that most of the applications written for it are so slow and bloated, with "value added" features taking precedence over quality and performance. With people like this on the side of Linux, Microsoft's continued desktop dominance seems to be secured.

    Let's hope we see more apps like KDE, where a decent product counts for more than ideological squabbles.

    1. Re:And about time too... by kyz · · Score: 1

      And if it weren't for "ideological squabbles", what's the betting that Qt would have a "freeware" license for a binary library and header file? And Linux, for that matter? No, one of the most important drives in people (IMHO) are their ideologies.

      As RMS keeps saying, freedom is important, and now we're seeing people percieving the value of freedom. OK, the issue of the QPL vs GNU GPL license compatibility is completely obnoxious legalese, useless for much more than flaming, but it's nice to see TrollTech making a deep sacrifice and jumping into the frying pan for the sake of public concern. It's OSS showbiz, the irony here is TrollTech is one of the few "Open Source" bandwagon jumpers that had a free (speech) product in the first place.

      --
      Does my bum look big in this?
    2. Re:And about time too... by divec · · Score: 2
      TrollTech is one of the few "Open Source" bandwagon jumpers that had a free (speech) product in the first place.

      If you mean QT, it wasn't free(speech) until version 2.0 last[?] year. (The source was available)
      --

      perl -e 'fork||print for split//,"hahahaha"'

  130. Re:A GPL Windows/QT could fork from the free codeb by Arandir · · Score: 2

    There's nothing stopping developers from forking the FreeQT codebase to create a new Windows based QT.

    How does the GPL effect this change? Under the QPL one had every right to port it as well.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  131. Re:GNOME/KDE = GPL ; QT = GPL ; GTK+ = *L*GPL. by Mr.+Hankey · · Score: 1

    What you are saying, then, is that TrollTech doesn't have the right to make money with their toolkit, in which they have placed considerable time and effort. Why, then, should companies who make proprietary apps have the right to make money with those?

    Just a thought.

    --
    GPL: Free as in will
  132. Linux Power's Christian Schaller? by Karma+Sucks · · Score: 2

    Oh my god, Christian Schaller (also known as UrAnus on /.) is out of a job too! Poor guy. Linux Power will have to close down.

    --
    (Please browse at -1 to read this comment.)
  133. Left it a little late. by not_cub · · Score: 4
    "Eeek, gnome's catching up on us. Quick, GPL it".

    I think they may have missed the bus on this one. If they had released Qt under GPL earlier, the whole KDE/gnome idiotic split could have been avoided.

    Why is it companies never open source stuff when things are going their way? (eg Netscape waited til Microsoft had them by the balls).

    not_cub

    --
    q='echo "q=$s$q$s;s=$b$s;b=$b$b;$q"';s=\';b=\\;echo "q=$s$q$s;s=$b$s;b=$b$b;$q"
    1. Re:Left it a little late. by Dionysus · · Score: 1

      Eh, Troll Tech/QT is not KDE. KDE uses Trolltech's free technology, but QT does not belong to the KDE project. The failure of KDE in the Linux/OpenSource environment will not affect Troll Tech in any way. The GNOME people doesn't have Trolls 'by the balls', anymore than Microsoft has VALinux by the balls (competing in different fields). But, being an informed reader, you probably already knew that, so what was your point again?

      --
      Je ne parle pas francais.
  134. Re:FSF now prefers Qt/KDE over Gtk/Gnome by Per+Abrahamsen · · Score: 1

    > But this is all speculation, isn't it?

    Yes, but you are right. The stated reasons for prefering GPL over LGPL doesn't really apply in this case. However, the idea of FSF advocating Qt over Gtk+ is fun.

  135. Re:More Debian-valid Software -- is this really go by be-fan · · Score: 2

    Both Mandrake 7.1 and Slackware 7.1 come with both egcs 1.1.2 and gcc-2.95.2. They also come with all the additional components for each compiler (egcs-java and gcc-java, etc).

    BTW> OBJC=objective C.

    --
    A deep unwavering belief is a sure sign you're missing something...
  136. Cost is an issue. by jetson123 · · Score: 2
    I agree that the strategic issues are very important to companies.

    But so is cost. I have worked at both large and small companies. $1500/developer is a lot of money, and you don't get a whole lot for it with Qt compared, say, to an MSDN subscription.

  137. Re:WRONG ! Re:We have a level playing field by Menthos · · Score: 1
    Gnome is GPL'ed, not LGPL. So, come up with another reason why Qt is still bad.

    Huh? Where did you get that from? The core gnome libraries (and gnome-core) are all LGPL, for maximum flexibility in licensing when you build something on top of GNOME.

    --

    GNU/Linux. The Freshmaker.

  138. YIPPIE by loik · · Score: 1

    Today is a great day for free software! Go KDE! Go TROLLTech! I wouldn't have dreamt of this! It also shows what constant, obstinate, bold complaining can achieve. (no, the excitement won't stop soon...)

    --
    and now for something completely different
  139. Re:Read before replying. by Kenelson · · Score: 1
    I did read! I was addressing the "On another note, ....". You are correct that the situation is asymetric with KDE can take GNOME code and not the other way around.

    My opinions (which don't represent that of GNOME) are mixed. Of course, neither project has been particularly good at sharing. Some GNOME people did not grant license to use code the KDE people have wanted (with some reason as Qt wasn't free and the KDE people at that time just assumed they could), and later some KDE people have licensed things with artistic license to prevent use in GNOME. It is childish tit for tat. I don't feel that KDE has a very good track record of respecting licensing issues. As far as licensing they have shown to be quite clueless. Closing your eyes and assuming it will go away like they did was short sighted. The fact that Qt actually did release GPL and cleaned up their mess does relieve them of the initial act.

    TrollTech on the other hand is quite cleaver in protecting their business model to the benefit of free software. They released as little as they could until Harmony came allong. They released more (ablity to fork code base) which wiped Harmony out. It however, was still not enough for Debian but most people could ignore that. Had GNOME not pressed on it would have remained that way. Then when KDE appears to be losing some ground to GNOME, they release it as GPL (ablity to port to other platforms). It is good for KDE and for free software, but it is too late to heal the frictions caused. Merging Gtk+/Qt won't happen because a GPL licensed GUI in a field with many LGPL GUI is not a value added. It also shows that there gamble that the QPL would be enough was not enough to keep KDE ahead politically. Had they released with GPL at 2.0, it may have made a larger difference. That should be a valuable lesson to other companies, if you want to be free do it with GPL. Less arguing and larger acceptance.

    For TrollTech latest gift, we should certainly thank them.

    --Karl

  140. honest license, but probably not competitive by jetson123 · · Score: 2
    I congratulate Troll Tech for doing "the right thing"; I thought the QPL was dishonest and misleading, and releasing Qt under a GPL license (with an option to license for commercial use) rectifies this. It must have been a hard decision, because it is difficult to predict how it will affect their revenue stream.

    But ultimately, I think it won't help much. GTK+ is covered by the LGPL, and there are nearly a dozen other free toolkits out there that can be used for both free and commercial software without paying anyone anything. Qt is competing against software that is much cheaper (i.e., free) for commercial usage, and the cheap competition is pretty good.

    Another issue that now needs to be revisited is what happens to commercial users of Qt if Troll Tech goes out of business or stops development. Will the FreeQt foundation continue to exist? In the past, it attempted to guarantee that a BSD-style version of Qt would be available.

  141. Re:GNOME's name is pointless... by Skeezix · · Score: 2
    No. ``Network Object Model'' means that the object model is network transparent.

    Yes. That's where CORBA fits in. CORBA is basically an object oriented RPC (Remote Procedure Call) specification.
    ----

  142. GPL vs LGPL by lytles · · Score: 1

    While the move to GPL is definitely a good one, it does not put qt on level ground with gtk/gnome. Most of the gtk/gnome libraries are LGPL, which allows dynamic linking by proprietary (non-GPL'd) applications, which is much better for "system" libraries.

    I understand that licensing to commercial apps is the tt business model, and that is fine, but the GPL does not eliminate the issue license in choosing a graphics library (if you want to see proprietary apps for GNU/linux/...)

    This is still a move to praise, but with the understanding that the qt/gtk competition is still important.

    1. Re:GPL vs LGPL by Per+Abrahamsen · · Score: 2

      > This is still a move to praise, but with
      > the understanding that the qt/gtk competition
      > is still important.

      Yes, to developers of unfree software, and to companies like Red Hat which want to attract unfree software to Linux. However, I suspect most free software developers don't see it as a problem, that developers of unfree software will have to pay Troll Tech for a license to the professional version.

    2. Re:GPL vs LGPL by jag29 · · Score: 1

      If you want to write proprietary code against Qt, buy a license from Troll Tech. Seems like fair licensing to me, more fair than LGPL in that respect.

  143. Re:MODERATORS: sucked in by reverse psychology! by Goonie · · Score: 2
    Really what good is it to claim somebody is uniformed and than call to the moderators to back your unmotivated opinion up?

    Because claiming that GNOME is "obsolete" on the grounds that it uses C instead of C++ is, IMHO, grossly uninformed, and didn't even deserve explanation. 90% of what makes code easy or hard to maintain is how well it is designed and presented, and maybe 10% is due to the language. I'd much prefer to have to maintain well-written FORTRAN than badly written Java, and, from most of the stuff I've looked at, GTK+ and GNOME are well-written.

    --

    Any sufficiently advanced technology is indistinguishable from a rigged demo
    --Andy Finkel (J. Klass?)
  144. Re:Not _JUST_ GPL. LGPL still prefered by Khalid · · Score: 1

    They will just have to ask the copyright of the patchs to be assigned to them, as does the FSF, otherwise the patchs won't be incorporated. Most of the time (although not systematically) having its patch incorporated is a priviliege (witness Linux) so I am pretty sure developpers will accept. They have also the option to "buy" the most intersting patchs.

    Technically speaking there is also a risk of forking, but "moraly" I don't see this happening, as most developers understand that Trolltech still need to make a leaving, to continue to improve QT. This will be like a stab in the back for someone who has given a lot to free software. Personally I won't hesitate to buy the commercial QT edition if I had to develop a closed product, I see this as a deserved reward for Troll Tech.

    Well those are just suppositions ! only the future will tell what will really happen !

  145. Bad news for C coders and Ada coders. by yerricde · · Score: 2

    KDE has a far superior architecture to GNOME (its main rival), since it is written in C++

    And has no C or Ada/GNAT bindings; do the C++ booksellers have stock in Trolltech?


    <O
    ( \
    XGNOME vs. KDE: the game!
    --
    Will I retire or break 10K?
  146. Re:I don't think so. by jpowers · · Score: 2

    When will you gamer morons get it through your thick skulls that a lot of people *DON'T LIKE* First Person Shooters?!? I for one would not pay .10 for a First Person Shooter.

    Don't get me wrong, I feel the same way about FPSes. I'd much rather play strategy games or RPGs, which I'm happy to pay for. What I was suggesting was that shareware has been and still could be an important route for NEW, DIFFERENT, and as yet UNDISCOVERED types of games to be introduced, and shouldn't be tossed aside while it still has potential value.

    Of course, to understand what I was trying to say, you'd have to have the capacity to grasp things in context, which would require that you NOT be a moron... too bad you couldn't manage.

    -jpowers

    --

    -jpowers
  147. Only Qt/Unix goes GPL ! by mlefranc · · Score: 1

    What should we think about the fact that only Qt/Unix (i.e., the one directly threatened by gtk/gnome) goes GPL ?

    1. Re:Only Qt/Unix goes GPL ! by Anders · · Score: 1
      What should we think about the fact that only Qt/Unix (i.e., the one directly threatened by gtk/gnome) goes GPL ?

      The Windows version is not even free in the beer sense. As a hobby developer, this puts me off using Qt. I like the fact that if I want to port to Windows, I will have the possibility.

      Granted, the current GTK+ stuff for Windows is far from easy to work with, but I have hopes that it will get better. And I have the time to wait; my programs are primarily for Linux and a Windows version would just be an added bonus. In the mean time I enjoy using GTK+ under Linux so no problem there.

      For someone using Windows as her primary platform, GTK+ is not that ideal, though. Freeing Qt/Win32 would be an excellent way to get more developers to the Linux platform; they might be interested in a Linux version if it was a free bonus when using a different widget set. I even have the impression that Qt might be better (cleaner) than what Windows programmers are used to. But while Qt/Win32 will cost a developer money, hobby developers are not even going to try it.

      The trolls could keep their "commercial usage costs" policy and they would not risk a whole lot of sales.
      --

    2. Re:Only Qt/Unix goes GPL ! by Per+Abrahamsen · · Score: 2

      Annoying for us who develop free software that must run on both Unix and MS Windows. However, with the Unix version going GPL, it is now our own fault if we don't port it to win32.

    3. Re:Only Qt/Unix goes GPL ! by Teliver · · Score: 1

      Answer: It probably is a direct response to the Gnome Alliance. THey saw that the issue was holding back acceptance of QT, and decided to bite the bullet. At the same time, they are unwilling to entirely give up their old way of doing business. This is perfectly understandable and reasonable for a company changing its business model. To put it simply, TrollTech has realised that it needs to learn to swim. But instead of diving in the deep end, they've gone in the shallow end in case they flounder. They probably won't, but at this stage no one can really tell. Think of this for what it is: A very brave first step.

  148. Debian by pyth · · Score: 5

    ARRGGHHH!!! Why does every good thing happen _after_ a Debian release!?!?!?

    1. Re:Debian by alleria · · Score: 1

      Um, because a Debian release _is_ a (very) good thing? :-)

    2. Re:Debian by MichaelH · · Score: 1

      Add this to your /etc/apt/sources.list:

      deb http://kde.tdyc.com/ potato kde kde2

      Seemed sort of inactive until shortly after the last beta release. Now the debs in question seem to get updated every few days. Works, anyhow.
      ---
      Michael Hall

      --

      Michael Hall
      mph.puddingbowl.org

    3. Re:Debian by CrosseyedPainless · · Score: 1

      Because, given the speed at which Debian issues releases, the chances are far greater that *any* given event will occur just after a relase, than just before a release. :)

      Disclaimer: I am a (mostly)happy Debian/KDE user.

      Although, on a related note, I've been using Helixcode Gnome (1.3?) for the last few days, and it's pretty impressive! (Let me say, parenthetically, that an analogue of kdevelop would do more for Gnome than all the corporate sponsorship in the world)
      I'd just like to know why click-to-focus stops working correctly after a period of use. Is it a sawfish thing? Can any gnomoids here point me in the right direction on this?

  149. Re:GPL by be-fan · · Score: 2

    Hipocracy means saying one thing and doing the other. Releasing your software under the GPL for Linux (saying that you embrace free software) while keeping it for-pay under Windows (which is essentially NOT embracing free software) is hipocracy by definition. Unless you can prove that using the GPL doesn't mean that you embrace free software, or that charging the developers on one OS and not the other is in tune with the ideals of OSS, then you've got no case.

    BTW> People who correct spelling are the most anal-retentive jack-holes you'll ever meet.

    --
    A deep unwavering belief is a sure sign you're missing something...
  150. GPL virus has yeat another victim by nchip · · Score: 4

    For immedeate release 4th september 2000

    The widespread virus called 'GPL' is spreading at alarming rate. Because most patients don't notice any symptoms, 'GPL' has managed to lurk it's way into so many lines of code, that many anylysts believe that all other copyright forms are about to become extinct. RMS, the author of the virus, has been spotted partying like a wild animal and laughing his beard off.

    --
    signatures pending - ansa@kos.to - (dont mail there)
  151. It'll mean that... by yerricde · · Score: 2

    ...Kylix apps can be released under GNU GPL. No more and no less.
    <O
    ( \
    XGNOME vs. KDE: the game!

    --
    Will I retire or break 10K?
    1. Re:It'll mean that... by PurpleBob · · Score: 1

      This is where we need a "Misinformative" moderation.
      --
      No more e-mail address game - see my user info. Time for revenge.

      --
      Win dain a lotica, en vai tu ri silota
  152. Re:Except Qt is copylefted. by bockman · · Score: 1
    Maybe you're right. I was wondering wy QT didn't make this move before ( GPL-ing the tollokit and making money by selling a GUI Builder/ RAD environment ).

    Now, however, it could be too late for this strategy, with KDevelop already well on his way - and both free and gratis, apart from powerful( I never used it, but I've read a lot of praising reviews ).

    So, let's hope they have a better strategy - or that they offer has enough added-value wrt KDevelop to gain them customers.

    --
    Ciao

    ----

    FB

  153. Yes by CAPSLOCK2000 · · Score: 1

    Yes, yes, yes, etc....
    I'm so happy. KDE will officially get into Debian and discussions with Gnome people are shortend by at least 40%.
    Thank you God, now how about that Ferarri I asked?
    Whaddaya mean, I get it on the same day as Microsoft break up and the 2.4 kernel?

  154. Re:GNOME/KDE = GPL ; QT = GPL ; GTK+ = *L*GPL. by jetson123 · · Score: 2
    Why should companies get a license to make proprietary software with free toolkits? If your goal is to make the free toolkit an industry standard, the reason is that allowing them to do so makes your toolkit more likely to be accepted. It's not a moral obligation, it's a choice the toolkit author makes. It's a basic, free-market choice: lower the price to get more market share. And at $1500 vs. $0, that's a significant incentive.

    LGPL is a good license for an open source or free software GUI toolkit if it furthers the goals of open source or free software. I think it does.

  155. GPL is an advantage to Troll by Erik+Hollensbe · · Score: 1

    WRT the GPL/LGPL debate:

    Am I the only one that noticed that Qt can still make money with the GPL, instead of the LGPL?

    The GPL benefits us, the home users and developers, with a free Toolkit.

    The application developers, who want to modify the source and not release the changes, are going to put a nice lumpy sum in the Trolls' pockets. The LGPL wouldn't require them to show anything but the library source. :)

    Erik

  156. Re:This makes Microsoft look good by Keith+Russell · · Score: 1

    A) Yes and no. You do have to pay for the Visual C++ compiler. But you can still download the Platform SDK gratis.

    B) Amen, brother!

    C) Have you seen the price of Qt/Windows? $1550 for one Professional edition license! Either that, or use Qt Free Edition, and write to an X11 library/server for Windows, which is redundant for obvious reasons.

    My big problem with Trolltech is that they consider Windows-compatible and Open Source mutually exclusive. Is it GPL eliteism, or are they just trying to stick it to the "evil empire", developers and users be damned?

    Every day we're standing in a wind tunnel/Facing down the future coming fast - Rush

    --
    This sig intentionally left blank.
  157. And the winner is... by Nailer · · Score: 1

    Personally, the only concern which seeme to be relevant was that closed-source software developers would have to pay licensing to Trolltech to write KDE apps. I didn't want one company controlling and being the sole benefactor of QT [which has contribution from many other sources].

    Now the closed source developers won't have to pay that license fee. This is a good thing, but not really that great. Still, it will slightly encourage vendors yet to take the open source plunge to create apps for KDE. This is a good thing.

  158. Windows port finally a possibility? by pjpII · · Score: 2

    From what I can ascertain, the license allows you to "distribute machine-executable forms of the Software or machine-executable forms of modified versions of the Software", and thus you could port Qt to windows- which means that some intreped developer could potentially make Qt an actual Cross platform development platform(I suppose that you could also port it to Mac, and various other OS's)

    This would be REALLY nice for all those open source projects that have been residing only on Linux due to Trolltechs strange marketing scheme for the professional version.

  159. End of OTT accusations? by divec · · Score: 3
    This is good news all round, and should hail the end of a lot of divisive mudslingling. Those who claimed that Troll's aim was to split the free software community are proven wrong; their aim was to make profit and when the GNOME foundation shifted the playing field their actions changed correspondingly. It should also show that the FSF and Debian were anti-QPL and not anti-Troll/KDE:
    "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.
    "Debian is excited to see Trolltech take this step," said Wichert Akkerman, leader of the Debian project. "This will encourage the acceptance of Qt as a building block for free software.
    --

    perl -e 'fork||print for split//,"hahahaha"'

    1. Re:End of OTT accusations? by divec · · Score: 1

      Sorry, the quotes were from the end of the article, I should have made that more clear.

      --

      perl -e 'fork||print for split//,"hahahaha"'

    2. Re:End of OTT accusations? by danny · · Score: 1
      Are they real quotes or did you just make them up? They're not among the ones in the TT announcement.

      Danny.

      --
      I have written over 900 book reviews
  160. A GPL Windows/QT could fork from the free codebase by maynard · · Score: 3

    There's nothing stopping developers from forking the FreeQT codebase to create a new Windows based QT. Frankly, I think the Windows port of QT is one of the best advantages of QT over GTK+. Windows support with GTK is still in it's infancy while QT is quite usable.

    The way to bring Windows desktop users over to Free Software is to create cross platform Apps which reduce the need for Windows as a base platform in order to create a migration path for users. That means porting the new StarOffice and KOffice to Windows, giving users a chance to feel comfortable with the new environment, and then waiting for the next costly Windows upgrade to convince the users "there's a cheaper way..."

  161. KDE Stile Guids. by Forge · · Score: 1

    Every time KDE is mentioned we have the claim about no standards or people needing QT to develop KDE apps.

    Actualy what you need is to folow the stile guide.

    KDE Standards and Style Guides

    Ohh. And here is an interview with Kurt Granroth.

    --
    --= Isn't it surprising how badly I spell ?
  162. Re:A GPL Windows/QT could fork from the free codeb by SEE · · Score: 1

    Have you ever tried to maintain a port where you can only distribute patch files to a base source file?

    While the QPL gave the legal right to create a fork, its patch clause made it a practical impossibility.
    Steven E. Ehrbar

  163. Next flamewar subject by Idaho · · Score: 2
    So, now we can't flame each other over this subject, I think it's time to search for new subjects. How about:
    • X is more stable
    • X has a better GUI
    • X uses much less memory
    • X also works on older computers
    • X compiles on more platforms!
    • X is/should be default on distro Y
    (where X is your favorite Desktop Environment)
    I'm sure you can make up more of these....
    --
    Every expression is true, for a given value of 'true'
    1. Re:Next flamewar subject by Tyndareos · · Score: 1

      Dumb me ... Before I had finished reading your post I thought you were making propaganda for using the bare X-protocols from now on for writing our apps. Ironically though most of the listed arguments hold for such a statement ...

  164. Re:GNOME/KDE = GPL ; QT = GPL ; GTK+ = *L*GPL. by Mr.+Hankey · · Score: 1

    Riiight. It has nothing to do with control, more likely it has to do with a few people who can't stand to pay for software. The free beer rather than the free speech. The code is GPLed, if you wanted/needed something which works differently, you could a) change it yourself, or b) use another toolkit. It seems you'd rather choose b, which in itself is telling. (As a side note, the "artificial right of profit," as you call it, is what keeps companies alive.)

    Qt by its nature presents a framework for application development. Anytime you create a framework for something, there is a certain amount of influence exerted. This is not necessarily a bad thing, progress has to be made somehow. The fact that a company has produced this toolkit has little bearing on its usefulness, however it has allowed TrollTech to create an excellent and productive programming environment which might not have existed had they not put their effort in. Indeed, they have gone the extra mile now and made it free - free to be distributed, free to be changed. This is a big step for a company which derives its revenue from Qt.

    Frankly, I don't believe that Trolltech is any more destructive than the Helixcode or Gnome foundation "bands of nobodies." The main thing that has been proven by this discussion is that people will complain about anything given the chance, and that's pretty sad.

    --
    GPL: Free as in will
  165. Doesn't solve all the problems by DanMilburn · · Score: 2

    It seems, from past discussions I've seen and had on Slashdot, that the reason the big corporations prefer Gnome is not the GPL or concerns over the legality of KDE, but the fact that the Gnome libraries are actually L(esser)GPL, which allows the development of proprietary apps.

    Now, the KDE libraries are LGPL, but if Qt is GPLed, that makes no difference. Anyone who wants to write non-free software in KDE will still have to pay for the Qt Professional License. Otherwise the whole lot will have to be GPLed, or released under a GPL compatible license.

    I suppose it's up to personal taste whether you regard this as a problem or not, but it's something to think about.

    1. Re:Doesn't solve all the problems by RPoet · · Score: 3

      If anything, the GPL licensing of Qt is an encouragement for "big corporations" to GPL their own Qt based software! Don't say this won't happen, because it will, it has, and it IS happening.

      The GPL licensing of Qt will be our guarantee that the KDE desktop will remain free and that we won't end up depending on one or more proprietary, closed-source components, which the LGPL would have permitted. After all, is not free software why most of us became Linux converts?

      Do not disregard Trolltechs announcement. Today might be the happiest day of the Linux desktop! Oh, the euphoria!
      --

      --
      "Oppression and harassment is a small price to pay to live in the land of the free." -- Montgomery Burns.
  166. http://www.trolltech.com/company/announce/generalp by Xenex · · Score: 2
    Correct link is http://www.trolltech.com/c ompany/announce/generalpl.html

    That links to the old QPL announcement.

  167. Re:It's officical! by Erwin-42 · · Score: 2
    How strange; why is the date on this announcement 31st April? And there are only 30 days in April, too.

    (although I would be more worried if the date was 31st march 23:59:59 :) )

  168. GNOME Foundation helping KDE by evin · · Score: 2
    Acknowledging that industry backing of the GNOME Foundation was a factor in the decision to GPL Qt, Eng said internal debate on the issue began in May and accelerated in the middle of June

    As some people had predicted, the formation of the GNOME Foundation is having more of an effect on KDE than the KDE leaders had claimed possible.

    Since Qt 2.2 should be compatible with KDE 2.0, I'll be checking it out in a couple days. Didn't like KDE 1.0 much, but I didn't like GNOME 1.0 much either.

    1. Re:GNOME Foundation helping KDE by scrytch · · Score: 3
      > As some people had predicted, the formation of the GNOME Foundation is having more of an effect on KDE than the KDE leaders had claimed possible

      1. KDE is already GPL
      2. Troll Tech does not produce KDE
      3. Troll Tech does not make reactionary rush decisions, and probably had this in their pocket for some time.
      4. Troll Tech has produced a usable product. The GNOME foundation has produced press releases.
      5. I speculate that a letter from RMS explaining how the GPL (as opposed to LGPL) would protect their "free software only" clause had a lot more to do with it than flaming cretins on slashdot.
      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
  169. Re:More Debian-valid Software -- is this really go by cjwatson · · Score: 1
    The real solution to this is to improve the Debian archive and associated tools so that the package system is easier to manage. I don't think we want to start saying "no, you can't package that, the distribution's too full now"; instead, there need to be various keyword search and categorization options, that sort of thing.

    The much-talked-about though never-quite-here package pool idea may provide a good infrastructure for this.

  170. Re:That's just your sick imagination by the_1000th_Monkey · · Score: 1

    It's that exact phenomenon why I personally view the GPL as unfreeing, by requiring me to license my software one way versus another reduces my freedom. In practice I almost always use the BSD license which gives the users of my software the most freedom: keep it open, close it, or just plain use it. Don't mistake me, I think the GPL is a Good Thing in many cases, for example the Linux kernel, by requiring all of it's derivations to stay open all modifications to it can be absorbed into it as they are deemed worthwhile by Linus; and this sort of mandatory evolution behavior is good for many sorts of projects, I just think it's wrong to refer to it as free, because I really think that's a huge misuse of the word.

    Looking back I trailed off, but that's ok :)

    --
    where'd my typewriter go?
  171. It's life - but not as we know it... by Snaller · · Score: 1

    Funny... the message was labeled as "Interestin", i would have labled it "Incomprehensible".... guess you had to be there...

    --

    --
    If Google really cared they would fix Android Chrome to reflow text, instead of discriminating
  172. Hooray! (echo) by korpiq · · Score: 2

    One less problem with an obvious yet unaccomplished solution on the way.

    This took a long time. I only hope it will prove profitable for Trolltech - that would show the way for other companies as well. Profitability is actually quite likely, due to more spread (Debian etc) with GPL and the fame of QT's ease of use (I haven't tried out doing user interfaces with anything else but HTML for years, so I really don't know myself).

    --

    I think, therefore thoughts exist. Ego is just an impression.
  173. TrollTech press releases by CentrX · · Score: 1
    "Qt Free Edition goes GPL: Trolltech offers a choice in licensing with the addition of GPL licensing for the upcoming release of Qt"

    and

    "Qt 2.2 to be released"

    Chris Hagar

    --

    "The price of freedom is eternal vigilance." - Thomas Jefferson
  174. http://www.trolltech.com/company/announce/generalp by Xenex · · Score: 2
  175. What Miguel doesn't want you to know about GNOME by Truth+About+GNOME · · Score: 1
    Fact: Anyone who has seen the GNOME desktop is well aware that it "borrows" heavily from successful commercial designs produced by Apple and Microsoft, and Miguel de Icazza's admission of blatantly stealing many Microsoft Excel features for his own spreadsheet application is often quoted. A lesser known fact is that the GNOME Foundation has stolen code from its bitter rival KDE, as well. It is no secret that GNOME uses about 11.5 thousand lines of C++ from KDE 1.*; all you need to prove this is a copy of the complete GNOME and KDE source. What is a secret is that only about 45% of this code is properly credited to the KDE Core Team.

    Why has this never been publicized in the past? A combination of two reasons. The first is that most (>99%) GNOME's users lack the technical skill to read source code. The second reason is that because of the rift between GNOME and KDE, very few people know both codebases well enough to notice, and those who do are probably the GNOME developers which stole KDE's work in the first place.

    --

    Brought to you by The Truth About GNOME . Please write us for more information.

  176. www.trolltech.com/company/announce/generalpl.html by Xenex · · Score: 1
  177. In All Cases by nuintari · · Score: 1

    I say, NONE, cause I don't use desktop enviroments! Unless you count CDE, which they make me use at school, which is still better than Gnome or KDE. Gimme a straigh window manager, and I'm happy.

    --N

    --

    --Nuintari

    slashdot : where an opinion can be wrong.

  178. QT/Unix only by MostlyHarmless · · Score: 3

    (from the spoilsport dept.)

    Large caveat: This applies only to QT free edition; that is, QT/Unix. Those who wish to develop cross-platform applications will still have to look elsewhere for their toolkit.

    Note: Don't bother replying with flames about GTK+ sucking for Windoze. At least the port exists, is free software, and has the chance to improve eventually.

    --

    --
    Friends don't let friends misuse the subjunctive.
  179. FSF now prefers Qt/KDE over Gtk/Gnome by Per+Abrahamsen · · Score: 4

    Well, I have seen no announcement to that effect. But given that FSF prefer libraries to be covered by the GPL rather than the LGPL, they should now consider Qt preferable over Gtk.

    Since companies like Red Hat have a interest in promoting development af Linux software, free or unfree, they should still have an interest in Gtk, because the LGPL allows their customers to develop unfree applications.

  180. What Miguel doesn't want you to know about GNOME by Truth+About+GNOME · · Score: 1
    Fact: Anyone who has seen the GNOME desktop is well aware that it "borrows" heavily from successful commercial designs produced by Apple and Microsoft, and Miguel de Icazza's admission of blatantly stealing many Microsoft Excel features for his own spreadsheet application is often quoted. A lesser known fact is that the GNOME Foundation has stolen code from its bitter rival KDE, as well. It is no secret that GNOME uses about 11.5 thousand lines of C++ from KDE 1.*; all you need to prove this is a copy of the complete GNOME and KDE source. What is a secret is that only about 45% of this code is properly credited to the KDE Core Team.

    Why has this never been publicized in the past? A combination of two reasons. The first is that most (>99%) GNOME's users lack the technical skill to read source code. The second reason is that because of the rift between GNOME and KDE, very few people know both codebases well enough to notice, and those who do are probably the GNOME developers which stole KDE's work in the first place.

    --

    Brought to you by The Truth About GNOME . Please write us for more information.

  181. Think of the economic implications... by Taurine · · Score: 1

    ...for news websites ;-) Without the opportunity to post stories about this topic, banner impressions will drop like a stone! Who will be the first to file bankruptcy?

    Or maybe they will move over to stirring up anxiety between BSD and Linux now...

  182. Reasons from GPLing from the authors by FattMattP · · Score: 5

    Freshmeat has an article by the Troll Tech guys talking about why they decided to go GPL.

    --
    Prevent email address forgery. Publish SPF records for y
  183. www.trolltech.com/company/announce/generalpl.html by Xenex · · Score: 1
  184. Another win for freedom of choice! by Per+Abrahamsen · · Score: 3

    > I thought OSS was about *freedom*, freedom
    > of choice.

    Well, Qt 2.2 gives the developer the *choice* of two licenses, QPL or GPL. Qt 2.0 only offered one license, the QPL. So it seems to me that the freedom of choice has increased, not decreased, with this announcement.

  185. Re:It will be interesting to look back in ten year by Gurlia · · Score: 1
    If this had happened two years ago, we'd probably be looking at one major desktop environment desk. Now we have two of roughly equal popularity and quality... I can't say if that's a good thing or a bad thing, though.

    I say this is a good thing. Competition prevents stagnation. 'Nuff said. Especially in the free software world, where profit is usually not a motivating factor.


    ---
    --
    mikre he sophia he tou Mikrosophou.
  186. If it ain't broke, don't fix it! by Per+Abrahamsen · · Score: 2

    > Why is it companies never open source stuff
    > when things are going their way?

    It would be silly to change a business model that *worked*. Only when the currect business model breaks down, you go looking for alternatives.

    Or do you believe companies should make free software for the good of their hearts?

    1. Re:If it ain't broke, don't fix it! by divec · · Score: 1
      It would be silly to change a business model that *worked*.

      But it's just as silly to assume that something will work tomorrow, just because it worked yesterday. I think that's a fair description of what Netscape did.
      --

      perl -e 'fork||print for split//,"hahahaha"'

  187. My e-mail to TrollTech. by renoX · · Score: 1

    I've send the following e-mail to TrollTech:
    >>>
    Your web site says in the front page "2000 Sep 04 Qt Free Edition goes GPL".

    My first reaction was: congratulations, but when I click to the link it links to 1998 article which talks about the QPL being an OpenSource license ??

    I am a quite puzzled by this, could it be an error ?, a bad link ? a web site defacement? I don't know.

    What I find very funny is that (if its true), they are protecting their business model (selling Qt licenses) by going GPL and not LGPL! But it should please RMS because he is telling people to use GPL and not the LGPL!

    I'm wondering, under what licence Gnome is ? GPL ? LGPL? a mix of both?

    Will we see a flamewar between LGPL supporters and GPL supporters? (beside the obvious C/C++ holy war of course).

    We're indeed living in "interesting times" :-)

  188. Other platforms? by Hortensia+Patel · · Score: 1

    Might it not be a good idea to release a free edition of Qt for Win32? Now that the source is GPL'ed there's nothing to prevent somebody else from building a workalike implementation layer, but using TrollTech's source would make for much cleaner development and easier upgrades to the Professional edition.

    I know a lot of the /. crowd consider the whole issue of Windows ports to be beneath contempt, but there are some useful OSS projects using Qt (Doxygen springs to mind) which supply binaries for Win32 but can't be built under Win32 unless you sell off some internal organs and buy a pro license. More testing eyeballs are all very well, but it seems a shame to restrict your developer base like this.

  189. Re:It's officical!?! by Xenex · · Score: 1
    I'm more worried about my spelling of official ;)

    It's 1am, and I've had no caffine for 6 hours.... so I have SOME excuse ;)

  190. Nothing Changes by Anonymous Coward · · Score: 2

    Excuse me if I am wrong. I belive the main gripe with the QPL was that if a closed source developer made software with QT they had to pay Troll Tech. Which means if KDE became the standard linux desktop then all closed sourse developers that wanted to write for Linux would have to pay money to Troll Tech. So the agaer was that is seemed wrong for one company to have such control over linux and m ake money off every closed source app. So that is why people did not want QT to be standard. Maybe I am crazy and wrong. But. They GPLed it not LGPLed. Which is funny because it is a library. What this means is now the code is split but.... If you want to wrote a closed source app you still have to pay Troll Tech! GTK however is under the LGPL with means it is free for closed and opensource developers. So really I don't see the change except the Debian will not include KDE and their distro and people who do not read between the lines with think everything is all better. Personally I don't care what license there software is under. It is their software. But I just don't want everyone who is writting for linux to be forced to pay these guys money. I would like to see them LGPL there library (or BSD it for all I care) and then just sell the development tools to whoever wants them. But hey what do I know. -Brian

  191. Port XEmacs to KDE! by Karma+Sucks · · Score: 1

    Go Per! :-) Just kidding. I love your work man.

    --
    (Please browse at -1 to read this comment.)
    1. Re:Port XEmacs to KDE! by Per+Abrahamsen · · Score: 2

      > Go Per! :-) Just kidding. I love your work man.

      Actually, I suspect Bill Perry (of Emacs/W3 fame) wish this had happened three months ago. He has just finished porting XEmacs to gtk/gnome, which he chose because of licensing reasons, even though he prefered Qt for technical reasons.

  192. Now GNOME code can be copied to KDE! by Karma+Sucks · · Score: 2

    Not only does the community gain, but KDE gains too. I hope this removes Miguel's objection to KDE using GNOME code. This will be very interesting indeed as now KDE is free to copy GNOME code verbatim. They may not really want to do that though, seeing how KDE uses clean C++ while GNOME uses C.

    On another note, I wonder what it means for Red Hat's C++ toolkit, GTK++, etc. They may gain from copying Qt code too.

    --
    (Please browse at -1 to read this comment.)
  193. How long before KDE/(QT 2.2) will be out? by divec · · Score: 1

    When Troll announced that QT v 2.0 would be released under the QPL, there was some lag time before v2.0 was released. I guess we might be up to the next Debian release before a "completely un-QPL-dependent" KDE is released - anybody know more about timescales?

    --

    perl -e 'fork||print for split//,"hahahaha"'

  194. Re:That's just your sick imagination by Wheely · · Score: 2

    Actually, the GPL doesn't protect you from commercial bastardisation at all. Sun WILL eventually produce there own gnome as WILL HP and IBM and even though the GPL means the source will have to be available, who is going to give a damn. There will just be Sun's source, IBM's source, HP's source, Helix source whatever.

    However, QT have to be given a little praise here, they grew from nothing to be a relatively profitable little Norwegian company and have taken a very bold step. I hope it works out for them.

    Regards

  195. KDE is already GPL. by Anomolous+Cowturd · · Score: 1

    If KDE was QPL then Debian would already have included it. Their beef was that the two licenses were incompatible, thus they could not legally distribute KDE. I believe the QPL version of Qt is already in Debian non-free.

    Whatever the PR, Troll did this because the Gnome Foundation scared them. One advantage of GPL over QPL is it's hydra-headedness.. you could kill Qt before by putting Troll out of business.. but now Qt is immortal.

    /etc/apt/sources.list will be losing a line anytime now.. coolies.

    --
    Software patents delenda est.
  196. Almost there by Aahven · · Score: 1

    Nice to see this happen. But... I still have to pay for not releasing the source. Yes, "it's good for the free software, you have to release the source"! I refuse to call my desktop free (as in speech) if I must to do that. I would release my software under GPL, but just because it's the only allowed way, I won't use it. This is my opinion, I know that everyone disagrees with me.

  197. Porting QT/Unix by divec · · Score: 2

    How hard would it be to port QT/Unix to Cygwin? Anyone who knows lots about this sort of stuff care to answer?

    --

    perl -e 'fork||print for split//,"hahahaha"'

  198. Except Qt is copylefted. by yerricde · · Score: 5

    Because Free Qt is copylefted (choice of QPL or GNU GPL), companies still have to pay the Trolls to be able to port their proprietary winsoftware to free*n?x. GTK+ on the other hand, is lesser copylefted under LGPL; it will be more popular for proprietary apps such as your precious games.
    <O
    ( \
    XGNOME vs. KDE: the game!

    --
    Will I retire or break 10K?
  199. Don't underestimate us the users. by Karma+Sucks · · Score: 1

    You overlook the users (that's me). The users want KDE and want it bad, as they have often made clear.

    If the bad commercial boys have any sense they will give it to us.

    --
    (Please browse at -1 to read this comment.)
  200. Whoa, fast reply! by renoX · · Score: 1

    30s or so after, I have their answer and now the links is refering to the true beef, here an extract:

    (2000/04/31) -Trolltech announced today that it will license the upcoming free version of Qt/Unix 2.2 under the GPL (GNU General Public License). Developers will have the option of using the open-source version of Qt 2.2 under either the QPL (Q Public License) or GPL license, depending on their licensing requirements.

    Many thanks to Trolltech.
    Mmm, time to have a second look to Qt.

  201. April's Fools by m2 · · Score: 1

    Hmmm... looks like TrollTech as a twisted sense of humour:

    (2000/ 04/31) -Trolltech announced today that it will license the upcoming free version of Qt/Unix 2.2 under the GPL...

    emphasis mine. Since April has 30 days, I guess this one is an April's Fools, no?

    Com'on! I'm joking! Wait! No... no! Arrrgggh!!!

  202. Great news by gizmoNaut · · Score: 1
    This is terrific news, for all the reasons others have pointed out already, but mostly, IMO, because it will remove the political barriers to using Qt, and therefore KDE. Now we can have a real, honest-to-God, head-to-head competition between KDE (particularly KDE 2.0) and GNOME, and let the better DE win.

    Personally, I always thought the licensing issue was blown way out of proportion, but now that it's history we can lay that to rest. (Even though I suspect some of the more ardent /.'ers will suffer withdrawal symptoms...)

  203. Red Hat covets non-free software? by divec · · Score: 1
    companies like Red Hat [which] want to attract unfree software to Linux.

    Is that a fair statement? Red Hat seem to strongly favour free software, though they use non-free software sometimes. If you were talking about Caldera I'd agree, or to a lesser extent SuSE.
    --

    perl -e 'fork||print for split//,"hahahaha"'

    1. Re:Red Hat covets non-free software? by divec · · Score: 2

      Ok, point taken - but would you say Red Hat does aim to attract non-free software? AFAICS they do a lot of evangelising of Open Source - as opposed to the aforementioned example of Caldera.

      --

      perl -e 'fork||print for split//,"hahahaha"'

  204. It won't end the flame wars by Tough+Love · · Score: 1

    But now the flamewars will be about straight-up technical merit, or perhaps the relative merits of C++ vs good old C for development and deployment.

    Such flamewars mainly have good effects. If you don't believe me, you haven't read the linux-kernel list enough. Most good things that happen in the kernel seem to require a flamewar somewhere along the line. Flamewars force participants to do their homework, and to engage in a continuous cycle of technical oneupsmanship. Flamewars force participants to produce results.

    Regardless of the prospects for ever-more-entertaining-and-productive flamewars, the door is now open for real interoperability between Gnome and KDE.
    --

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  205. QT and Gnome by IcesTorm-I · · Score: 1

    Such announce is never gratuitous in the open source software world. This kind of event has to be triggered...Let me think...Ho yes, all the momentum around gnome this past week must be the reason why Troll Tech has decided to release QT under the GPL. They were afraid to lose interest against the duo Gnome/GTK with all the declarations made by Sun, IBM etc. Ho well, the past has shown that releasing a software under the GPL is godd to compete. I would love companies to release more software under GPL not because of the pressure or competition but because it really good indeed. Congratulation to TrollTech anyway. We will miss the KDE/Gnome troll.

  206. C++ compilers: why Sun, HP went with GNOME by Anonymous Coward · · Score: 1

    The C++ ABI is a moving target. Sun and HP would want to release binary distributions of any desktop/GUI environment, and unfortunately, this is not possible with KDE/Qt because Sun and HP's compilers keep changing their C++ compilers and break their ABIs. GNOME is the lowest common denominator - it's written in C and will work as well on 15 year old compilers as it does on the current crop of optimizing compilers. You can write your GNOME/GTK C program with gcc and link it against a Sun compiled set of GNOME libraries without any trouble - try that in C++/g++ and see how far that gets you. Commercially I can tell you that supporting Sun's C++ offerings is a complete fucking pain in the ass: 4.2, 5.0, 5.1, 6.0 all have incompatable ABI changes. A C++ vendor *MUST* ship source code - there is no other choice. No wonder why the public loves Java so much - in theory it works the same everywhere with no ridiculous compiler/environment/version conflicts to worry about. Too bad the C++ crowd can't get their act together. Life would be MUCH simpler if all companies dropped support for commercial compilers altogether and just supported GCC.

  207. Source for the quote? by gizmoNaut · · Score: 1

    Where did that quote from Eng come from? I'm not questioning its accuracy; I just want to find it.

  208. MODERATORS: sucked in by reverse psychology! by Goonie · · Score: 1
    Now for some flamebait:

    Once again, moderators have been sucked in by a comment along the lines of "I'm going to get moderated down for this, but...". In general, I think that any post containing such a remark should be moderated down because it's an attempt to unduly influence the moderators. In this specfic case, the second half of this comment is grossly uninformed and/or just flamebait and deserved to be moderated down. There was NO justification for moderating this comment up.

    I call for some debate on an explicit addition to the moderation guidelines that these kind of appeals should cause a comment to be moderated down. Does anyone else out there care?

    Of course, I realize I'm going to be modded down for this flamebait :)

    --

    Any sufficiently advanced technology is indistinguishable from a rigged demo
    --Andy Finkel (J. Klass?)
  209. Not _JUST_ GPL. LGPL still prefered by Phill+Hugo · · Score: 1

    People still stand in having to pay royalties to Troll to use Qt in a non GPL application. Not necessarily a bad thing. That comes later...

    Gnome's libraries are mainly under the LGPL allowing royalty free use which is really why its been blessed so.

    Its a risky, but perhaps rewarding move for Troll. On the bad side (from their view) the GPL base would permit a better, seperately maintained
    variant with GPL code they cannot add to their commercial option - it wouldn't be all their code at that point.

    On the good side from their view, it may mean more people use KDE/Qt. Thus developers wishing to support it end up paying Troll in the
    process.

    This isn't bad though. The problem (as I see it) is this....

    Companies who wish to use Qt commercially can do so (at a price) without giving their improvements to Qt back. While GTK+ can be used without
    royalty, its LGPL status means any improvments made that a non Free product uses must be distributed back out under LGPL or GPL. Nothing
    else. No bribe accepted. (Yes, they may go elsewhere but the real issue here isn't about being popular, its about being Free. Ideally both, but not simply popular. Windows has that).

    In the absense of an "only GPL" library suite in popular use (meaning GPL applications all round from everyone who uses it), the LGPL option
    with no alternatives is better than the GPL with a (regardless of price) non Free alternative. At least we get the improvements.

    Its a fair swap. More use of Qt to Troll's benefit for the option to merge Qt/Gtk under GPL. That would be the Free softy utopia but for not the GTK is still probably going to be prefered until an "only GPL" Qt vriant becomes widely used without a commercial option.

    Phill