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

Top 4 open source alternatives to Google Analytics

If you have a website or run an online business, collecting data on where your visitors or customers come from, where they land on your site, and where they leave is vital. Why? That information can help you better target your products and services, and beef up the pages that are turning people away. To gather that kind of information, you need a web analytics tool. Many businesses of all sizes use Google Analytics. But if you want to keep control of your data, you need a tool that you can control. You won’t get that from Google Analytics. Luckily, Google Analytics isn’t the only game on the web. Here are four open source alternatives to Google Analytics. Read more

Welcome To The (Ubuntu) Bionic Age: Nautilus, a LTS and desktop icons

If you are following closely the news of various tech websites, one of the latest hot topic in the community was about Nautilus removing desktop icons. Let’s try to clarify some points to ensure the various discussions around it have enough background information and not reacting on emotions only as it could be seen lately. You will have both downstream (mine) and upstream (Carlos) perspectives here. Read more

Programming: Perl, JavaScript, Ick, PowerFake, pylint-django, nbdkit filters

  • An Open Letter to the Perl Community

    Some consider Perl 6 to be a sister language to Perl 5. Personally, I consider Perl 6 more of a genetically engineered daughter language with the best genes from many parents. A daughter with a difficult childhood, in which she alienated many, who is now getting out of puberty into early adulthood. But I digress.

  • Long Live Perl 5!

    While not mentioned in the original Letter, a frequent theme in the comments was that Perl 6 should be renamed, as the name is inaccurate or is damaging.

    This is the topic on which I wrote more than once and those who have been following closely know that, yes, many (but by no means all) in the Perl 6 community acknowledge the name is detrimental to both Perl 6 and Perl 5 projects.

    This is why with a nod of approval from Larry we're moving to create an alias to Perl 6 name during 6.d language release, to be available for marketing in areas where "Perl 6" is not a desirable name.

  • JavaScript Trends for 2018
    Trying to bet on how many new JavaScript frameworks will be released each month, is, the best software engineer’s game in the past 5 years.
  • Ick: a continuous integration system
    TL;DR: Ick is a continuous integration or CI system. See http://ick.liw.fi/ for more information.
  • Introducing PowerFake for C++
    PowerFake is a new mini-framework/tool to make it possible to fake/mock free functions and static & non-virtual member functions in C++. It requires no change to the code under test, but it might need some structural changes, like moving some parts of the code to a different .cpp file; or making inline functions non-inline when built for testing. It is useful for writing unit tests and faking/mocking functions which should not/cannot be run during a test case. Some say that such a feature is useful for existing code, but should not be needed for a code which is written testable from the beginning. But, personally I don’t agree that it is always appropriate to inject such dependencies using virtual interfaces or templates. Currently, it is not supposed to become a mocking framework on its own. I hope that I can integrate PowerFake into at least one existing C++ mocking framework. Therefore, currently it doesn’t provide anything beyond faking existing functions.
  • Introducing pylint-django 0.8.0
    Since my previous post was about writing pylint plugins I figured I'd let you know that I've released pylint-django version 0.8.0 over the weekend. This release merges all pull requests which were pending till now so make sure to read the change log.
  • nbdkit filters
    nbdkit is our toolkit for creating Network Block Device (NBD) servers from “unusual” data sources. nbdkit was already configurable by writing simple plugins in several programming languages. Last week Eric Blake and I added a nice new feature: You can now modify existing plugins by placing “filters” in front of them.

Moving to Linux from dated Windows machines

Every day, while working in the marketing department at ONLYOFFICE, I see Linux users discussing our office productivity software on the internet. Our products are popular among Linux users, which made me curious about using Linux as an everyday work tool. My old Windows XP-powered computer was an obstacle to performance, so I started reading about Linux systems (particularly Ubuntu) and decided to try it out as an experiment. Two of my colleagues joined me. Read more