On Monday, OSNews had the pleasure of talking face to face with Trolltech's CEO and founder, Haavard Nord. Mr Nord discussed with us the new features found in Qt 3.3 (download, changes, announcement), Qtopia and the arising market of Linux in mobile phones as well as in the business computer market. Update: ITManagersJournal hosts a Trolltech article as well.
Permalink for comment
To read all comments associated with this story, please click here.
I'll pretty much agree with you on your points only to add that as other have stated, the QT# bindings were a major pain because of the whole virtual functions problem in c++. I'm not compiler wiz, but saw a couple posting by Adam(who was the first guy to work on qt#) on the GCC mailing list to see if anybody could give him any hints to go about. I guess if the ABI were stable, then you could've does some hackery with vtables, but like I said, I'm not compiler expert.
The KDE developers never had a problem with qt# or kde# bindings. There's still a link to the qt# page at developers.kde.org. I'll agree that c++ takes away many of the advantages that wrapping gtk+ up in a managed language gives you over straight c and gtk+, but I'll say that writing little irc clients in c++ probably isn't an optimal use of developer time, even though the KDE framework is great.
I've said it before many times, and Eugenia even wrote it up in an article - writing your average Gnome app(I'm not talking core libraries here) in straight c in 2004 reminds me of assembler programs i would talk to in 1997 that refused to migrate to c. To each their own obviously, but at some point you have to move on.
As far as win developers - year, I don't think there's a win developer on the planet that is going to lose sleep over the win32 api and MFC going the way of the Dodo bird.
I'll pretty much agree with you on your points only to add that as other have stated, the QT# bindings were a major pain because of the whole virtual functions problem in c++. I'm not compiler wiz, but saw a couple posting by Adam(who was the first guy to work on qt#) on the GCC mailing list to see if anybody could give him any hints to go about. I guess if the ABI were stable, then you could've does some hackery with vtables, but like I said, I'm not compiler expert.
The KDE developers never had a problem with qt# or kde# bindings. There's still a link to the qt# page at developers.kde.org. I'll agree that c++ takes away many of the advantages that wrapping gtk+ up in a managed language gives you over straight c and gtk+, but I'll say that writing little irc clients in c++ probably isn't an optimal use of developer time, even though the KDE framework is great.
I've said it before many times, and Eugenia even wrote it up in an article - writing your average Gnome app(I'm not talking core libraries here) in straight c in 2004 reminds me of assembler programs i would talk to in 1997 that refused to migrate to c. To each their own obviously, but at some point you have to move on.
As far as win developers - year, I don't think there's a win developer on the planet that is going to lose sleep over the win32 api and MFC going the way of the Dodo bird.