• Static

  • About Me
    • Copyright Policy
  • Links
• Skype - Unlimited Calls to Landlines
• Great offers at Skype's clearance sale
• Domain Sale! $7.49*.com at GoDaddy.com
• Click here for Free IT - Software & Development Resources!

• Blogrovr!

  want this on your blog?

• Meta

  • Register
  • Log in
  • Entries RSS
  • Comments RSS
  • WordPress.org
• 

Sebastian Kuegler of KDE recently agreed to give an interview, the first in what I hope will be a series. His responses are well thought out and detailed. I hope you enjoy it as much as I do.

1. For the readers unfamiliar with you, tell us about yourself and the work you do for KDE.

I’m a 31 year-old German, living in the Netherlands with my girl-friend and my two chinchillas. My KDE history involves coding on Guidance, a set of system administration tools written in Python using PyKDE and PyQt. My current coding activities for KDE focus on Plasma, KDE4’s new desktop shell.

During aKademy 2005, I’ve started with the help of some others the KDE Marketing Working Group. With this group we have improved KDE’s PR work consistently over the past years. In 2006, I was elected into the Board of Directors of the KDE e.V., the foundation that is backing the KDE Community legally, financially and administratively.

2. How was the Release Event? What stood out the most to you?

The most amazing thing during the late Release Event was that KDE, while traditionally a bit Europe-centric, has an impressive presence in America as well. The event in Mountain View almost felt a bit like our yearly get-together Akademy. From a community-building and -strengthening aspect, it was a huge success. I also got to meet some people I’ve never met before. This kind of event is vital to nourishing a community and was a great success.

On the other hand, the event was a great opportunity to show what KDE offers right where the industry is. We got quite some people from companies interested in KDE, and we showed well what KDE has to offer, and how to make use of it.

The event itself was well-balanced between community and industry. Something which I particularly liked is that we kept it open, we gave everybody, including the press a look into the “KDE kitchen”. We don’t have anything to hide, this is how we work.

3. You have mentioned being thrilled at how KDE has improved its processes. Would you mind elaborating?

Sure. While the most apparent presence of KDE is often screenshots and surely new software for those who want to try the new version, during the last two years we were also able to improve the organisational side of things. Project governance is an important aspect for Free Software projects, and KDE has managed to make itself more sustainable and stable from this point of view.

2.5 years ago, the members of the KDE e.V. decided to formalise certain aspects of the KDE Community. This was achieved by creating a set of so-called Working Groups, small committees that deal with a field of interest within KDE. The initial set of Working Groups was the Technical Working Group (more on that later), the Human Computer Interaction Working Group, dealing with usability, accessibility and artwork and the Marketing Working Group.

The Technical Working Group didn’t work out very well. The members, that had been elected by the KDE e.V. members, all core developers of KDE didn’t have
enough time left to formally deal with issues related to release management and decision-making in technical matters. The only real result of the Technical Working Group was the decision to use CMake as a build system for KDE (back then, there were 3 buildsystems in use). CMake turned out to be an excellent choice for KDE, of course, but the TWG itself didn’t last that long. After some discussions about the form and members of the TWG, we have decided to put back this problem into the hands of the wider community, calling for people to take responsibility and form a release team.

Some people stood up to take this responsibility, a mailing list was set up and the release team started its work. Most important aspect was to get on the release train towards KDE 4.0. It turns out that this Release Team works really well. It’s very open, everyone can subscribe to its mailinglist and follow discussions, and its members are respected so the decisions that are being made are followed by the rest of the community.

The HCI Working Group has been working continuously to integrate usability and accessibility engineering into the KDE development process. Recently, there is for example hardly any developer meeting without a usability expert present. This way, we make sure that usability and accessibility are not applied as an  aferthought, but are one of the bases of the technical design process. To make applications more consistent, and developing easier for the hackers, the HCI group is also working on human interface guidelines, which explain how certain aspects of our user interfaces should be designed. The Oxygen team, which is responsible for artwork in KDE is also flourishing. We can see that KDE has gotten a new, contemporary and modern look through the last 3 years.

The Marketing Working Group has taken care of good relationships with the press, has fostered the idea of “Guerilla Marketing”, promotional activities carried out by the wider community, and has also provided guidance for those that want to get involved with promoting KDE. One of the most important achievements of the Marketing Working Group is being accepted by the developers, and creating a strong brand which is based on fairness, honesty and other elements of the Free Culture spirit. More tangible improvements are materials telling about KDE (remember Troy Unrau’s “The Road to KDE 4″ series of articles?) and generally improved communication channels with the press.

