A Quick Cost Analysis of Qt vs GTK 19
An anonymous reader writes "George Staikos responds
to Michael Meeks' arguments
of using GNOME over Qt. There is also a discussion of events at KDE.News. In Meeks' same set of slides, he states that Ximian OpenOffice is much faster to start than native OpenOffice."
The Point (Score:1, Interesting)
Commercial software companies prefer Qt (Score:4, Interesting)
As someone who works for a company that owns Qt commercial (for unix), I'd like to offer my point of view.
Management tended to be overly estatic about this Linux development environment because it's "free". So, obviously, there needed to be some justification of making a $2300 purchase in order to support this "free" linux system.
When first learning about what was available a few years ago (GNOME and KDE) I set up machines to evaluate both. We chose KDE, and it was 95% because of Qt; it's API, it's professionalism, the signal/slot idea, etc. All of the software we've developed with it has been proprietary in house stuff; we haven't made any money off of software sales - just off of its use.
But I'm sure other people may feel differently. Obviously if you're a lone consultant, it may be a bit too expensive for you to attempt to spend money up front in order to make money off of software. I suppose that's part of capitalism.
But I am a happy Qt commercial user, and we will continue to support KDE development, and pay for Qt, as long as we're still writing software for Linux.
If a GNOME advocate can point me in the direction of information/screen shots of something that can match the power of Qt/KDE/ and KDE kiosk mode, while providing clean documentation, a quarterly newsletter, and 1 year of e-mail support, I'd be interested in finding out more information.
Until then, KDE and Qt well exceed our needs, and I'm happy to be able to use them.
It all goes back to that TCO doesn't it (Score:2)
Re:It all goes back to that TCO doesn't it (Score:2)
Re:And if you don't know either yet. . . (Score:3, Interesting)
The GTK project seems to have gotten away with not having updated its documentation for 1.2 since it was 75% done in 1999. Looking over the documentation requirements and comparing those to what I expect from good documentation, they were really more like half done.
The GTK 1.2 documentation is still in that state, & GTK 2.0's documentation doesn't appear to be much better.
Not every function or object has a complete description, almost every
Re:And if you don't know either yet. . . (Score:2)
The GTK 1.2 documentation is still in that state, & GTK 2.0's documentation doesn't appear to be much better.
I like the ambiguity of your using the word "appear" - shows that you know GTK+ 2.0's documentation is in fact much better than 1.2's, but don't want to admit it. Yes, Qt does have nice documentation, but it still uses that poxy slot and signal mechanism along with a daft preprocessor.
Chris
Re:And if you don't know either yet. . . (Score:2)
Free software fork to closed? (Score:2)
As I understood it at the time, if you use free Qt then your program can never be non-GPL (or at least non-free). That is, any work done with free Qt has be free software, which means that even the original developer (who is normally free to fork to a non-free version) can't fork his/her project into a commercial, closed version.
Take, for example, TuxRacer. There is a non-free version of it
Re:Free software fork to closed? (Score:1)
A persistant myth. Free Qt is released under a dual license GPL/QPL. The QPL allows you to use any Free or Open Source license. You are NOT restricted to the GPL.
Re:Free software fork to closed? (Score:1)
That seems to say that code developed with free Qt must be free, always. Doesn't that mean that the code in a commercial app which was developed with free Qt must continue to be free. Can you explain how dual licensing means that my reading of the above bit of the FAQ is incorre
Re:Free software fork to closed? (Score:2)
That approach (obviously) takes sagans more time than using an adaptable library license in the first place, but I imagine it would be legally permissible.
Re:Free software fork to closed? (Score:2)
I'm interested in this as well. Under my understanding of the GPL, you need to give source to anyone you provide binaries to. If I only give the two other guys on my development team binaries compiled against the GPL'd Qt Free Edition, I'm complying with the letter of the GPL. If we then turn around, purchase a commercial license of Qt and start selling this software, has either license (GPL or Qt commercial) been violated? Sure, maybe
Re:Free software fork to closed? (Score:2)
Name one Free or Open Source license that does not allow this. There aren't any. Note that this does not specify that ALL people EVERYWHERE must be able to distribute it as free/open, just that the person with the Qt GPL/QPL license must do so; i.e. the original author.
the receivers must be free to give it to whomever they like.
Since the receivers got the software in a free/open form, then of course they
Re:Free software fork to closed? (Score:2)
Basically, TrollTech doesn't want a team of developers coding with Qt Free for years, and then buying a single license to build the final closed-source product. They're a friendly, easy-going company and as someone else said, if you really found yourself in the situation of wanting to make a closed fork, they'd be happy to sell you a license.
Re:Free software fork to closed? (Score:3, Interesting)
Re:Free software fork to closed? (Score:1)
Depends on your interpretation of "original developer" ... the person writing code in this case it building on top of the Qt codebase. Therefore in some ways the "original deve
You just forgot to mention one thing: (Score:2)
They got it nail down pretty well: you want to benefit from our work? OK but it is only you or others in an "altruistic" basis.
You want to become the next Bill Gates? That is fine, but you stood in our shoulders, so cough up the dosh.