KDE 4.0 RC 1 Released
angryfirelord writes "The KDE Community is happy to announce the immediate availability of the first release candidate for KDE 4.0. This release candidate marks that the majority of the components of KDE 4.0 are now approaching release quality.
While the final bits of Plasma, the brand new desktop shell and panel in KDE 4, are falling into place, the KDE community decided to publish a first release candidate for the KDE 4.0 Desktop. Release Candidate 1 is the first preview of KDE 4.0 which is suitable for general use and discovering the improvements that have taken place all over the KDE codebase."
does it run on Vista?
Looks like plasma.kde.org is Slashdotted right now, so hey -- Wikipedia to the rescue.
If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
The main site is already bogged down. However, the major change is the completion & inclusion of Plasma. I like candy.
Screenshots are important for superficial people like me :)
I like the widget and window theme, but the kicker replacement at the bottom looks pretty tacky. It was the same in beta, and I'd hoped they'd change it for release, but it seems like they're sticking with it.
I have reviews of the general KDE desktop and Dolphin 4 on my page. I will review RC1 as soon as I can get Kubuntu packages.
Rudd-O - http://rudd-o.com/
I finally tried out a full KDE4 session last week and it is really coming together. I really look forward to the creative stuff people make with Plasma. Its not just a tool for having fun widgets on the desktop (which it is), but its designed so folks can easily develop their own taskbar, interactive wallpaper whatever.
So KDE 4.0 will be cool, KDE 4.0 + 6 months of people creating fun plasmoids, even cooler.
For people who want to check out the RC without reinstalling KDE (and without risking breaking your existing setup) there's a live CD available at:
http://home.kde.org/~binner/kde-four-live/
Have a lot of fun!
And yet I find myself installing more and more KDE apps on my GNOME system because of how slow or boneheadedly featureless their GNOME equivalents are. (Evince, I stab at thee! So much hatred for its sluggish rendering and inability to change its default view.)
And when is GNOME ever going to get a good burning app like K3b?
If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
Plasma isn't planning too, but most KDE apps will be able to run on Windows. If not at the KDE 4.0, then in the near future.
And yet, despite all the extra features and configurability, KDE still manages to use about the same resources as GNOME:
http://ktown.kde.org/~seli/memory/desktop_benchmark.htmlhttp://spooky-possum.org/cgi-bin/pyblosxom.cgi/kdevsgnome.html
KDE doesn't have much fat; it has muscle.
Am I alone in thinking that people are abusing the term "Release Candidate"? Since there already is a term, "beta", that means "functional, with minor bugs to be ironed out", I would consider "Release Candidate" to refer to a true candidate --that is, it might really be released! KDE (or whoever the responsible author is) might say: "Okay, all those of you who downloaded Release Candidate x (where x=1,2,...), you can just go ahead and keep using it, because the RC has turned into the real thing."
Software or distros that are "coming together" are not Release Candidates. They have no possibility of being released. Suppose everyone who tried this KDE4 RC1 said, "Yup, everything works fine! No changes need to be made," would KDE release it? No, because they're NOT DONE YET --Plasma still has to be put together. Since they won't be releasing this version at all, it shouldn't be called a Release Candidate. It's another beta.
There's no shame in calling it beta (heck, half of Google's services are labeled beta); I don't see the need to keep advancing the terms. What's next? If "Release Candidate" comes to mean "beta", should we start using the term "Release Candidate with Potential For Use Unchanged"?
Maybe someone can correct on this if I'm wrong. What makes this a Release Candidate and not a Beta?
(Btw, diehard KDE fan here --I'm not even considering GNOME until they start having user-configurable key shortcuts. Waiting for KDE4 final release in December to be worked into Gutsy so I can put it on my Came-With-Ubuntu laptop.)
404555974007725459910684486621289147856453481154 in hex is "You sank my Battleship?"
[GPG key in journal]
Well, I can't say I object to any of these improvements, but most of them seem pretty minor and incremental. Cleaner APIs and more efficient libraries are nice. For the end user, where's the meat of this release? Okay now it supports Widgets. Well, that can be sort of useful if there is a good selection of them. I've heard claims they added support for OS X native widgets and that could help a lot to make this actually useful. Anyone actually tried using them yet?
When a new full version comes out and I find myself looking forward to the improved spellchecker, because it is still worse architecturally than on other platforms I use, but at least it is better... well I start to wonder what happened. I'm not trying to put down the developers or anything, this is obviously a lot of work, especially Dolphin, but I guess I was hoping for more. When will KParts be upgraded to work like OS X system services? Where's grammar checking? Where's anything we haven't seen on another OS/Window manager already? As a Kubuntu user, I guess I'm just not really as excited by this as I'd like to be.
Well, there's two kinds of "bloated" and people often don't differentiate between the two. There's bloated in the sense of being written poorly and wasting a lot of resources for no reason, and then there's bloated in the sense of having a whole bunch of features that various people may or may not want (which usually determines if they consider it bloated or not). The first kind of bloated of course is clearly a valid criticism that needs to be addressed, the second kind however is mostly a matter of taste. Myself, I like a bit of eye candy, but at the same time I don't like to waste a lot of space, so I tend to lean towards either Enlightenment, or Blackbox for my WM. Both can be configured to be relatively minimalist in terms of screen real estate used by the various pieces of the WM, but in the case of enlightenment it tends to use some resources because of all the eye candy options. Does that make it bloated? Maybe, but that really depends on if you like eye candy or not.
Curiosity was framed, Ignorance killed the cat.
Gexactly. GGNOME Gdoesn't Ghave Gthese Gissues.
I recently had a very busy weekend trying edubutu, ubunutu, xubuntu, and gOS on an IBM T40, with mixed results.
I did not get around to kubuntu, perhaps I should have. Ubuntu is (for the most part) a Gnome environment. Kubuntu is the KDE oriented version of Ubuntu. At this point, Kubuntu lacks the polish seen in Ubuntu. As you seem to be getting your feet wet, you probably would want to stick with Ubuntu and its polished Gnome environment.
Me, myself... I'm using Kubuntu. I just like KDE better and am familiar enough with it to deal with Kubuntu's occasional rough edge. You might feel inclined to test those waters once you're feeling like you've got a good footing.
It should be stressed that the issue of Gnome vs. KDE (vs. Blackbox, Enlightenment, etc., etc.) is mostly a matter of interface and taste. The applications you run aren't necessarily restricted by your desktop... even if they are often bundled with one project or another.
Release candidate? Come on, I know people are pretty lax about terms to use - alpha, beta, RC, what do they even mean anymore? But come on, this is going a bit far:
This release candidate marks that the majority of the components of KDE 4.0 are now approaching release quality...
And so on. Now, unless I missed something, a release candidate is when you think your product is about ready for public release but you want to have people test its "final form" first. You think it is ready, but you want to real-world test it to iron out bugs that have escaped you. Release candidates are not packages that are known to be incomplete. Is KDE doing this just to show some progress since the year is stretching on without a release of KDE 4? Just call it another beta. Heck, it sounds like it might should be alpha still. They are not yet to the final bugging stage, it is not feature complete, they are still adding new code. I can forgive them for calling an alpha a beta, but calling an alpha a release candidate? Come on!
(P.S., I know I'm hijacking a thread to get higher position with my post. Please forgive me. This post is in release-candidate status and the final form of this post is expected to be relevant to the current discussion thread.)
I love my sig.