Language Selection

English French German Italian Portuguese Spanish

What I wish I'd read months ago about KDE3 vs. KDE4

If a certain (suspected) spambot had not resurrected an old thread at the KDE forums, I never would have seen this post from Aaron Seigo's blog which completely ended all of my anxieties about KDE4 finally and for the foreseeable future. It's all here. And I quote:

Meme 1: What is the future of 3.5?

This year, as with most years since KDE3 emerged, there have been huge deployments of KDE 3 based software. These deployments will not shift for years to come, no matter what KDE4 is. This is because large institutional deployments (government, corporate, educational, etc) typically have 3-7 year cycles (sometimes even longer) between major changes. Patches and security fixes? Sure. Major revamps? No. This alone ensures that KDE3 will remain supported for years. Why? Because there are users. That is how the open source dev model works: where there are users, there are developers; as one declines so does the other. The developers tend to be a step ahead of the users for software that is progressive, but you'll also find that they have a foot in the here and now too (as well as the past, often).

KDE3 is still open in our svn so that bug fixes, security fixes, etc. can continue to be made. KDE 3.5.x is a rather solid desktop system and really doesn't need a huge amount of work given what it is today; the work to move it to the next level is what we refer to as KDE4, of course. This means that the efforts needed to put into it aren't huge to keep it viable. However, efforts that do go into it are welcome.

While the core KDE team will continue to concentrate our work on KDE4 since that is the long term direction of things, it is fully expected that our partners (which include some KDE core team members as employees/members) will continue supporting and even developing on KDE3 issues. The central project will also be around to lend a helping hand with advice and what not; I did that for a person the week before I left for holidays in December, actually, so it's not wild hypothesis but solid theory.

For those familiar with the open source method, the above probably sounds .. well .. obvious. That's because it is .. for those familiar with the open source method. We will find in this blog entry that many of the concerns people raise come from not acknowledging how Free(dom) software is created via the open source method.

Really? And thanks for helping us out with that. For months I've been going out of my freaking mind, posting angrily, trying to get a handle on where KDE3 was going. And there has always been a fairly clear, black and white answer that we weren't hearing. KDE could have done a better job of getting this information out. Judging my my own case, I think that this has been the source of a lot of discord between developers and users, not KDE4 not being ready. In all of the general whining and bitter accusations-- anyone who didn't like KDE4 was accused of being a secret gnome-lover-- and (now clearly unnecessary) fork proposals, I don't remember anyone from KDE saying that KDE expects to maintain KDE3 for years! I would have put down my pitchfork and extinguished my torch... as I do now.

Ah well. Possibly, the KDE team doesn't excel at Public Relations, but I can see know that they're handling the development part exactly right. I don't prefer KDE 4, by which I mean I don't prefer all the versions of KDE4 I've tried up to now, and I'm not really interested in trying any more for a while. But KDE3.5 is alive and well. It's now in "maintainance mode", and that's all that KDE3 users can ask, in my opinion. KDE4 is where the development is happening, and development is the business of developers. We users may wish for a little constancy, but the developer's job is to look toward the future. To me, the surprise ending to the conflict may be that everybody wins.

More in Tux Machines

Android, Android on Desktops (Android-x86), Samsung Galaxy on Desktop/DeX

  • Pixel 2 Has Screen Burn-In Problem, Google Says They’re “Actively Investigating” The Report
    Android Central has reported that their Pixel 2 XL review unit is having screen burn-in issues. That’s a bad thing for the latest made-by-Google flagship which was announced earlier on October 4, ditching the headphone jack.
  • Android-x86 7.1-rc2 Now Supports NVMe SSDs, Better QEMU VirGL
    The Android-x86 project derived from Google's Android Open-Source Project code-base remains officially at Android 6.0, but there is an Android 7.1 "Nougat" build available for testing. Quietly released earlier this month was a second release candidate based on Android 7.1. The Android-x86 7.1-RC2 release is based on upstream AOSP 7.1-RC2 / Nougat-MR2 along with some extra improvements for this x86-targeted build.
  • What To Do When The Power Button Of Your Android Phone Is Broken?
  • Samsung is adding Linux support for DeX with the new ‘Linux on Galaxy’ app
    Since Samsung debuted the DeX feature earlier this year with the Galaxy S8 and Galaxy S8+ smartphones, the company has been making small changes to improve the whole experience of using your smartphone as a PC. In order to further enhance Samsung DeX, the company has announced “Linux on Galaxy”, an app that will let developers run Linux-based distributions on their mobile device, allowing them to code on-the-go. The app is DeX-enabled, which means developers can code on a bigger device, powered by their Galaxy S8, Galaxy S8+ or Galaxy Note8.
  • You can run any Linux distro on Samsung smartphones using Linux with Galaxy App
    The convergence of a smartphone with a PC/laptop is not new and has been in making for several years. In fact, the idea of such a convergence started with Nokia’s Communicator phone launched in 1996 when it was the undisputed king of feature phone and mobile phone arena. Ubuntu devs tried a similar theme with the now-dead Ubuntu for smartphones and tablets. The Ubuntu os was launched with the idea to run full Linux apps on your smartphone. The smartphone even gave users an option to connect a keyboard, mouse, and display. However, that did not sell.

Linux Foundation Announcements: CIP, OpenMessaging, CDLA

  • Civil Infrastructure Platform Announces the Release of CIP Core
    Hosted by The Linux Foundation, CIP addresses the needs of long-term software for the power generation and distribution, water, oil and gas, transportation and building automation industries. CIP members such as Codethink, Hitachi, Plat'Home, Renesas, Siemens and Toshiba are working to create a reliable and secure Linux-based embedded software platform that can be sustained more than 10 years and up to 60 years.
  • Linux Foundation Launches OpenMessaging Project
    ​Through a shared exertion bnb m from endeavors and groups put resources into the cloud, enormous information, and standard APIs, I'm eager to welcome the OpenMessaging project from The Linux Foundation. The OpenMessaging group will likely make a comprehensively embraced, merchant impartial, and open standard for dispersed informing that can be conveyed in the cloud, on-commence, and half and half utilize cases.
  • Linux Foundation Debuts Community Data License Agreement
    he Linux Foundation, the nonprofit advancing professional open source management for mass collaboration, today announced the Community Data License Agreement (CDLA) family of open data agreements. In an era of expansive and often underused data, the CDLA licenses are an effort to define a licensing framework to support collaborative communities built around curating and sharing "open" data.
  • The Linux Foundation Releases Three New Open Source Guides for the Enterprise
    The Linux Foundation, the nonprofit organization enabling mass innovation through open source, has released the next three in a series of Open Source Guides for the Enterprise, created to help executives, open source program managers, developers, attorneys and other decision makers learn how to best leverage open source. These three new guides add to the six released last month at Open Source Summit North America.

openSUSE Tumbleweed Linux OS Patched Against WPA2 KRACK Bug, GCC 6 Now Removed

If you're using the openSUSE Tumbleweed operating system, you should know that one of the latest snapshots removed the GCC (GNU Compiler Collection) 6 packages from the default install and patched it against the WPA2 KRACK security vulnerability. Read more

Librem 5 Linux Phone to Include Nextcloud's End-to-End Encrypted File Storage

Purism and Nextcloud announced partnership to bring Nextcloud's end-to-end encrypted file sync and sharing services to Purism's mobile and desktop computing products Read more Also: Librem 5 Privacy-Focused Linux Phone Crowdfunding Campaign Ends with $2 Million Nextcloud to be available on 'free' smartphone