Language Selection

English French German Italian Portuguese Spanish

The critics are wrong: KDE 4 doesn't need a fork

Filed under
KDE

After the recent release KDE 4.1 beta 2 and openSUSE 11 with KDE 4.0.4, some critics have been especially vocal in expressing their displeasure with the KDE 4 user interface paradigms. The debate has grown increasingly caustic as critics and supporters engage in a war of words over the technology. The controversy has escalated to the point where some users are now advocating a fork in order to move forward the old KDE 3.5 UI paradigms. As an observer who has closely studied each new release of KDE 4, I'm convinced that the fork rhetoric is an absurdly unproductive direction for this debate.

As KDE 4 begins to replace the stable 3.5.x series as the default KDE environment in major distributions, users who are now migrating to the new version are being exposed to a lot of the rough edges. This has ignited a new wave of complaints.

Steven singles out KDE 4.1's desktop folder view plasmoid for criticism, but I regard it as one of the most promising features in KDE 4.1. In fact, I think the new desktop folder view offers some of the first truly compelling evidence that Plasma can deliver on its potential and provide more than just a conventional widget layer. I think it's innovative and it increases the efficiency of my workflow.

The value of conventional desktop icons is that they allow users to organize their files into spatially relevant groupings. But most users just treat the desktop as a dumping ground for temporary content because moving things to and from the desktop requires more interaction and isn't always feasible if you need your project to have a consistent path.

More Here




Too soon to tell.

I used to dislike it, even hate it, but since I installed openSUSE 11, I have decided that it's awful, terrible, just a train wreck, but when I think something is terrible, I usually turn out to be wrong. That's just my track record. I could point to my infamous anti-ubuntu rants from not too long ago. I like Ubuntu fine now.

People who like it probably get it, and I don't get it. I've spent a lot of time running it now, several different versions. People talk about how KDE4 simplifies the desktop, and I am astounded at that. "Simple" is the last word I would ever use to describe KDE4. What do they see that I can't? All I see is an incomprehensible mess. This is why I don't submit bug reports. I don't feel like I understand it enough to be sure that when my YAST repeatedly crashed, it wasn't my fault. (Although it stopped crashing when I installed KDE 3.5.)

If this turns out to be the odd time that I'm right, KDE will be forked, because there will be a need. No need to debate it in blogs, it'll just happen, because it will be necessary. In the past there hasn't really been a need, which is why previous attempts to fork KDE failed. And since I'm usually wrong, this is probably what's going to happen this time.

Anyway, it's too soon to tell if we need a fork, and too soon to tell if we don't need a fork. That's the long and the short of it. We don't have the actual finished desktop, so what we have is a lot of speculation, and it all sounds canned and forced, bloggers trying to stir up controversy and other bloggers trying to squelch controversy. None of it is based on the finished software. That doesn't exist.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Red Hat and Fedora

  • Is there need for Red Hat Certification training in Zimbabwe?
    A local institution is investigating the need to train Systems Administrators/Engineers who use Linux towards Red Hat certifications. The course is targeted at individuals with at least 2 years experience using Linux.
  • Red Hat, Inc. (NYSE:RHT) By The Numbers: Valuation in Focus
  • Fedora @ Konteh 2017 - event report
    This year we managed to get a booth on a very popular student job fair called Konteh. (Thanks to Boban Poznanovic, one of the event managers)
  • Fedora 26 Alpha status is NO-GO
    The result of the second Fedora 26 Alpha Go/No-Go Meeting is NO-GO. Due to blockers found during the last days [1] we have decided to delay the Fedora 26 Alpha release for one more week. There is going to be one more Go/No-Go meeting on the next Thursday, March 30th, 2017 at 17:00 UTC to verify we are ready for the release.
  • Fedora 26 Alpha Faces Another Delay
    Fedora 26 was set back by a delay last week and today it's been delayed again for another week. Fedora 26 Alpha has been delayed for another week when at today's Go/No-Go meeting it was given a No-Go status due to outstanding blocker bugs.

GNOME News: Gtef, GNOME 3.24 Release Video, Epiphany 3.24

  • Gtef 2.0 – GTK+ Text Editor Framework
    Gtef is now hosted on gnome.org, and the 2.0 version has been released alongside GNOME 3.24. So it’s a good time for a new blog post on this new library.
  • GNOME's GTK Gets Gtef'ed
    Developer Sébastien Wilmet has provided an overview of Gtef with this text editing framework having been released in tandem with GNOME 3.24. Gtef provides a higher level API to make it easier for text editing or in developer-focused integrated development environments.
  • The Official GNOME 3.24 Release Video Is Here
    By now you’re probably well aware that a new update to the GNOME desktop has been released — and if you’re not, where’ve you been?! GNOME 3.24 features a number of neat new features, welcome improvements, and important advances, most of which we’ve documented in blog posts during the course of this week.
  • A Web Browser for Awesome People (Epiphany 3.24)
    Are you using a sad web browser that integrates poorly with GNOME or elementary OS? Was your sad browser’s GNOME integration theme broken for most of the past year? Does that make you feel sad? Do you wish you were using an awesome web browser that feels right at home in your chosen desktop instead? If so, Epiphany 3.24 might be right for you. It will make you awesome. (Ask your doctor before switching to a new web browser. Results not guaranteed. May cause severe Internet addiction. Some content unsuitable for minors.)

today's howtos

AMDGPU Vega Patches and AMD Open-Sources Code

  • More AMDGPU Vega Patches Published
    Less than one week after AMDGPU DRM Vega support was published along with the other Vega enablement patches for the Linux driver stack, more Direct Rendering Manager patches are being shot out today.
  • AMD have announced 'Anvil', an MIT-licensed wrapper library for Vulkan
    AMD are continuing their open source push with 'Anvil' a new MIT-licenses wrapper library for Vulkan. It's aim is to reduce the time developers spend to get a working Vulkan application.
  • AMD Open-Sources Vulkan "Anvil"
    While waiting for AMD to open-source their Vulkan Linux driver, we have a new AMD open-source Vulkan project to look at: Anvil. Anvil is a project out of AMD's GPUOpen division and aims to be a wrapper library for Vulkan to make it easier to bring-up new Vulkan applications/games. Anvil provides C++ Vulkan wrappers similar to other open-source Vulkan projects while also adding in some extra features.