KDE 4.1 Beta 2 – Two Steps Forward, One Step Back?
jammag writes "Linux pundit Bruce Byfield takes a look at the latest KDE beta and finds it wanting: 'Very likely, KDE users will have to wait for another release or two beyond 4.1 before the new version of KDE matches the features of earlier ones, especially in customization.' He notes that the second beta is still prone to unexplained crashes, and goes so far as to say, 'Everyone agrees now that KDE 4.0 was a mistake.' I'm not too sure about that — really, 'everyone?'"
"Everyone" agrees that Vista is "a failure", even though it's really not. So why can't dumb generalizations be applied to software that's supposed to be perfect in every way?
You know, I thought that the idea of Beta software was so that people could report unexplained crashes back to the developers....
I'm starting to think GNU is the problem with "GNU/Linux" these days.
I certainly don't think KDE 4.0 was a mistake beyond calling it "4.0" which led a bunch of idiots to expect something "finished", and that despite the up-front warnings that it wasn't finished.
It's a clear design improvement on 3.x in every way (though I don't particularly like or use the new desktop with its "plasmoids", I didn't like the 3.x desktop either, and the 4.x desktop can emulate it trivially - desktops widgets are just pointless, you just don't see them or the desktop for 99.9% of the time you're using the computer), it's just not stable yet.
the point --> .
.
.
.
. (this is the whoosh area)
.
.
.
you --> x
Contrary to the contributor's comment, I'm saying that 4.1 *is* better than 4.0, but not as much as better as people hoped, and that, in Folder View, it introduces a new source of controversy.
I twisted the original saying to reflect my opinion.
-Bruce Byfield ("nanday")
Here's why:
1) NIMBY - If Z is a feature or program I don't use, not only do I not care about it, I don't care about whether or not it can interact properly with programs I do care about.
2) Windows-ism - Many projects now try to replicate the functions of Windows apps. But the clones and work-alikes they produce are not only imperfect, programmers also can't take the same shortcuts that the Windows developers do.
3) Real Programmers - If a program isn't hard to write, it isn't worth writing, and if you make it easy for programmers to write for a platform, especially new ones, they will only produce crap that you somehow have to deal with. Compare this with MS's "Developers developer developers" motto, or Apple's excellent dev tools.
4) Esoterism - The command line is better than graphics. Graphics, and especially graphic quality is unimportant, and studies with evidence to the contrary notwithstanding, whether an interface is cleaner or more obvious or better-looking is irrelevant. It's okay for GUI tools and programs to just be front-ends for their command-line equivalents, even if it puts unnecessary limits on the graphical version.
5) Arrogance - (related to 1) There is only one right way to do things, one language, one library, one kernel, one package, one work-flow set-up. If you do it any other way, you're wrong; if you suggest that another way is good, I must shoot you down and insult you because you implicitly threaten the validity of my worldview; if you say that there can be more than one solution to a problem, you are really saying that your solution is right and mine is wrong.
I once listened in on a conversation by some digital typographers about their work set-ups, and unlike linux-heads they were genuinely interested in the advantages and disadvantages of different ways of solving the same problem, instead of arguing over whether which was best.
While having a story linked to on Slashdot always makes my day, the summary given with the link doesn't accurately report what I said:
-- To say that I found 4.1 "wanting" is incomplete. I say that it is a major improvement over 4.0.x, but, based on the beta, isn't likely to deliver everything people want. I suggest that, while it has faults, it may be the most innovative free desktop currently.
- I say that it crashes, not as criticism (it is a beta, after all), but to suggest that casual users might not want to spend the time compiling it, and should use a Live CD to explore it instead.
- The full context in which I call KDE 4 a mistake is: "Everyone agrees now that KDE 4.0 was a mistake. However, what the mistake was -- and whose -- is a matter of opinion. KDE developers blame distributions for rushing to include a release that was never intended for everyday use, while users blame developers for changing everything." In other words, all I'm saying is that it's causing a lot of controversy -- a fact that anyone who knows how to open a search engine can easily verify.
Trying to correct an impression that gets started in comments is difficult, but I thought I'd try anyway. So, let me spell out my opinion as clearly as possibly: I'm fascinated by the KDE 4.0 series with all its innovations (in fact, I'm using it on my laptop), but I think the KDE developers seriously misjudged user reaction, and that the software itself has a ways to go.
I don't mind in the least if people disagree with me, or even condemn me; you get used to it, after a while. However, I would prefer if they disagreed with or condemned what I actually said.
4 is almost a complete rewrite. It seems people have the impression that the reason all of the 3.5 desktop features weren't completed in 4.1 is because of a conscious choice. When actually, it is was just limited time. Feature freeze tends to stop the adding of magic ponys.
KDE shot itself in the foot by making the KDE 3.x so polished. KDE 3.5 is essentially 9 years of evolutionary development from KDE 1.0. Unfortunately, its impossible to recreate 9 years of development and polish in only 3. I think that the long term prospects for KDE 4.x are great, but short term I'll continue to use 3.5.
I've tried the first beta of 4.1 and while its much more functional than 4.0, its still not there and probably won't be for a few more releases. On the other hand, I remember that KDE 3.0 was, while more functional than 4.0, also much rougher than 3.5, so I can't complain too much.
KDE 4.0 and 4.1 are not meant to be perfect in every way. They are meant to establish a new scheme of APIs and a new design dynamic. It is a big overhaul that is in its beginnings. Nobody is claiming KDE 4.x is feature comparable to 3.x right now. This is just one person's view, and this is another view with excellent counterpoints. It is a failure where people are expecting too much of it in its current state.
Vista is supposed to be a workstation solution ready for every day production use right now. People are considering that to be a failure in its current state as well, and you are right, these two alleged failures are similar. But one product that is at an early start (4.0 & 4.1 beta, the more mature 3.5+ still seeing a lot of active development and use due to its maturity) and the other has the promise to be mature enough to use right now. You are not forced to upgrade to KDE 4.x, but Vista is required for some of today's games and applications because they don't run in earlier versions. This is the difference.
Twinstiq, game news
If you like Gnome, you'll love KDE4. It lacks many of the same features Gnome lacks.
Vista failed to achieve the goal that MS had when designing and programming it. I'm not sure how that can be anything other than a failure. The fact that they're really having to pull the plug to get people to move on and that people will likely switch directly to Win 7 if they can will prove it. And I see no evidence that that's not going to happen.
As for KDE, make it less bloated, better modularized and make the defaults include fewer programs.
I stopped using Windows because of the bloat and the unwanted features, I'm not about to start using a desktop environment that's as bad. But, really the same could be said for gnome and pretty much every desktop environment.
And for the love of god allow some alternate way of compiling the smaller applications without KDE itself. I hate having to install both the gnome and KDE libs because there's that one program which invariably requires the other set of libraries.
Tunnelling, I'd suspect.
KDE? more modular?
Kparts means that you can include practically entire programs (spreadsheets, browsers, editors) inside other programs - how much more modular can it get?