This all shows one thing well, KDE as a Free Software community is turning into a community of Free Culture people. “Just coding” is not enough to spread Free Software, making Free Software a success is something that requires a multi disciplinary team working together well. That is what we see happening in KDE.

4. How can everyday users help with “Guerilla Marketing”? Is there an easy way to step in and help?

Yes, there are many easy ways to help. The most obvious is helping people installing KDE, answering questions on forums, IRC and other media. Lately, we’re getting also an increased amount of requests for speakers. Often local LUGs are interested in talks by KDE knowledgeable people. It might sound a bit scary,  representing KDE in your local LUG, but it’s really what KDE is about. Everybody comes from a local community, that is where our grassroots are. People often don’t think that they are entitled to represent KDE, but that’s just not the case at all. In fact, the marketing and promo team have a hard time finding enough speakers for all events. Slides are usually available, so it doesn’t need all that much preparation.

There are of course many more areas where you can support KDE. Writing articles for magazines is a way to even earn some money, helping with maintenance of websites, submitting KDE-related news to your local newssites, maybe even writing for them, translating news (or of course applications), helping out at events and fairs, there’s lots to be done, much of which doesn’t involve writing a single line of code, but it’s just asimportant.

5. I was excited to see the new release schedule for KDE. How did this come about?

Well, we obviously need a release schedule, otherwise our developers don’t get an idea of when their code should be release-ready, and of course not knowing when to release doesn’t have a great effect on motivation. That’s the immediate reason why we worked on a release schedule quickly after 4.0.0 was released, but our release plans are really two-fold. The next 6 months with a monthly bugfix update and 4.1 in July are only part one. Part two is that we agreed to release a feature release every 6 months.

This is where public perception and our own didn’t really match lately. Looking into the past, KDE had a pretty steady release rhythm where we released a new feature version (3.x) at least every 8 months. Unfortunately, this was found to unpredictable by some external parties, especially distributors, so we thought how we could accommodate them better. At the same time, we need to have a close look at our development cycle. How long will people need to stabilise the codebase? How long does it take to implement new features? What part of our development time between releases do we want to spend feature-frozen? All those are important questions. First and foremost, we want to develop software, if we don’t, we don’t need to release at all. So our development process is what should dictate release schedules.

If we have a look at how the KDE 3.x cycle worked, we can get a clue of what’s to be expected for 4.x. With 3.0 we had put the pieces necessary that are necessary to build great applications in place. It turned out that we could release more than once a year, and with every release provide exciting changes and nice new and updated applications.

Now with 4.0 delivering even better frameworks, we can build on those. Having a stable basis in place makes it possible for us to cut down the time between
releases — because changes don’t need to be done under the hood. Oversimplified, we don’t need to change much but can build exciting new stuff on top of our frameworks. The issue how long a feature takes to be implemented becomes less important. Our community has reached a size where there will always be the bigger thing that just won’t make it into the release. We should learn to live with that.

On the other hand, we seem to have lost a bit of our traction with larger Linux distributions. We hope we can address parts of that with being more predictable. I don’t think that merely a release cycle is to be blamed for that, but really, we are putting the pieces together to make living with KDE easier for our commercial partners. We have emphasised focus in UI aspects such as usability and artwork, but we’re also more actively working together with distributions and try to engage them more in our development process. The release schedule, as an example, has been created after consideration of some distributions.

6. Are there any misconceptions about KDE 4 you see regularly and would like to address?

The most striking misconception I saw in the review is that people don’t really get what KDE is. I saw quite some bad press that didn’t go any further than “The panel lost some features”, but without really having a look at what changed. The Panel, belonging to Plasma is a completely new component. As that, it’s not exactly surprising that it has not yet reached feature parity. It’s quite a pity though to see that some journalists don’t look any further than that. We have some terrific new applications, our frameworks are greatly improved (which will make for many more new and improved applications in the near future). KDE 4.0.0 is really what it’s called. A dot-oh-oh release. Some people said that we should have waited half a year and released 4.0 as 4.1, but those don’t seem to understand how the Free Software development process works.

