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 377171
To view parent comment, click here.
To read all comments associated with this story, please click here.
segedunum
Member since:
2005-07-06

Certainly that should exclude KDE from government agencies and the bulk of private companies.

Is it any wonder that the wider computing world thinks that a lot of people touting open source desktops are a bunch of masturbating monkeys? There's nothing more hilarious when you see someone absolutely steadfast in their belief that a new lick of paint on the poop deck is what's needed as water gushes in through a gaping hole below decks.

Government agencies, and especially private companies ((!) What planet are you on?), use totally inaccessible applications and set ups all the time. Why? Because they have functionality that they want. If you start touting something to them that cannot run those applications, and has no developer base whatsoever to provide them, then you'll get drop kicked out of the door before anyone even thinks that accessibility is an issue. Organisations cross accessibility bridges when they come to them, and they do it by buying in software most of the time. Now where's that potential developer platform................? There's no guarantees and there's a lot of work to do, but KDE as a default desktop cannot make the situation any worse on that front.

Has SLED or any other 'enterprise' Linux distribution's total inability to gain any traction whatsoever not sunk in anywhere? Something has to give sooner or later.

In fact, I'm wondering how any Linux distro which claims to support freedom and equal opportunity for users could default to it in good faith until such time as that issue is resolved.

1. Because he's wrong.

2. Trying to deny the inevitable and claim that we need to keep rearranging deck chairs in the meantime is not going to get OpenSuse, SLED or desktop Linux anywhere.

But........we've had this brain dead nonsense for the best part of a decade now.

Edited 2009-08-05 12:04 UTC

Reply Parent Score: 2

sbergman27 Member since:
2005-07-24

There's nothing more hilarious when you see someone absolutely steadfast in their belief that a new lick of paint on the poop deck is what's needed as water gushes in through a gaping hole below decks.

Oh, KDE4 has the water gushing in through a gaping hole below decks, as well. I certainly haven't missed that. The poop deck paint simply happens to be the topic of this thread. And it needs that too.

Regarding your claim that Darknexus is wrong... please present some evidence. Darknexus, who needs and uses these kinds of facilities everyday (and whom I've usually found to be fair on these matters) has a hell of a lot more credibility than you do (whom I've often found to be a bit of a shill). Stop your desktop cheerleading for long enough to actually think for a bit about real users who need accessibility.features.

Edited 2009-08-05 12:21 UTC

Reply Parent Score: 2

segedunum Member since:
2005-07-06

Regarding your claim that Darknexus is wrong... please present some evidence.

Try reading. It usually helps. Here's a summary:

1. He claims that Qt doesn't support AT-SPI. It does.

2. Qt 4 supports the newer D-Bus AT-SPI interfaces. This project has been in existence for around three years. Gnome and GTK are still stuck with CORBA usage and haven't done enough work to update to it. I really can't imagine why they'd drag their heels.... This is seemingly a problem when it comes to compatibility between different applications (no surprise there) such as Orca - which is the root issue he seems to be driving at - and he's got the impression that that is all KDE and Qt's fault. I can't imagine why.

3. Simply supporting AT-SPI doesn't mean that you are 'accessible'. You need magnification, developer support, transparent application support, device support, guidelines........ You also need other organisations filling the gap with their own software. I can't imagine where he's got the impression that simply supporting AT-SPI and having it work with some Gnome/GTK applications meets some supposedly hard prerequisite for getting your software used.....anywhere. Puzzling.

Darknexus, who needs and uses these kinds of facilities everyday (and whom I've usually found to be fair on these matters)...

All he probably knows is that his software doesn't work. We need to find out why ;-).

Stop your desktop cheerleading for long enough to actually think for a bit about real users who need accessibility.features.

I realise that it's a tough chew to swallow...... The time for politics over who supports what is finally going to come to a close at some point in KDE 4's cycle in favour of straight comparisons between open source desktops and the proprietary competition. Straight jackets at the ready. I can't wait to be honest. We've seen this incessant crap for nearly ten years now.

Alas, it's probably not a PC thing to say but the userbase coming off the back of accessibility and for applications like Orca is very small and there is limited manpower when compared with what needs doing. Banging on about a single area won't increase open source desktop usage, and it hasn't. You need application and developer support and with that accessibility gets dragged along. That's how companies like Dolphin make a wide variety of add-on accessibility products. Until that support starts happening then arguing about who's more 'accessible' just sounds plain sad.

Reply Parent Score: 2