To view parent comment, click here.
To read all comments associated with this story, please click here.
> darkside
hahahahaa! qt is not dark, it's opensource, run by a really nice group of _people_ that have been very supportive to the freesoftware movement. you make it sound like it is microsoft. shame on what ever being that calls a useful gpl code producing entity 'darkside'.
i think qt is a good thing for opensource, and opensource mobile, it's a pity it didn't became the standard in the first place.
> GTK has its advantages (the license for example).
i dont see any underlaying advantages. if you want to write a freesoftware app with qt its cool and free. if you want to write a commercial app you pay a little (yes it is not much taking in to regard what the developer cost are for a commercial app). with the money trolltech^H^H^H^H^Hnokia actually does something: they develop the most kickass cross platfrom toolkit available. i only see everyone benefit here.
i dont work for troll^H^H^H^Hnokia, i do code some kde app, i did try gtk and gnome development and based on experience with the two of then decided to develop my app on qt/kde as it develops a lot faster for me.
hahahahaa! qt is not dark, " [/q]
Read again, he was talking about the OLPC, and by dark side he meant windows.
i dont see any underlaying advantages. if you want to write a freesoftware app with qt its cool and free. if you want to write a commercial app you pay a little (yes it is not much taking in to regard what the developer cost are for a commercial app). "
Don't have to tell me. I even own a Qt commercial license. But the GTK license is still an advantage over Qt. It just happens to be that it's not enough of an advantage to convince me to use it.
i dont see any underlaying advantages. if you want to write a freesoftware app with qt its cool and free. if you want to write a commercial app you pay a little
If you want people writing software for your platform, that pretty much sucks, because you are alienating a large userbase that doesn't wish to publish their code under the GPL and has no intention in purchasing a Qt License.
RE[2]: Where now for Gnome Mobile?
This is quite common, sadly. When VLC switched to Qt for their main interface because of the cross-platform benefits (right-to-left languages for one) and because VLC is a real cross-platform open source application, the usual objections of licensing (VLC is still GPLed anyway) and the use of C++ were wheeled out.
People totally misunderstand C++, and have misunderstood a lot of comments people like Linus Torvalds have made about it. There's nothing wrong with C++ itself, but as an object-oriented language you inevitably find yourself using a library like Boost or the STL. This is where pretty much all the problems come from.
I think the problem rather comes from the fact that you can program in C++ for ten years but still have a hard time taking over code from an C++ developer that has been using it for fifteen years.
There is such a thing as too much complexity and too much freedom. C++ has its uses, but imho application development isn't one of them anymore these days.
I do agree that those ditching a project like OpenMoko for such a switch is an overreaction. You can still keep programs simple, the problem arises if you get that kind of C++ developer on the project who is complicating things for the sake of bragging.






Member since:
2005-09-21
I dunno if that's the case. They've certainly said that they won't be switching to Qt on Maemo. Just making Qt more well supported there. I don't think anyone particularly feels like rewriting the existing GTK code.
Probably not. GTK has its advantages (the license for example). But when it comes to getting stuff done, it seems the openmoko people have decided that Qt is the better way to go. Of course if the community pours a lot of effort into bringing the GTK apps up to snuff then that could change.
I thought it was funny that in that thread, one of the responses was from someone that was so fundamentally opposed to C++ (claiming it is completely unusable) that he immediately rejected the whole openmoko project based on this switch. I can't see how anyone with such a closed, unyielding mind can call themselves a developer.