Having 4.0.0 out gives it more exposure to users, but also shows some other components down the stack that they really need to catch up. We’re raising the bar of what’s being done with desktop operating systems, this is not free of pain. Plasma for example exposes some bugs in video drivers and other toolkits such as GTK — simply because we’re the first to make extensive use of ARGB visuals (or, for the less technical inclined, transparency effects). Hadn’t we released 4.0.0, nobody would’ve tested their drivers with it. Result, if you then release 6 months later: the bugs are still there, simply because no one has run into them (well, except for us developers, but we are only so many). See, we’re not an island, we cannot create all great stuff only by ourselves. We’re highly dependent on projects like X.org, the Linux kernel and of course a lot of Freedesktop components. And some of those just don’t accept bug reports that come from a beta release of KDE. It’s a chicken-egg situation, if you want.

So sure, 4.0.0 is not as polished as anyone (especially ourselves) would have wanted it to be. It certainly is a usable desktop, if not up to all the goodness of 3.5.8 (which is what people seem to be used to, which shows that we do deliver quality work). We knew from the beginning that the development cycle leading up to a stable KDE 4 release would be painful. The fact that the definition of stable varies widely within our userbase and the expectations of everyone doesn’t make it any easier.

And then, most of the issues people have been complaining about are already fixed (and will be released in early February with KDE 4.0.1). Others will certainly be addressed with KDE 4.1, coming this summer. And of course, we always have our good old proven 3.5 branch, which is the perfect fit for those that cannot or do not want to live on the bleeding edge. KDE 3.5 is still fully supported, we’ll be releasing an update with quite some improvements especially in the KDE-PIM components in February. KDE-PIM in KDE 4 is scheduled to be released along with 4.1, making this release much more attractive to the users that are a bit more hesitant than our average developer.

7. What in the upcoming 4.1 release excites you the most?

I think the part that most people — just like me — are really looking forward to is an improved Plasma desktop shell. It really is the most visible part of the desktop. The good news here is that Plasma, a relatively young subcommunity within KDE is really alive and kicking. We’ve already been able to fix most of the problems that were still there in 4.0.0, and if we continue to keep the current pace of development, it looks like we have exceeded feature parity in those part with the 3.5 series already by summer.

Then of course, I’m looking forward to KDE-PIM in 4.1. It will make use of the Akonadi storage framework and as such be more stable and usable as the 3.5 series. Then, just recently, Dragon Player has been merged into our 4.1 tree. Dragon Player is a very simple but powerful video player, which of course makes use of Phonon, our new multimedia framework. For non-Linux/UNIX users, 4.1 will also bring the first stable applications to Mac OSX and Windows, which is another very big thing in my eyes.

Other features include more scripting support, newly ported applications (Amarok for example seems to be aiming for a summer release as well), performance improvements all over the place, new plugins for the KWin window manager with its nifty compositing features, and many more.

This really suggests what I expect from the KDE 4 series, new, innovative and really exciting features and improvements at a steady pace. With the KDE 4
series, we’ll simply outperform our proprietary competitors in terms of speed of innovation and user orientation.

8. What are your feelings about Gnome? People love to play up a war between KDE and Gnome and fight it out in comment sections. How is your relationship with Gnome? Do you find anything interesting about the Gnome desktop?

It’s sometimes a bit tiring that people try to put everything into the KDE vs. GNOME perspective. We’ve been working together with people from GNOME for a
long time and reached a lot together. A quick glance at freedesktop.org shows that there is plenty we have in common, and that we are doing quite a good job sharing efforts where it makes sense. I feel that the sentiments are often caused by people that simply have nothing better to do, or are out for sensationalism. The friendly competition between KDE and GNOME has probably helped both projects to become what they are now: Serious competitors of proprietary desktop systems.

On the other hand, GNOME often is not all that interesting to us to work with since one essentially can replace the other. Our issues up an down in the stack usually don’t hit GNOME directly, and GNOME offers an alternative to KDE, which also means that we don’t have to suit everyone’s need.

Frankly, I don’t like the whole concept of the “Linux Desktop”. Linux is really just a kernel, and in this case very much a buzzword. Having to mention Linux (which is just a technical implementation detail of a desktop system) suggests that something is wrong. Should it matter to the user if he runs Linux or BSD on his machine? Not at all. It only matters because things just don’t work so well (mostly caused by to driver problems, often a matter of ignorance on some vendor’s side).

