Slashdot Mirror
KDE Responds To Misconceptions About KDE 4
Jiilik Oiolosse writes "PJ at Groklaw speaks with a member of the KDE team about some of the common myths circulating about KDE 4. 'There has been a bit of a dustup about KDE 4.0. A lot of opinions have been expressed, but I thought you might like to hear from KDE. So I wrote to them and asked if they'd be willing to explain their choices and answer the main complaints. They graciously agreed.' Among the topics discussed are: 'Releasing KDE 4.0 was a mistake,' 'I cannot put files on my desktop,' and 'KDE should just have ported KDE 3.5 to Qt 4 and not add all that other experimental stuff right away.'"
I've always preferred KDE over Gnome, but unlike many I didn't rush to install KDE 4.0 (what with it being an incomplete beta and all.) I didn't get XP until it had been out for years either, and by the time I'm considering Vista it'll be lying in a shallow grave from the sound of things.
Basically, I see KDE 4.x as something to play with alongside my regular desktop. I'll jump onboard properly when things calm down, but in the meantime I have work to do.
Hal Spacejock: Science Fiction with Nuts
I'am not so sure if the Apple GUI experience can be described as superior. I have a Mac Mini with dual boot into OS X and Linux with KDE 3.5 on top. Overall I think OS X looks cooler and more professional designed, but from a usage and efficiency point of view into the KDE environment better fits my needs.
...
For instance:
o The Alt+Tab vs. Alt+Tilde thing - I understand the technical difference between switching applications and multiple "documents". Still I often have the case where I have 2 Terminals and 1 Firefox open and need to constantly switch between them. Here I don't want to think about if it's another application or document I want to switch between. I just want to do it and I can with KDE, Gnome, Windows, OS/2 but not OS X. Ok there is an extra tool (forgot the name), but that one didn't work flawless eather.
o Virtual Desktops - Well that something a lot of Nerds seemed to miss, something which the OSS community had in their products for years. Not having it can result in considerable clutter on the screen which is exactly how my OS X screen looks like. Great to see that Apple finally came around and introduced it in it's latest version.
o Zoom vs. Maximize - One IMHO really strange thing in OS X is the Maximize button which actually is a Zoom button. The window size gets proportionally increased until it reaches the horizontal or vertical limits - whatever comes first. It's not possible to really maximize a window to cover the entire screen. Exception to that being that applications can alter this behavior and e.g. Aparature is doing so - showing the same behavior as this botton does in KDE, Gnome, Windows, OS/2,...
o Resizing a Window - To resize a window you have to drag the lower right corner and only the lower right corner. Why can't I use the left side border of the window if I choose to? Also something that's possible nearly everywhere else.
o Focus follows mouse -
o Rename a file - You can do tons of things (like copy, move to trash,...) within the context menu of a file. But still you can't rename it. Instead you have to click on it once and then again on the name below the icon. I find this quite inconsequent and also not very intuitive - actually I had to google it.
o Consistent UI appearance - It's true that Qt, GTK etc. based applications look different. But so do OS X applications where you have the white style, this brushed metal style and another one which escapes me right now.
So don't get me wrong, I didn't want to rant about OS X. It's my favorite UI from a design and "looking at" point of view. But if it's about daily work with it, then points like the mentioned above are really in my way. With KDE it's vice versa for me. It doesn't look that good, but I lets me do the job and it's more consistent with what you would expect coming from other UI's.
Why, yes I know. Don't feed the trolls... I just can't resist here.
That would have helped so tremedously! It would have made clear to trolls and dumb people that it is not for them and real FOSS lovers would have still tested it and filed bug reports and feature request.
So I'm dumb or a troll for feeling let down when a stable release (which a 4.0.X release should be) of a major open source project tends to crash on me constantly? In the FLOSS community, release management has a lot to do with honesty.
If your 4.0 branch has scathing architectural deficiencies that make it unusable for production environments, call it 3.9, if you already had that, call it 3.10. Now KDE has their own gnome 2.0.0. Anyone who remembers that one awful experience?
Naming convention for the future:
*Insert big FOSS project X.0 ( X > 1 )* "Developer Release"
Otherwise all the dumb users will think it is Photoshop CS4 or something.
IMHO that is the path to happiness!
BTW KDE4.1 ROCKS!
If it's not 4.0 don't call it 4.0 -- it's that simple.
Well, to be fair, calling it KDE 4.0 suggests it's relatively bug-free (else it would have been 4.0-beta), and feature-complete (else it would have been 4.0-alpha).
From what I've read it was neither of those...
this sig has intentionally been left blank
Many people uphold OSX or Vista as the pinnacles of desktop beauty, and in the case of Mac, usability and user experience, yet the beauty possible on modern Linuxen desktops is not only equal to that of the Big Two, but in fact far surpassing them. Yes, I am talking a lot about "beauty" and "aesthetics", terms that programmers and techheads usually spurn or dismiss as irrelevant or superfluous. However, because it is not in the front of many geeks' minds does not mean it is irrelevant (especially considered I being a programmer myself) - beauty is important! In KDE, in particular KDE4, and especially coupled with technologies such as Compiz-Fusion and/or Metisse, the Linux desktop is far ahead any competition in presentation aesthetics, a fact seldom recognised.
That said, I am not using it on my production system and will not until release 4.2.
The problem as I see it, and the mistake made by the KDE dev team, lies in using a version numbering system that makes great sense for them but has little relation to how it will be interpreted and understood outside the development circles. For the devs, according to TFA, the "4.0" in KDE 4.0 means
For most of the world, the release of a new major version means both something new and exiting, which KDE4.0 certainly delivers, but also a finished and usable system that will be refined, embellished and updated. The KDE devs, on the other hand, means it as a platform on which a functioning system can and will be built. Their mistake lies in not realising that public perception of "4.0" would differ from their intention.
That said, this is a very common mistake in all human communication. Seldom indeed does intention transmit perfectly into perception.
If anyone was wondering why KDE 4 was so user unfriendly, then this article pretty much says it all. None of the answers are user friendly. They are all argumentative and poor excuses at best.
KDE 4.0 is the starting line, not the finishing line.
Isn't that the precise definition of BETA software? They released KDE 4.0 Beta as the finished product, and are now ARGUING that it is not finished, but a "new beginning." Well, thanks for telling us beforehand, which btw would have been as simple as adding "beta" to the name. If 4 is so backward compatible and "user friendly" then why have so many users failed to "make use" of KDE 4? If they listen to their users, then why do they feel they haven't been heard? If you disagree with them then fine, but you cannot argue with them and expect to win anyone over and claim that that is listening.
Why, exactly, is it surprising that, when the product is announced to be "out of beta and released", it will be pushed out to end users?
If it's not "objectively ready", then it's not even beta, it's alpha. If the libs are ready but not the desktop itself, then release "kdelibs-4.0", and keep the version of the desktop itself at alpha until that part is finished.