Linked by Thom Holwerda on Tue 26th Feb 2008 15:08 UTC, submitted by masalinger
Thread beginning with comment 302594
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2005-07-22
if they just wanted good technology, why not take advantage of KDE and Qt?
You're not comparing like with like.
Qt is a cross-platform toolkit, and Mono is a runtime which supports multiple programming languages as well as C#. GTK+ and other Gnome libs form a cross-platform toolkit and it makes perfect sense to complare that with Qt.
You can write Qt apps in Java via the excellent QtJambi bindings, and you can write Qt apps in Mono/C# via the Qyoto bindings (with Kimono the KDE superset coming in KDE 4.1).
Mono isn't part of Gnome and has no dependencies other than the GTK# bindings. Those bindings don't make Mono part of Gnome any more than the Qyoto/Kimono bindings make Mono part of KDE.
Obviously there are some nice apps written in GTK#, but they are all optional and none of the core Gnome libs depend on Mono. In the same way none of the core KDE libs depend on any language other than C++ which is fine, as C++ is a great language for writing libs.
The more Gnome or KDE applications (as opposed to libs) which are written in non C/C++ languages, the better as far as I'm concerned, as they are too hard to learn for most people, particularly casual programmers. If Mono helps use break away from needing to write apps in such primitive languages, that is all to the good in my opinion.