KDE Adopting Mono
leandrod writes "The Register reports that members of KDE are committing to use and support mono, Ximian's independent .Net implementation. Not only does this provide KDE with some of the multilingual programmability it initially forfeited by its use of Qt, it also spells well for cross-desktop application and even KDE-Gnome desktop integration, because mono is developed by Gnome's most prominent ISV, Ximian, and is intended for Gnome integration." Update: 09/12 14:22 GMT by T : Actually, the Register story overstates things a bit, it seems. According to KDE developer Hetz Ben Hamo (heunique), "Yes, you can use QT# to write QT/KDE apps, but it doesn't mean that KDE will support mono. you can use kernel 2.4, but you can use any linux kernel or any other unix based OS." See also this comment from David Faure for more insight.
I wrote a small maintenence application, and compiled it targeting non-.NET Win32, the file was 19 meg.. ok, yeah, it's probably got the runtime in there... a similar java runtime is 7 or 8 meg.
KDE is also going to suffer from a similar rash of programmers like windows VB programmers who thing that dragging and dropping an application together makes them every bit as valuable as someone who can lovingly craft inline assembler into their C routines for speed and keep an eye on memory utilization. The dot.bomb shakeup was good for scaring those VB types out of the industry for a bit, but MS is still trying to sway focus over to "productivity" over stability or longevity.
Yeah i know i'm ranting, but i've got mana to burn.
You are right. I tried to correct some of Gavin's statements such as: 'Qt is a language'
:-)
LOL, but I was in the middle of dinner when he called and he didn't have time to wait...
KDE is not 'switching' to Mono nor has KDE 'adopted' Mono, but some developers are attempting to include support for Mono in KDE. That's it. It is a another choice for the developer and IMHO a very _cool_ choice
Cheers,
Adam
Ah, so the interview was done over the phone and you had no way to check the printed version before it went online? That's very bad IMHO, they should check with the person interviewed first. That's how misunderstandings happen - such as this one.
The article was already very misleading IMHO, the slashdot headline even more so. I think many more statements should have been corrected in that article...
Well, thanks for the work on the language bindings, keep it up.
David Faure.