Linked by Thom Holwerda on Tue 4th Aug 2009 10:43 UTC
SuSE, openSUSE SUSE Linux used to be a very KDE-centric distribution. Then Novell came around, bought SUSE and Ximian, and slowely but surely they turned the now-openSUSE distribution into effectively a GNOME-centric distribution with KDE as its sidekick. The openSUSE community, however, doesn't appear to be particularly happy with KDE being a sidekick.
Thread beginning with comment 376893
To read all comments associated with this story, please click here.
KDE4 and Novell... like oil and water
by darknexus on Tue 4th Aug 2009 16:23 UTC
darknexus
Member since:
2008-07-15

Given NOvell's Ximian investment, plus their 100% backing of Mono, I don't see them moving to KDE anytime soon. There would be too much involved really to move to it, as a good deal of Novell's other technologies would have to have more bindings and the like for KDE and would have to go through an extensive testing period. It would be more trouble for NOvell than it would be worth, considering that OpenSUSE is to SLED as Fedora is to RHEL. Sled is not going to move to KDE, so neither will OpenSUSE.
Too, given they have several developers employed to work on accessibility features such as those for Mono and other GNOME technologies, it wouldn't make sense from that perspective either... and if they ever hope to have U.S government contracts, they need to keep their system accessible (or at least accessible enough). KDE would be a non-starter when you add that into the equation on top of everything else already.

Reply Score: 5

segedunum Member since:
2005-07-06

Given NOvell's Ximian investment, plus their 100% backing of Mono, I don't see them moving to KDE anytime soon.

Show me the money, as they say. Despite Novell's much vaunted support of Mono I don't see it used very much at all in any of Novell's administration tools or development kits across their range of paying products. They might have written some stuff for .Net on Windows but that's not the same thing. It just seems to be a vain, hopeful addition so that some people will move their .Net applications and run Novell's Linux, and few of those will need GTK, Gnome and GTK#. They've written a music player, a photo application and a soon-to-be completely replaced indexing and search system with it and that's about it. I'm sure Novell, GTK and Gnome would survive without those things.

Mono has bought them very, very little.

There would be too much involved really to move to it..

They already do use it and it already is supported because they ship it. They also still support SLES and other customers where it certainly was the default. There's little to tie Novell to Gnome because they have a pretty much non-existant developer and application base with it. One might ask why.

...and would have to go through an extensive testing period.

They already ship it, have done for years and that testing process is already in place. What's being discussed here is a default for focus given the stagnation that we have right now. That's a different thing.

Sled is not going to move to KDE, so neither will OpenSUSE.

SLED is an insignificant little enterprise desktop distribution that isn't raking in any money because there is no differentiator and nothing to get excited about whatsoever. Do the maths.

...and if they ever hope to have U.S government contracts, they need to keep their system accessible (or at least accessible enough). KDE would be a non-starter when you add that into the equation...

Why would that be when KDE 4 and Qt 4 supports ATK/AT-SPI? I always have a bit of a chuckle when people start scraping the barrel for things like accessibility, which while certainly important, is a fairly insignificant piece of the jigsaw when compared with what your desktop actually does.

People care about what your desktop does, and that means functionality and applications. If you don't have those things then nobody wants to use you and that's a far bigger mountain to climb than any accessibility regulations.

Edited 2009-08-04 22:30 UTC

Reply Parent Score: 1

darknexus Member since:
2008-07-15

Excuse me, but I think I have more experience with accessibility than you do given that I use it on a daily basis.
QT claims to support ATK/AT-SPI. However, Trolltech at the time of QT4's inception decided to communicate with at-spi over the Dbus protocol... which, naturally, at-spi of course didn't support and still doesn't (at-spi uses CORBA). There is work happening on this, but who knows when, or if, it will be completed. Meanwhile, QT4 apps are just as inaccessible as they always were and just as inaccessible as QT3 before them.
I do not like being called a liar, particularly by someone whose facts are blatantly misleading. This isn't the first time you've made these half-truths either. You love QT and KDE, good for you. I might love them too, if they were of any use to me. But do not misrepresent the current situation just because you like one environment and toolkit over the other.

Reply Parent Score: 3