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

SF’s Elections Commission asks mayor to put $4M toward open source voting system

While the Elections Commission may be among the least followed city bodies, the seven members are playing a critical role in determining whether San Francisco will begin to use an open-source voting system. For years, open-source voting advocates have called on San Francisco officials to part ways with traditional voting machine companies. Open-source voting is widely considered the best defense to voter fraud with the added benefits of cost savings and flexibility. Much to chagrin of these advocates, The City has continued to sign contracts with nonopen-source voting companies. While no open-source voting system has been deployed elsewhere, other jurisdictions are currently working on it, such as Travis County, Texas. After The City allocated $300,000 in the current fiscal year to move San Francisco toward an open-source voting system, the effort has gotten off to a slower-than-expected start. Advocates worry if funding isn’t committed to building out such a system, the effort will face further delays. Read more [Ed: Microsoft a threat]

KaOS 2017.02

KaOS is proud to announce the availability of the February release of a new stable ISO. The policy is, once a first pacman -Syu becomes a major update, it is time for a new ISO so new users are not faced with a difficult first update. With the exceptional large amounts of updates the last four to five weeks a new ISO is needed a bit sooner than usual. As always with this rolling distribution, you will find the very latest packages for the Plasma Desktop, this includes Frameworks 5.31.0, Plasma 5.9.2, KDE Applications 16.12.2 & not yet released ports of KDE Applications. All built on Qt 5.8.0. Read more

Linux Kernel News

  • Linux 4.11 Adds EFI Memory Attributes Table Support
    The (U)EFI support continues to evolve within the Linux kernel and with the 4.11 release will be new and improved functionality.
  • Security Changes Bring Major AppArmor Update, Better TPM 2.0 To Linux 4.11
    James Morris has filed the security subsystem feature updates targeting the Linux 4.11 merge window. Changes to the security-related components in the kernel include a major AppArmor update with policy namespaces support and many fixes, /sys/kernel/security/lsm now makes it easy to show loaded Linux Security Modules, SELinux updates, and improved TPM 2.0 support.
  • Linux 4.10 arrives
    With more than 13,000 commits, the release of Linux 4.10 was not as small at Linus Torvalds was expecting. Nonetheless, it arrived over the weekend, bringing with it significant changes, such as the introduction of support for virtual GPUs.
  • Linux Kernel 4.10 Released -- Happy Anniversary!
    Kernel 4.10 has the honor of being christened the "Anniversary Edition" by Linus Torvalds. I'm guessing this is because of the recent 25th anniversary of the release of Linux 0.01. Admittedly, it is a bit late for that (the anniversary was back in September); however, Linus had not named any of the recent releases for the occasion, opting instead for naming them after several deranged animals.
  • Collabora Contributions to Linux Kernel 4.10
    Linux Kernel v4.10 is out and this time Collabora contributed a total of 39 patches by 10 different developers. You can read more about the v4.10 merge window on LWN.net: part 1, part 2 and part 3. Now here is a look at the changes made by Collaborans. To begin with Daniel Stone fixed an issue when waiting for fences on the i915 driver, while Emil Velikov added support to read the PCI revision for sysfs to improve the starting time in some applications.
  • Mesos Is to the Datacenter as the Kernel Is to Linux
    Necessity is the mother of invention. We needed our datacenters to be more automated, so we invented tools like Puppet and Chef. We needed easier application deployment, so we invented Docker. Of course it didn't stop there. Ben Hindman, the founder and chief architect of Mesosphere, co-created Apache Mesos. In his keynote at MesosCon Asia 2016, Hindman relates how failures and elasticity led to the development of Mesos.
  • Power Management Sees More P-State Tweaking, Other Changes For Linux 4.11
    Rafael Wysocki has submitted the ACPI and power management feature updates for the Linux 4.11 kernel. The work in the power management space this cycle includes improvements to Operating Performance Points (OPP), CPUFreq core clean-ups, new CPUFreq drivers for Broadcom BMIPS and TI SoCs and Qoriq.
  • RADV Vulkan Driver's PRIME Code Rewritten
    Red Hat's David Airlie keeps to work on improving the open-source Radeon Vulkan driver.

Games for GNU/Linux