The result is that people talk about Linux, then get confused between KDE and GNOME. The first question they ask “Why do I have to choose?” which expresses
that they are having a hard time dealing with the complexity that is offered immediately. The really important concept is plurality, and that is where we
can all win. Once people understand that the choice for KDE and GNOME is very much like the choice between, say Mac OS and Windows (nobody ever says: “Well, the world would be much better off if the effort wouldn’t be spread between Apple and Microsoft!”), so I keep asking myself why people often come up with this when talking about the Free Desktops. What we want is raising consciousness that you don’t have to swallow everything that a certain vendor wants you to, that there is choice, and that consumers can actively influence the market and put pressure onto those that don’t respect the consumer’s needs.

The term “Linux” serves more or less as a buzzword, but I think calling KDE “The Linux Desktop” is harmful. First, it ignores the concepts of plurality and choice, which are very much core values in the Free Software community. Second it ignores the efforts being undertaken to push KDE onto other Free Platforms such as FreeBSD, OpenBSD and OpenSolaris — those are not second class citizens for us.

To fix this problem, we need to increase awareness of the Freedom concept and not so much “teach people what Linux is”. The concept of Freedom is also much
more appealing to the masses than the concept of an operating system kernel, it just requires us to start thinking outside the box. Creating strong brands of user-visible components makes a lot of sense here.

John Palmieri, a top GNOME developer who attended KDE’s annual conference two years ago said: “Competition and collaboration are not mutually exclusive”. I
agree with this statement.

9. Thank you so much for your time, Sebastian. It certainly has been illuminating. Any final thoughts?

Thanks a lot for offering the opportunity to share my thoughts.

Thank you Sebastian, for an interesting and thoughtful review. It is appreciated. Be sure to check out Sebastian’s blog, vizZzion.org, for news on planned features of KDE 4.1, a horrific story of a crocodile attack and much more.

KDE 4.0 was released last week and all hell seemed to break loose. What I view as a solid first step in a very positive reaction was met with some applause, but generally scorn and complaints. I think some perspective is needed, and I humbly offer to try and provide some. I’d like to take issue with some things I see that are just plain wrong.

KDE 4 is Vista. Vista is an operating system. KDE 4 is a desktop environment. Right off the bat, on a basic level, this is wrong. If you only look at the DE aspects of Vista, it still doesn’t stand up. People complain about Kickoff, the new (possibly temporary) menu in KDE 4. Have you used the monstrosity that Vista provides? Plus, if you do not like Kickoff, you can drag the old style launcher to the taskbar and be happy. Vista offers nothing of the sort. KDE 4 runs very well on modest hardware. Vista is painful on modest to good hardware. I had a hardware failure on my main machine yesterday. It runs Linux. I’m stuck writing this from Vista on a 64 bit processor (AMD 3200+) with 3 gigs of RAM and it is unbearably slow. My desktop effects consist of some translucency and some crummy 3-D window switcher. With KDE 4 there are a lot more useful effects this early in. KDE 4 = Free Software. Vista = closed source. Complaints people have with KDE 4 are already being addressed. Some have been fixed. Get that kind of action from Microsoft. The Promised Land, KDE 4.1, is rumored to be released in about six months. The Promised Land for Vista, SP1, is still unreleased a year into its life (and the reports of the beta are less than glowing.) Maybe it kind of looks like Vista with the use of black, but that is about it.

KDE 4 is Gnome. This is usually meant as a swipe at Gnome as well as KDE, based in the belief that the Lords of Gnome sit in their ivory towers deciding how the peons can use their computers. The great Nautilus-Spatial-View Wars of 2004 saw a lot of bickering on this front. Since a lot of configurability that KDE is famous for just wasn’t ready for the 4.0 release people are assuming that it is just gone forever. It is coming; you can relax or file bug reports. If the configurability you are used to isn’t there in 4.1, then I’ll be right there with you. I believe the developers when they say it is coming. It isn’t like there is a lack of options in KDE 4; I’ve even read complaints that there are still too many. It is just that the most visible ones, like in the taskbar, just aren’t there yet. That is right in your face immediately.

This also feeds into the Holy War that Gnome and KDE are locked in. We have choices. Some people like Gnome, some KDE. There are plenty of other choices as well. Fans of gerbils can use XFCE. Enlightenment is cool. FVWM Crystal works nicely. Blackbox, Openbox or Fluxbox. Why so much energy is devoted to Gnome people attacking KDE people and vice versa confuses me, other than people love to have an enemy. In the words of convicted wife-beater Rodney King, “Can’t we all just get along?” When the negativity impacts development (my 10 things I hate about KDE 4 RC2 article was accused of stopping development for hours, weirdly) then things are getting out of hand. Some thicker skins might be in order as well.

KDE 4 is lacking in cowbell. The “needs more cowbell” joke stopped being funny about three days after you heard a co-worker say it for the first time. That was years ago! Enough already.

It was a mistake to release KDE 4.0. This has already been addressed nicely here, here and here. For the “tl;dr” crowd, the release has to get out into the real world and take a beating. I’m sure the complaints so far have been useful in some sense and will influence direction. This is a complicated issue that has been covered in more detail by people smarter than me; I just wanted to address it. I’m surprised to even see this, since “Release early, release often” is such an ingrained part of Open Source. Imagine if Duke Nukem Forever was Open Source and followed this philosophy.

“My experience with KDE 4 is the One True Experience” There are so many odd combinations of hardware, distributions and preferences that everything becomes equally valid. The experience you have with KDE 4, for you, will set your ideas into stone. I’ve read there were numerous problems with the Kubuntu packages. People who used those are naturally going to be unhappy with 4.0 for good reason. OpenSUSE has done an outstanding job with their packages. I’ve used them and have a positive feeling about 4.0. Nvidia cards perform well with the proprietary driver and KWin’s composite. I’ve read ATI doesn’t work that well. For the ATI owners, composite will be horrible. Some people love Kickoff. Some people hate it more than anything else in the world, apparently. Who is right? People passionately hate Dolphin, others love it. Most people, for these reasons, are going to have very different experiences with KDE 4. If we could just cut each other some slack and recognize the validity of each person’s opinion I think the overall atmosphere will improve.

Things haven’t been perfect. It is too bad that KDEPIM wasn’t ready. From what I have seen and read, it will be worth the wait. Distros have had some trouble with packaging. Things are nowhere nearly as bad as you may read, either. Before my hardware failure, I had been using 4.0 as my main desktop for weeks. I’m starting to prefer it, warts and all.

Here is my somewhat lousy analogy for KDE 4. You’ve lived in a house (KDE 3) for years. You have everything set the way you want it to, have gotten used to the oddities of it and love it. Some major parts of it have fallen into disrepair (arts) and it is time to move. You decide to build a new house from the ground up (KDE 4). It reaches a point where you can move into it, or stay in the old one for a few more months. You decide to move. The old house had cable. The neighborhood for the new on is being wired for cable, but it isn’t available just yet. Is your old house better because it had cable? Is the new one a failure because cable isn’t ready yet? The new house has a different thermostat that is quite different from the old one, and you can’t set it the same way you could the old. The builder promises that in a couple of months you will have three thermostats to choose from that are a lot better than the old one, but at least the current one works. The builder also says that if you do move in, he’ll listen to things you don’t like and give you the opportunity to change things, instead of just giving you something set in stone. He even promises to continue to improve the house for years to come. You can either live in the old house for a while longer and watch the progress of the new one and stay comfortable; or jump into the new one and get used to it. Odds are you aren’t going to complain that you shouldn’t even have built a new house. Particularly because it is free and built at no cost to you. It could be worse; you could be in the luxury prison down the street, where the prisoners complain that the old one, while bad, was much better than the new one.

The KDE Release Event is today. I had hoped to go, but the complete lack of free flights complicated it. Congratulations again to everyone involved. You have a lot to be proud of, and a lot more work ahead.

KDE 4.0 is out as of today. Click here for the official announcement. A separate announcement with info on packages for different distributions is here. OpenSUSE had the updated packages available when I checked at midnight last night–great job yet again by the packagers (or packager?).

A wll written and helpful Visual Guide to KDE 4.0 is available here. It has plenty of screenshots and information.

A post on Aaron Seigo’s blog  is very interesting, and gives you more of an idea on why you should be excited about the KDE 4 series. Click here for that. If anything, it should give you an appreciation for what the devs are going through and the hard work they put in. All for something we get for free.

This is a big step forward, and the first of many big steps for KDE. Congratulations to all of the developers and to everyone involved!

Using KDE 4.0 yet? If so, leave a comment with your experience.

Update! The following link, and Emergency FAQ, has been posted and is helpful:

http://software-libre.rudd-o.com/KDE_4.0.0_emergency_FAQ 

I’ve complained and cheered about KDE 4 RC2 from openSUSE. I’ve updated to the latest openSUSE packages since writing those articles, and things have moved in a very positive direction. I’ve been able to use it as my main desktop without issues for about a week now. I’d like to commend openSUSE for the outstanding job they have done with KDE 4. Using one-click install, it couldn’t be easier to get it going. With YAST it is very easy to keep it updated. With the release imminent, I thought I would take one last look at what openSUSE terms KDE 4 RC2++. I’ll warn you, the list may be odd, these are just things I have come across in daily usage. I promise no rhyme or reason!

Fixes to my complaints:
-It is no longer crashy and inconsistent. I haven’t had a crash in days. Behavior now works as expected, consistently. Improvement was quick and dramatic.
-Right click in Dolphin now works correctly.
-Right click on the taskbar does give options, albeit limited. There is still no option to change the bar size, but changing my resolution has made this less of an issue. I don’t even mind the transparent strip across the top of it now that I am used to it.
-Blurry fonts are no longer blurry fonts.

General Improvements:
-Responsive. The overall speed of the desktop has improved with the latest updates. Everything feels very close to normal.
-Pager is in the taskbar. I think this will give people a level of comfort. I’m preferring to use Ctrl + F8 and Alt + Tab to move around. Old people will like seeing the familiar four box grid.
-Digital Clock is configurable. At some point for me it wasn’t. It now acts exactly as I would expect it to. You can choose your timezone, font, whether to display a 24 hour format, show the date, basically, anything a configuration junkie would want. It looks nice, too. Now maybe the Clock Nazis can chill.
-Composite effects work nearly flawlessly on my setup (Nvidia 8400 GS). I’m liking the effects more and more. Compiz has always felt like a second class citizen with KDE, this helps to overcome that. The effects are smooth and feel natural. I hope there is a webpage with the keystrokes and tips for using it once 4.0 releases. If not, I’ll make one.

Small things I like:
-The new splash screen and logout screen are beautiful. Nice touches. Pic of logout screen below:

-I like the new default wallpaper. It fits the darker theme but isn’t too dark. There is already a lot of whining about the choice, like it won’t take five seconds to change it.

-Being able to right click the title bar and choose the window opacity. That is slick, and helpful.
-Marble is cool. what is marble, you ask? It looks like GoogleEarth, but uses no hardware acceleration, so it is small and lightweight. More info here.

-Oxygen Cursor Theme- I’m using the White Cursor Theme, it looks nice but is not obnoxious. More info here.
-Deal or No Deal- until they get sued, the game Deal or No Deal from playground, I believe, is a nice little time waster.

Bigger things I like:
Okular- Great interface and it works very well. I love being able to uncheck the “Obey DRM limitations” box. Clever. It is fast. The toolbar is clean, with options to junk it up as much as I’d like. I love that it can handle multiple formats. It is consistent with the rest of kde 4 and fits in well.

KPlayer- I’ve never liked KPlayer, for no good reason. I like the updated interface. Unfortunately there isn’t an openSUSE package for Dragonplayer (formerly Codeine) at the moment. I may actually start using KPlayer.

Kdegames – The games are cleaned up and consistent looking. They look fantastic in SVG. Excellent job here.

KDEPIM- Ridicule me, remind me it is alpha, I don’t care. I really like it and it doesn’t even crash all that much. I cannot wait until it is finished. Pictured is KOrganizer:

Consistency- It has been hard to write this without using the word consistent fifty times. Everything just goes together nicely. I normally wouldn’t care too much about this, but the more I use the desktop the nicer it seems. KDE 4 apps have a KDE 4 identity. That is a good thing.
I could go on and on, but the release is tomorrow and I’d rather write about it.

Final Thoughts:

Once again, I have to applaud openSUSE’s KDE 4 packaging team. Outstanding job. My hat goes off the the KDE developers, the progress in the last few weeks has been incredible, and this release is shaping up to be phenomenal. We are stepping into the future tomorrow, and making a big jump. I respect the courage and hard work that has gone into KDE 4.0 and I cannot wait to install the release tomorrow.

I hope the negativity–that I contributed to–settles down once people use KDE 4. Install it and stick with it for a week. You may not like it at first, you may love it at first but give it a chance. Use it for a week before you start bitching. I think, like me, you will be pleasantly surprised. It is better than you have read. I look forward to KDE 4.1, and can’t wait to see how this grows and changes, but 4.0 will be my desktop of choice. Now that I am used to using it daily, I prefer it to anything else. It isn’t as if 3.5 is going away, or there are a lack of other choices if it isn’t for you. I predict the community will rally around this release. Complainers will still complain and further progress will be made. The bottom line: The future begins tomorrow. I’m excited.

Next Page →