Bero Quits Red Hat Over Treatment of KDE 615
Vicegrip writes "In an article on leaked release notes on Redhat 8.0 CNet also revealed that Bernhard Rosenkraenzer, known here on Slashdot as berorh, has quit over objections he has on what Redhat is doing to KDE in the new release. Bero says that the new version of KDE in Redhat 8.0 is going to be crippleware.
I know I always found Bero's comments here on Slashdot helpful and insightful. His worries about what Redhat is doing to KDE for 8.0 have me rather concerned and thinking of switching distributions."
Maybe he will join MandrakeSoft again! (Score:5, Interesting)
I am with Red Hat on this one... (Score:4, Insightful)
I am one of those who say that Red Hat should only support either Gnome *or* KDE, but allow through the libraries to run each other's applications, in a way that it is completely unified (apps to behave and look the same even if they are from different toolkits).
More discussion about this here:
http://www.osnews.com/comment.php?news_id=1808 [osnews.com]
Re:I am with Red Hat on this one... (Score:2, Insightful)
Re:I am with Red Hat on this one... (Score:4, Insightful)
Actually, I'm planning on waiting for the imminent release, rather than the "null" work in progress, having a play around with it and then making up my mind. There is so much FUD on this issue from the KDE and Gnome developers, as well as Red Hat and the community that this is the *only* way to go.
As a firm KDE desktop user who runs a lot of Gnome apps within it I'm all for making KDE and Gnome look alike for a consistent desktop. I've basically done this so far by using very similar themes on both window managers and tweaking out the differences where possible, and it was my impression that Red Hat had just taken this one stage futher, which was fine by me. However, for Bero to take this step, especially given that this is the same Bero that so eloquently dispersed the FUD around Red Hat's recent compiler choices, I'm getting a little concerned they may have gone a bit futher than that.
Red Hat has an excellent track record for me; I've had problems with most of the the other popular choices that Red Hat didn't even bat an eyelid at. They are also pretty on the ball with the security patches, unlike some distros I could mention, which is essential when you are responsible for numerous boxes out on the Internet.
All in all, I do hope they are not going to spoil their track record over this, but a large part of using open source code is about having the freedom to make a choice, isn't it? I don't see any reason why that shouldn't extend to the distro packagers too, and frankly I think it somewhat hypocritical to believe otherwise.
Re:Bollax (Score:4, Insightful)
Asserting tht RedHat is trying to "neutralize" KDE is attributing political motives to their actions. Instead, I think, they're simply trying to sell more copies of RedHat Linux.
Re:Bollax (Score:4, Insightful)
Ehm, this must be a matter of opinion, since I believe KDE to be putting out better quality applications (in a shorter timespan too, they are not losing their head-start, they are increasing their lead). As for "political stunts", consider this: when I think of GNOME, I think of Ximian and Eazel (the millions wasted, the strange Google ads). When I think of KDE, I think of a team of developers "getting shit done." About the only bad mark that KDE has ever had was with the old Qt licensing, which all boiled down to wanting to "get shit done" instead of worrying about licensing. If you want to talk about politics, talk about GNOME.
Maybe if they had been developing instead of throwing tantrums their applications would be the ones Red Hat had chosen instead.
Red Hat chose GNOME way back in the day, as far as Linux desktops are concerned. KDE wasn't all that great back then, and GNOME was fully GPL. I think the licensing had to do more with their decision than quality of applications (especially considering that GNOME at that time was awful). Of course, it is harder to turn back now that Red Hat promoted GNOME so much. Considering that Red Hat is the only major distribution shipping GNOME as the default desktop, I wonder if Red Hat could end the desktop war by simply switching to KDE as default? Something to think about...
It is also important to remember that the people debating this are people like you and I, not the actual core KDE developers (or GNOME developers for that matter). They are not throwing tantrums, they are coding. I'd even guess that most of them don't even have Slashdot accounts. KDE continues to have a very strong developer community that generally does not worry about things like this. Please place blame appropriately.
Re:Bollax (Score:4, Insightful)
Just the fact that RedHat and Sun both agree that GNOME is a better desktop should say a lot. Besides, even if KDE was just as good as GNOME, GNOME would still have quite a lead, as most apps are based on GTK. Loading and maintaining twice as many toolkits and libraries is a waste of system resources, and effort.
Re:Bollax (Score:3)
Shipping without KDE would probably be a good solution to all of this drama. Of course, it'd just create more RedHat-forked distros. Another, uh, Mandrake.
What they've done to KDE is a much easier way to neutralize it than not shipping it. Of course, I don't think Redhat is purposely doing this or anything.
> Do you seriously believe that Red Hat continues to include KDE because they hate it?
They probably include it to help customers who prefer KDE. *shrug*
Redhat hate (well, maybe not as strong as hate, perhaps apathy) of KDE is well known, and the opposite is true as well.
amen to that (Score:4, Insightful)
(for the KDE lovers out there, I find Gnome just about as annoying and "more unintegrated"
Re:I am with Red Hat on this one... (Score:2)
All major distributions are using KDE as default except one that is using GNOME.
In 2 months all major distributions are using KDE as default except one that is using some strange newly created mixture of KDE and GNOME.
Now you can speculate what RedHat had to do to create a unified desktop and wether their "nullifying" efforts are a step towards that goal.
Amen (Score:5, Interesting)
KDE people whining about this are going to be ignored. The GNOME people have accepted the loss of their icons without throwing fits, though it certainly changes RH GNOME's "look and feel". I can't figure out why the KDE people can't do the same for the changes that affected their "look and feel."
Re:Amen (Score:4, Informative)
RedHat should have given the user a choice at least. If the user installed KDE (not default), then by gosh, they probably wanted to run KDE.
Re:Amen (Score:3, Informative)
If someone really wants KDE, they can get it straight from kde.org -- I get a fair amount of software from the original source. The KDE project can distribute their blessed distribution however they want to do so. If you *really* want vanilla KDE with no GNOME integration done at all, then there are distros like Mandrake that *have* taken this approach...but I like seeing the diversity among distros that characterizes Linux. If someone wants to make a distro that has a totally terminal-based UI through an X server and AAlib and runs Enlightenment...well, they can do so. The users will end up voting by using whichever they prefer -- it could be that Red Hat is doing the wrong thing or the right thing. People will try both, and comment on them. RH will probably polish things up in 8.1, and if people still don't like the approach...well, Mandrake will get them.
Re:Amen (Score:4, Insightful)
This is little more than an elaborate theme and a default set of applications.
It has nothing to do with "slowing down" KDE or "removing choice". It has to do with delivering a common user experience across both desktops.
If you don't like it, don't use it!
If you don't like it, and have to use it, change the config to something YOU can live with.
I don't get what the hell is so hard to understand about this relatively straightforward concept.
Re:I am with Red Hat on this one... (Score:5, Insightful)
It is a common misconception in these discussions that people are mad about the unified look and integration between KDE and GNOME that Red Hat is promoting. Nothing could be further from the truth, and I hope I can speak for all KDE fans when I say the unified look is a step forward, and integration is good. After all, people have been crying out for both for years. But what Red Hat is including is not KDE, it is simply KDE's panel used to launch other applications. The panel is not what makes KDE compelling, it's the app integration. If Red Hat wants to use GNOME app defaults, then what are they doing including KDE at all? It is a joke, simply so they can put "KDE desktop" on their boxes.
I am also not trying to say that Red Hat should drop all KDE support. No matter what, Red Hat should include libraries to run KDE apps, and I don't think anyone would argue otherwise. If they aren't going to use KDE app defaults, though, they might as well not include KDE as a choice on the login screen. There is no reason to.
Re:quit whineing (Score:3, Informative)
Maybe because there are third-party apps that use KDE libraries, just like there are third-party apps that use GNOME libraries. I just wish more people would realize that wanting to have GNOME and/or KDE installed is not always necessarily the same as wanting to have the look-and-feel of GNOME/KDE.
what exactlly are they doing? (Score:2)
is this not the case?
Re:what exactlly are they doing? (Score:5, Insightful)
AFAIK, it is the case. RedHat's trying to do something for people who aren't emotionally involved with either KDE or Gnome -- make a consistent, usable desktop. I think this is a good thing to do. KDE and Gnome are working together these days (see freedesktop.org). This is encouragement from RedHat to make KDE and Gnome more interoperable. If they don't interoperate, then there make as well be two entirely separate types of desktop linux -- KDE linux and Gnome Linux. Vendors would need to pick one (or both) to support.
Macs have a default interface. Windows has a default interface. Linux systems should as well. Note that you can run QT programs on Windows and MacOS -- similarly, you can use the toolkit of your own choice on a Linux system. But having a default desktop system would be a good thing for Linux in the desktop arena.
I wish (Score:5, Funny)
Re:I wish (Score:3, Insightful)
Re:I wish (Score:4, Insightful)
As for me, personally I am curious and interested to see what RH has done with the desktop in v8, and don't feel too strongly about the KDE/GNOME/Bluecurve arguments -- and I don't know enough about whether I should agree with Bero's statements about crippling KDE.
-=Ivan
"free" software (Score:5, Insightful)
Real free software people would be against (or at least oblivious) to the branding in the first place.
Re:"free" software (Score:5, Insightful)
Re:"free" software (MOD PARENT UP) (Score:5, Insightful)
It's like people have confused 'freedom' with 'freedom do you whatever the hell you want without actually being subjected to what other people _think_ of it'. Which is a shame, because peer discussion and judgement is about the most important check/balance in society. While we try and limit the actions that can result from peer judgement (to avoid mob justice, for instance), we should try and avoid attempting to squash criticism just because its not 'productive'
When people are free to do crap, don't forget others are well within their rights to freedom to voice dissatisfaction
Re:"free" software (Score:4, Interesting)
The rhetoric being levelled at Red Hat from the KDE zealots goes way beyond mere criticism.
Re:"free" software (Score:5, Insightful)
Real free software people wouldn't be emotionally offended by others taking advantage of their own freedoms to modify the software. RedHat is doing what the GPL allows. This is what it's all about, guys -- freedom with the software you use, develop with and distribute.
Re:"free" software (Score:5, Insightful)
Okay, so if I use your XSLTFilter on a Web site that displays XML-indexed goatse pictures, you'll suddenly become convinced they're the most attractive thing you've ever seen?
There's a deep divide between toleration and approval. As I understand it, RMS (for one) is generally speaking opposed to war. However, the GPL under which he releases his software contains no provisions preventing militaries from using it in the development and deployment of weapons systems. RMS tolerates the use of glibc in weapons -- that is to say, he doesn't try to stop it. That doesn't mean he approves of it, or wouldn't be offended by the thought of a missile guided by glibc-linked code blowing up a village in Iraq. (Hell, I'm offended by it, and I didn't even write glibc.)
The confusion between toleration and approval (or between taking offense and being intolerant) is a dangerous one, like the confusion so many people have between criticism and censorship. It is destructive of public discourse, because it leads people to react emotionally as if they were being threatened with force, when in fact they are merely being told someone's opinion.
Re:"free" software (Score:4, Insightful)
Yup, they're silly buggers, no question there.
But I don't think it's valuable to call them "fake free software people", or whatever the antonym of your "real free software people" upthread was supposed to be. I don't even know what a "free software person" is meant to be in that context -- an advocate? user? developer? We have clear criteria for what makes a program Free Software but we do not have criteria for what makes a "free software person."
I find it disturbing sometimes how much resentment there can be in the community. Whenever one of these atrocious flamewars breaks out, it seems to me that it's more because people are looking for a fight, looking for some battle line on whose sides they can form up. Quite often, it seems it's the resentful impulse that was once called levelling that serves as the impulse for this. Levelling is the harmful side of envy: instead of raising yourself up to the level of the envied one, you knock them down to yours.
Many free-software users hate Microsoft, because they observe that Microsoft has done wrong and profited by it -- but a sizable minority envy Red Hat, because while Red Hat has done no wrong it has profited where others have failed. None in this matter of KDE in Red Hat 8.0 have presented a coherent argument that Red Hat has done wrong; rather, they have seized on something unusual that Red Hat has done and unfoundedly declared it wrong, as a justification for knocking down Red Hat.
It's foolish, and in the end it drags everyone down. The negative publicity hurts Red Hat directly and the rest of Free Software/Open Source by association. The attitude of intolerance towards modifications -- that if I want to modify your code I need your explicit permission -- creates a contradiction with the operating principles of FS/OSS and works to deprive us of its benefits. The inherent ugliness and acrimony of unnecessary hostility hurts us all.
Unless... (Score:2)
Re:"free" software (Score:4, Informative)
Anyone who's used the 8.0 beta can tell you they're enhancing their usability, nmot their brand with their changes. The grab bag of different applications, inconsistent themes, and desktop specific panel apps are there if you want them. But Red Hat have made themes and panel apps consistent by default and put what they consider the best apps forward by outting them on the quick launch area of the taskbar. Its no big deal, and Red Hat 8.0s KDE runs every KDE app I've built and packaged for it.
Get Mandrake 9.0 (Score:2, Informative)
Re:Get Mandrake 9.0 (Score:2)
Mandrake tagged the final release RC3 while it was heading out to the mirrors. It will be renamed once all the mirrors get it and then officially announced.
Crippleware? (Score:5, Insightful)
Re:Crippleware? (Score:2)
Can anyone point me to a canonical listing of precisely what the KDE people are so upset about? Most of the objections I've seen seem silly, but I don't want to dismiss the issue without feeling I'm fully informed on it.
Re:Crippleware? (Score:2, Insightful)
http://people.redhat.com/otaylor/rh-desktop.htm
Anyone who's used it likes it. (Score:5, Informative)
Red Hat have:
Re:Anyone who's used it likes it. (Score:4, Informative)
> release:
But not an informed one. You left a lot out, in addition to putting the RH spin on what you included. RH has also:
- Added lots of buggy Xft stuff to QT
- Buggy changes to support vfolder
- Broke service name compatibility
- Broke plugin handling
The gruesome details are all in bugzilla.
These are off the top of my head, I've probably left some out.
Re:Anyone who's used it likes it. (Score:5, Interesting)
Since KDE has never released a proper announcement of what their issues with Red Hat beyond some generally false stuff in their forums (cheers Mosfet) and as an extensive KDE user I haven't encountered them, I may indeed not know everything.
I didn't put a RH spin on anything. Users should pick the best apps. RH aren't trying to turn KDE into Gnome - 2 of 3 non KDE their `best apps' aren't Gnome apps either. And Konq, KMail etc still work (apart from the plugin bug you mentioned). I'm a Konq fan, but at the end of the day, Mozilla can render more pages (such as www.ninemsn.com.au, the most popular site in the country) and Konq can't. And as I said, every KDE app I've rebuilt for Null has been fine.
The Xft additions seem to work well enough that I haven't noticed them negatively at all - just that for once I got Xfthack quality font rendering out of the box on a Linux distro without having to screw around. This is a good thing. I don't know what's buggy about it and when I do notice something, I spend a bit of time in Bugzilla reporting it or checking it out.
Konqueror plugisn are broken, huh? Flash works fine on www.xdude.com works fine (using the Flash 6 beta under Konqueror on the current Null). Quicktime / Crossover also work fine, albeit a little slowly than I'd like. But I accept there are likely remaining bugs in Konq plugins, as Macromedia.com doesn't work properly, and last time I looked its also in Mozilla marked for RH to fix, along with the latest Nautilus fuckups. How is this malicious? What have Red Hat done to deliberately break it? And why would they deliberately break it if they're going to fix it? You haven't said so I'll treat RH as innocent until proven guilty.
I don't know about what applications vfolders you're talking about, or what `service names are'. Care to tell or give us a bugzilla link?
Using GCC3 does not equate to sabotage. (Score:4, Interesting)
- Broke plugin handling
The gruesome details are all in bugzilla.
If I'm uninformed, then you sir, are a liar. Read the actual bug report [redhat.com] sometime. Red Hat have done nothign of the sort - they've just compiled KDE with the current GCC - Macromedia has yet to release a GCC 3 based Flash (tho it would seem Flash 6 corrects the problem). You're trying to make out that Red Hat have deliberately sabotages KDE plugins. When Suse, Mandrake, and every other distro also compile KDE with GCC3, will you accuse them of the same?
With Redhat on this one... (Score:5, Insightful)
This IS the way to better software . . . (Score:4, Insightful)
I must disagree with this. I think strong principles are a great virtue of the open source community. Instead of being less productive at a KDEless Redhat, Bero will be more productive somewhere else. This doesn't say anything bad about Redhat or Bero and only further supports the diversification (and competition) of the community.
I am sure that the majority of MS employees would not walk out if suddenly MS decided to do something as drastic as go Open Source. You may call this corporate strength, but I call it 40,000 "yes" men (and women) who don't give a fsck what their company does, as long as that paycheck comes on Friday.
He should change his name ... (Score:5, Funny)
I use gentoo (Score:2, Insightful)
And it makes sence because gnome2 is the default DE, why is it bad for qt apps to have unified look?
Gezz!
It's rather sad. (Score:5, Insightful)
I'll tell you why -- good old fashioned ego. Whereas the low end (kernel developers, compiler writers, etc.) and high end (clustering software, 3D modelling and rendering, etc.) of development is led by strong, well-organised teams of well-trained developers with vision and understanding, the middle ground of the Linux world is polluted with warring egos and silly spats like this. There are myriad competing, mutually incompatible yet separately inadequate office suites (Star Office, KOffice, Applix,...), desktop environments (KDE, Gnome, XFCE, CDE, UDE, ROX,...), and X servers (XFree86, MetroX, XiG). We can't even decide on a printing system! If all the man-hours poured into fighting over KDE and GNOME were combined into a common vision, we would have one perfect end-user desktop, instead of two poor imitations of Windows.
Don't give me the old "competition" argument either. There is only one Linux kernel, which seems to progress just fine without another competing project nipping at its feet and instigating flamewars. The endless KDE vs. GNOME, Applix vs. StarOffice, and other feuds have wasted more productivity than would be gained by and competitive drive.
I, for one, am somewhat miffed that while my operating system powers Hollywood blockbusters and NASA supercomputers, it still can't fully replace Windows on my office desktop. Linux is growing up; its users need to grow up with it, shed their egos and work towards the common goal of creating an excellent working environment.
Re:It's rather sad. (Score:5, Insightful)
When I implement rendering software, its very easy to tell if my approach or your approach is better; bench mark.
Now hell me how to objectively detemine which interface is better: KDE or GNOME?
I think its obvious that there is always going to be way more arguments about what the handles and knobs looks like than whether or not that engine is implemented in the best way possible. You can quantitatively test and compare all the kinds of software you say that doesn't suffer from the problems KDE/GNOME do
Re:It's rather sad. (Score:4, Insightful)
You missed the VM system flamewars? The scheduler fights? The CML2 flamewars starring ESR? The kernel developers are by no means an egoless hive-mind, noiselessly producing good code. Read kernel-traffic [zork.net] for a little taste, or delve into the linux-kernel list raw & unfiltered for more than you evidently expect in the way of competition.
If you want to look for "Not Invented Here" mentalities and competition between kernel projects in the free-software world, consider also Linux vs. BSD. As I understand it, there's no reason that OpenBSD's pf firewall module -- which has some serious advantages over Linux's netfilter -- could not be integrated with the Linux network stack. It hasn't been, though, and I don't imagine it will be.
Kernels can be fighty places, too.
Re:It's rather sad. (Score:2, Interesting)
>There is only one Linux kernel, which seems to progress just fine without another competing project nipping at its feet and instigating flamewars.
And how exactly can you say the kernel wouldn't have progressed faster with competition ? If you lack any comparison element how can you tell ?
And in the long run...See yourself in 10 years; you have this incredible feature to integrate in a desktop. But badluck, at this time the comitty steering the UNIFIED DESKTOP doesn't deem your idea interesting (always remember that very bright people can fail to see - planck's idea took a long time to get through, and he was talking with the best crop of physicist of his time). Well, if there's a second project...you have 100% more chances to get your idea through. And both might consider your idea a bit more, being cautious that they could lose it to the other side, just in case.
Or you don't have that second destop solution: maybe you'll fork the UNIFIED one yourself, thus ten years later proving yourself wrong.
Na, I think it's better with competition. Safer on the long run.
Re:It's rather sad. (Score:2, Interesting)
I disagree. Of course you might like to have everyone work on the same thing - but these are volunteers who work on what gives them enjoyment. You can't get them to work on a common environment - the best you can achieve is common interface standards, and that is happening.
With this environment then you do get competition, because each camp wants their side to win. This moves each side on faster than it would without the other. We don't know whether one environent will become THE ONE (the others will not disappear immediately - if at all - but will continue anyway as a minority solution).
As for your one kernel. The kernel development goes through the same thing, look at the number of competing file systems.
Re:It's rather sad. (Score:5, Insightful)
I think you're mistaken in assuming that computationally enormous is equivalent to hard. Designing and optimizing a Unix-ish operating system is a solved problem. It's been done well for decades by some really smart, well-funded people and there's plenty of experience and available source to draw on.
The desktop is hard. Apple and Microsoft still haven't gotten it down pat and the CDE guys completely failed at it. I remember a few years ago the attitude was, "We have graphics toolkits, and we've made Windows-like desktops with icons and toolbars. Thanks to the power of open source, we'll have Mac/Windows quality desktop apps in two years!" (I'm quoting the royal "we" of Linux enthusiasts.) It turns out that it's a lot harder than that, and that the devs at Apple and Microsoft and Adobe are a lot smarter and more innovative than a lot of the Linux xealots gave them credit for.
Re:It's rather sad. (Score:4, Interesting)
For math papers, OpenOffice works *better* than the MS equivalent, and for many tasks, makes more sense than using Maple or Mathematica. And Open Office is wonderful for writing in French, or any other Western language.
When other people say "The Desktop" they're not talking about work, they're talking about Entertainment. And there are real shackles, very high barriers to entry in that arena, that have nothing to do with one piece of free software versus another, and everything to do with the hostility of hardware makers and industry associations!
But that's the "desktop" as an entertainment venue, and not as a workplace. Because of the current state of affairs where we are willing to accept (1) unnecessary expenses and (2) distractions from functions that apply to work tasks, we seem to find things like "windows" and "osx", or even "gnome" or "kde" to be reasonable items to have in a workplace -- because those are the things we are accustomed to.
Why is the Windows Solitaire program considered a tolerable standard feature on a business machine? Why is it that even in environments demanding hardcore accountability, strict adherence to schedule, and zero loss, we find any such systems? What stopped there being a "next level" in workplace equipment?
Re:It's rather sad. (Score:5, Interesting)
And even the lower levels have their problems. There might be one Linux kernel (excepting -ac and other myriad branches and patches), but there's also BSD, Mach, Darwin, and the Hurd out there.
As for "simple" things like reading Word documents, you try reading a document that's really and collection of embedded COM objects and see how well you do with it. Things like that aren't easy. On the other hand, I can read and write my windows partition, as well as many other file systems, quite easily in Linux, which is something Windows can't do now. I also have virtual desktops, which is simple to implement in your WM using X, but Windows can't do this "simple" thing by default. Every environment has its advantages and disadvantages.
All those diseparate projects like KDE/Gnome, OO/KOffice, etc. will either learn to cooperate or one will die out. KDE and Gnome have very very slowly been taking steps to meet on some levels, and distros can step in at other levels (like Debian's excellent menu system). OO and Koffice are working towards using the same file format, or at least being able to read and write the same formats. Things will get there, just be patient.
Oh, and incidentally, I get better frames in Q3 on Linux than I do in Windows.
Specialized vs. diverse use of an OS (Score:4, Insightful)
Re:Amen (Score:4, Insightful)
And what about Debian or Slack, quite arguably the two most "pure" distros of all? What gives Redhat the power to dictate the desktop environment for them?
The fact is, for most desktop developers, having Linux take over the mainstream desktop isn't the priority. It's providing the best desktop software on the planet for themselves and their users. This whole "Linux vs. The World" is just some childish notion that attempts to shoehorn people. A big part of Linux is that it is Free Software, and with that comes the freedom to choose what you want. Distros have their default desktop, but that shouldn't interfere with me in any way.
You people are missing the point (Score:5, Insightful)
An employee of RH was being asked to work on something he disagreed with. So he left.
KDE is free to moan, RH is free to mod KDE, and this guy is free to get employment elsewhere.
Personally, it restores some of my confidence in humans. At least we're not all wage slaves who couldn't give a rats ass what they were working for and who they were serving.
Re:You people are missing the point (Score:5, Interesting)
I agree with you 100%. But I can also see where some people are worried. A respectable man disowns a company he works for over political reasons such as the modification of KDE, and it will make people question the company. Things like this will always bring rise to the Redhat/Microsoft comparison that happens way too often.
BUT the whole Lemming mentality happens way too often as well. Someone respectable leaves something like redhat behind, and all of the sudden people think it's tainted. Now, don't get me wrong. In a situation like this, questions do arise in my head. But I further research an analyze the situation. Perhaps our hero doesn't want to modify KDE because he thinks it works BEST the default way. Makes sense. But I'm willing to try out the new modified version before I agree with him.
So I announce now that I will go against the grain, and I will at least try out Redhat 8.0 before I denounce it. I will try Xandros too, and the latest Debian, and so on. I'm an OS mosquito, I go where the brightest light is.
Quitting... yeah, that'll help (Score:2)
I'm sure that, since he is no longer an employee, he'll have even more influence over RedHat's decisions.
I think it would have been better for him to demonstrate a better way -- such as making a set of RPMs for RedHat 8.0 available for how he thinks KDE should be. I remember downloading RPMs from ~bero in the past.
Over reacting? (Score:2, Insightful)
I'm sad to see him go, I hope things work out for him.
Seems a pity for Bero to leave RedHat over this (Score:2, Interesting)
However, I can understand why redhat is standardising its interface this and I'm not sure it is a bad thing. The difference between KDE and Gnome _IS_ confusing to new users, and it is somewhat ugly to mix GTK and QT apps on the screen at the same time. I think that KDE and Gnome should compete on the technical merits of their class libraries, not on how pretty their default install is.
Consider Ximian, Lindows, etc. They all modify kde to look like windows. Why is it ok for them to do that, but no ok for RedHat to give all their programs a similar look-and-feel.
Anyway, I hope financial reasons won't mean Bero is no longer able to contribute to the open source community.
Re:Seems a pity for Bero to leave RedHat over this (Score:2)
Ximian modifies KDE? When did this happen?
Please explain crippleware. (Score:5, Insightful)
Furthermore, it is my understanding that the default KDE themes are in there and simply need to be selected from the configurator. How is this crippling it.
To go one step further, I see a fair bit of ranting, especially on Slashdot(go figure), about how bad this new Red Hat theme is. The thing is, if you don't like it change it. How many people actually continue to use KDEs default themes? Few if any, I'll bet. Pretty much everybody changes the desktop to their own preferrences. So, what's the big deal about selecting your own preferrences over the Red Hat theme versus selecting your own preferrences over the KDE themes?
Much ado about nothing....
Re:Please explain crippleware. (Score:4, Interesting)
However, what they're doing is not very nice, and it isn't at all about themes and icons...if that's all it was, there would be no issue.
First there was the issue of the removal of the "About KDE" item in all KDE app help menus. From Redhat's point of view, they're trying to make a Redhat-branded desktop, so seeing "About KDE" in some of the apps might be confusing to the user. From KDE's point of view, if Redhat "de-brands" the desktop, then the about box is really their only chance to let the user know about the app's authorship. It *really* makes it seem like Redhat is, if not trying to take credit for the apps themselves, then at least trying remove credit from where it's due (the KDE devs).
I don't know for sure, but I think Redhat may have decided to replace the "About KDE" items. Time (or beta testers
Second, and more importantly, they have replaced KDE apps with equivalent apps, either from GNOME or independent projects. For example, they replaced konqueror with Mozilla, Koffice with OpenOffice, KMail with Evolution.
Some people say these alternatives are better anyway, so who cares? Is KDE just whining because they can't keep up? I don't think so. For one thing, even if you change the widget style, these apps aren't going to be very well-integrated into the rest of the desktop, both in terms of look-and-feel and interoperability with other apps. This tight integration is one of KDE's great strengths; without it, KDE is, well, crippled. Plus, since these apps depend on libraries that are not preloaded when KDE starts up, they will appear to be sluggish to the user, who might incorrectly conclude that KDE is slow and clunky.
In summary, it isn't about themes or icons. It's that Redhat removed all trace of KDE from the apps, and replaced core KDE components with alternatives that are likely to confuse and frustrate users.
So what? (Score:5, Insightful)
Redhat isn't violating anyones license, and they've done so much for the free software movement. If you don't like it, send em an email. Then, shut up. Its not your company.
This is not meant to start a flamewar (Score:3, Interesting)
Besides 'nicety' issues (it would be nice if RH didn't do this) and besides marketing reasons (obviously having a consistent interface is very desirable) can anybody explain any legal reason why RH isn't allowed to do what they are doing?
As far as I remember, when you GPL your software, anybody can do practically whatever they want with it as long as they provide it at cost (duplication costs) and as long as they publish their (modified) sources.
If you don't like the way RH ships their preconfigured Gnome/KDE desktop, well, uninstall the provided packages and install the ones you can download from ftp.kde.org and so on.
The people that would be interested in having a 'pure' KDE and/or a 'pure' Gnome, are technically inclined people which are more than capable of doing what I just outlined: I really doubt that your average non-power-user cares at all about this, as long as they can use mozilla, openoffice etc. I don't think they'd care.
If you have licensed your software under a specific license (GPL, BSD, Artistic...) and a licensee does things to your software that you don't like, well, maybe you didn't think long & hard enough before opting to use the license you've been using. The only solution is to decide on a new license (good luck in getting everybody to agree) and to fork the codebase under that new license, but it's definitely not a painless or sometimes even possible solution (given the 'viral' nature of the GPL).
Re:This is not meant to start a flamewar (Score:3, Insightful)
Nope. There is no legal reason for them not to - they are allowed to do this. I'm also allowed to walk up to your finace right before you get married and tell her that in my opinon, she's a mongrel whore, thus ruining your wedding. Both acts are not morally sound, however. RedHat has committed source patches to change some of the fundimental UI for KDE (including the one possible legal violation, removing the About KDE, which lists the authors as copyright owners and the GPL as the license the application is distributed under), and that's not, in the open source world, considered a nice thing to do. Sure, it's legal. Doesn't mean that they aren't being asses.
--
Evan (no reference)
Re:This is not meant to start a flamewar (Score:3, Insightful)
Why is it considered "insightful" to compare Red Hat's effort to unify Gnome and KDE to calling someone's fiancee a mongrel whore on her wedding day?
Just to be safe: consider your wedding invitation from me to be cancelled :-).
If you insist on KDE's moral right to have an About box on the desktop, then every other author of everything on your system has the same right. This was the problem with the old BSD advertising clause (which required that blurbs of the author's choice had to be displayed by the system and appear in all documentation); the GPL folks have always rejected this concept.
Free software is a bazaar. If folks don't like the GUI changes, Red Hat will come under pressure to change them; if people do like the GUI changes, KDE will come under pressure to accept them.
If the KDE folks act too much like control freaks, they risk losing control of their own project. This happened to RMS a couple of times, with the emacs/xemacs split and the egcs split, although the latter split was healed when RMS surrendered control of GCC to the egcs team. Some aspects of what Red Hat did to KDE are arguably broken, others are arguably improvements. If the KDE folks have a good attitude, the result could be a better KDE. Otherwise, I predict that other distributors will emulate Red Hat's approach, and KDE will lose control of what KDE looks like on other distros as well.
I have used the beta. (Score:2)
I just see this as an honest effort from redhat to make things simpler for the user. They could just as well just plain dropped the KDE desktop and only included the libs.
Why do some of you even complain when you outright screamed when OEM's couldnt remove ie or change icons in windows?
Crippling KDE??? (Score:2)
Re:Crippling KDE??? (Score:3, Informative)
It might be considered premature, but its the direction things are moving in both the GNOME and KDE world. One thing that is rarely pointed out by the khicken littles is that this code hasn't been declared stable for GNOME either.
>changing KDE service types (thus, breaking third
>party kde apps that use kparts/ktrader.)
They only changes the binary names. The whole point of ktrader is that you don't *need* to hard code names or paths.
Matt
ha ha (Score:5, Funny)
Developers developers developers developers developers!
What should Red Hat do? (Score:5, Insightful)
Now Red Hat is trying to integrate KDE into their distro seamlessly. The KDE guys don't like this at all.
What should Red Hat do to make these guys happy? I think the only way the KDE guys would be happy is if Red Hat puts in KDE without changing anything. Great, now Red Hat has two different install options that look and work very differently. What a support nightmare. So, Red Hat would have to budget more money for support of KDE, or else just say it isn't supported... in other words, push GNOME and ignore KDE.
So it looks like the only way the KDE guys will be happy is if Red Hat goes out of their way to increase their support costs. Let's face it, if it is going to cost money to keep the KDE guys happy, Red Hat isn't going to do it!
P.S. Calling the Red Hat version of KDE "crippleware" isn't helpful. Red Hat isn't trying to hurt KDE; they are a business, and how does hurting KDE make money for them?
Any bugs Red Hat introduces to KDE will increase their support costs. People who buy Red Hat call Red Hat when they have trouble.
Red Hat is doing this so that a user can run KDE apps or GNOME apps without really caring which is which. Some of the KDE guys are complaining that Red Hat will make KDE look bad. The idea is that no one will even notice whether they are using KDE or not.
steveha
Re:What should Red Hat do? (Score:3, Insightful)
On a side note, those who download RedHat for free don't get some of that support without paying. If it becomes a large known issue, a patch goes up. If it's a minor issue with only a few people, I would expect RH to charge them service fees.
How do you think companies with free software/OS's make money? One of the big ways is support.
Not quite. (Score:5, Funny)
Whooptie doo (Score:2)
All this kvetching and martyrdom bullshit from the KDE developers is just that. Pissed off that someone is using your code in ways that offend, insult, or annoy you? Fork the codebase and develop under a more restrictive license. These pointless martyrdom gestures and venom-laden rants only make you look dumb and childish.
Re:Whooptie doo (Score:5, Insightful)
He's not trying to be a martyr. He's trying to have a job in which he agrees with the things he's asked to do. It's those who remain in the job at the expense of their happiness that are the dumb and childish ones. Whether or not KDE is "cripplewear" in RH is besides the point; he has set of values, he's actually going to do something about it
Exactly WHAT is Red Hat doing to cripple KDE? (Score:2)
Through all the flames and accusations, the only thing I've definitively concluded Red Hat is doing is changing the default themes & colors & such so that KDE apps and GNOME apps behave as identically as possible, in order to minimize interface confusion for users. Maybe they're doing other stuff, but I haven't got a straight answer.
WHAT IS RED HAT DOING TO KDE? While we're at it, are they doing similar stuff to GNOME?
KDE on RH 8 (Score:4, Interesting)
Of course I knew this story would get posted (Score:2)
Of course what do the editiors care? They just light the fuse and walk away. It the bystanders who end up getting hurt.
Now this useless blown up story about a developer who disagreed with his employer will spread all around the internet.
I look forward to tomorrow's frontpage of Cnet, NY Times etc where they all say the entire opensource community has turned on Redhat. And also how the split between Gnome and KDE is ripping the community apart, and maybe a little Linux is too fragmented FUD as well.
Did I say thanks already?
Quit? (Score:2)
Sooner or later... (Score:2, Flamebait)
RedHat pushes GNOME and GNOME was only created to kill KDE. (Yes, you can mod this down, but it's still the truth and you know it.) RedHat doesn't like KDE and the only reason there were KDE-packages (other than those included in the RedHat releasees) was Bero creating them in his spare time. Yes that's correct, RedHat did not pay their "KDE-maintainer" to create packages for KDE-releases.
If you look at non-technical usegroups, you will see that in areas where KDE-centric distributions dominate (like SuSE does in Europe), about 5 to 15% of users post with Linux, while Linux is pretty much non-existant in American usegroups (although Linux has risen very much in the last months, it's still usually less than 5%).
Coincidence? Maybe. I didn't do statistics on all newsgroups.
(Yes, I do know that usegroup users are not representative for the all computer users, yet is proves that Linux can be used by A LOT of users on the desktop RIGHT NOW and that no magic "formula" is needed. The software is available RIGHT NOW.
Will RedHat's attempts to "nullify" their desktop make it more successful on the desktop? I don't think so (Will GNOME apps use KDE's great printing dialogue that lets you create or even email PDFs? No. Will GNOME PIM apps be aware of the KDE-counterparts? No. Creating a theme does not solve any problem), anyway we will see what happens. They certainly can't do any worse on the desktop than they are currently doing.
Re:Sooner or later... (Score:5, Informative)
Actually, it's false, and I suspect you might not know it. GNOME was created by the GNU folks as an alternative to KDE at a time when KDE was dependent on a piece of non-free software, specifically the Qt libraries. Though it's now Free, Qt was at the time "shared source," more or less. Once Qt became Free, people kept developing and using GNOME because they were used to it and had come to prefer it.
They did it for the same reason RMS started GNU in the first place: to give people who insist on Free Software a good system to use. RMS didn't start GNU to "kill" SunOS or HP/UX or BSD, but to have the kind of system that his ethics and aesthetics preferred. Yes, BSD was non-free when GNU was started: BSD depended on AT&T proprietary Unix code. That quit being the case in 1994 or so -- but you wouldn't expect all the GNU and Linux developers to suddenly jump ship for BSD, would you? Of course not; as with GNOME and KDE, they had come to prefer their own system and kept developing it because they wished to.
That's called freedom. Not "killing" -- freedom. Learn to recognize it.
Re:Sooner or later... (Score:3, Insightful)
I disagree. That's like saying Window Maker wouldn't exist without KDE, or that FluxBox wouldn't exist without KDE. I believe there are certain irreconcilable differences between the two development groups, and that multiple Linux desktops are inevitable. Even if KDE or GNOME ends up "winning the war" and becomes the de facto standard for all the major distros, and more importantly, for ISV's, this will STILL not change the fact that there will be multiple Linux desktops. That's the double-edged sword of Free Software - if you don't like it, you're free to try something else. This leads to a lot of initial divisive fighting, but eventually it ends up creating incredible software - look at the great FreeDesktop.org standards! The more of those standards KDE and GNOME pick up, the lower the bar is for users to switch between desktops. Basically, we can have our cake, and eat it, too.
Re:Sooner or later... (Score:4, Informative)
If you know the truth of proposition P (viz., that the purpose of the creation of GNOME was other than to "kill" KDE) but you assert in debate proposition not-P (that the purpose of creating GNOME was to "kill" KDE) then you engage in a wrongful act of lying. There is no place in intelligent debate for lying. The only purpose lying can serve in discussion is to attempt to lead another astray -- to cause another to think or act on the basis of information you know is wrong. Though lying may serve some useful purposes in certain social occasions (contra Kant) it has no justification in debate and is wholly immoral.
Now, back on topic -- license problems may not be a "real life" issue to you if you are neither a Free Software developer or distributor, nor of the opinion that secret-source, thought-monopoly software is harmful. However, not all the world is in the same boat you are. To a substantial number of people -- among them the GNU and GNOME core developers, self-evidently -- these are issues most assuredly real. They would be remiss in their ethical duties to set aside their own principles simply because a fool might someday mock them as impractical.
Re:Sooner or later... (Score:3, Informative)
-Hope
hmm (Score:2)
Oh, and guess what: you don't have to use Red Hat. I don't. Funny how the world works. no?
Who do I (Score:5, Funny)
Open Soap Opera (Score:5, Interesting)
On minute we have a bunch of Linux zealots beating their drums and putting a bead on the back of Microsoft, bent on unseating Microsoft whenever and where ever they can.
The next minute, someone actually in a position to move that goal forward, and they're crucified for it.
Get over it, or get your priorities straight so I can either dump my MSFT stock or buy more of it (seriously). If the goal is to make Linux a viable and flexible operating system, then people need to understand that their Open Source projects may be co-oped by someone else and modified. It's the rules of the game, the nature of the beast.
If the goal is to create software with your name all over it, a web site that tells everyone what chic and dastardly cool programmers you are, then that's ok too. But don't yell about Microsoft and how Linux would make it all different.
What about normal users? (Score:2)
Personally, I think trying to make it so users DON'T KNOW NOR CARE what the underlying libraries are makes sense, the resulting system will become much easier to use. If the KDE apps are crippled, then that's a problem, but I'd expect that to be fixed in future releases. More importantly, it's likely that this process will encourage more reuse between the groups, and that's a good thing.
The scoop (Score:2, Flamebait)
HERE IS THE ANSWER EVERYONE.... (Score:5, Insightful)
From the article:
"Red Hat's new "Bluecurve" desktop interface, a customization of the traditional KDE or Gnome interfaces."
Translates too:
Red Hat decided - instead of using just KDE and Gnome to add Bluecurve which is a modified version of KDE that is "more user friendly"
Former RH employee
"I don't want to work on crippling KDE, and they (Red Hat) don't want an employee who admits (Red Hat) 8.0's KDE is crippleware,"
Translates too:
I think the majority of linux users will not want to use this "user-friendly" crap because linux users are all power users and red hat is dulling themselves down just to try and bring more noobs to linux and make some money and i'm too self-righteous to be involved in that hideous plot.
The words "Cripple KDE and former RH employee" appear on Slashdot and the masses go crazy....
Try it? (Score:4, Insightful)
Try it for god sakes. Before you bitch about it or even see it, just try it. Wait until Redhat 8.0 comes out, get a copy, install it, and check out the GUI.
If it sucks big-time, then flaming is somewhat justified. If it works better than what has gone before, then either use it or go crawling back to your old glitchy GUI versions and feel that hollow satisfaction that your whining was warranted.
Seems to me, the only way anyone wins is if it's an improvement - phorm
So how does he get income now? (Score:4, Funny)
As an out of work programer, I can tell you first hand that this is not the enviorment to quit in if there is any other choice. Mind you his reasons for leaving are good, but it is aweful hard to get a job today. Maybe he has name recignition to get one, but there are a lot of good programers (and many bad ones too I suppose) who are looking for work.
Good luck is all I can say. If you find a job, please think of the rest of us without work, and see if you can do something for us. (hint, get me a job. :)
not berorh anymore? (Score:5, Funny)
It's mind boggling (Score:4, Insightful)
This is just more evidence for the idea that GNU/Linux users don't really want to win the battle... don't want GNU/Linux to become popular... that there is an elitist attitude among many out there (myself included) that relishes the role of the underdog, and wants things to stay with GNU/Linux in that position. So we all need to reconcile these two feelings... ask the question-- do you really want to see GNU/Linux become mainstream? Further, are you willing to see the use of open-source through to its end? So far, in my experience, both of these answers have been "no".
What all the fuss is about (Score:5, Insightful)
Windows has a distinctive look-and-feel. The macintosh has a distinctive l&f. Why? Branding, branding branding! The same organisation that is responsible for the overall package -- the OS in Microsoft's case; computer in Apple's --- is responsible for the interface. The visual differences between KDE and Gnome exist for similar reasons. By replacing their respective brand-imagery with its own, RedHat now gets to gobble up the mindshare of both teams -- the only form of 'payment' that these projects really ask for --- without any sort of renumeration. Need I remind the reader how important mindshare is to the financing and ultimate success of any open source project? Would KDE have received funding from the German government if it had just been some grey nnonymous widget-maker for a couple of American software firms?
Sure, you could characterise this as a case of warring egos; but egos are essential to survival: The perfectly altruisitic quickly become fodder for the pragmatically selfish. KDE and Gnome are well within their rights to protest; their identities are their equity. That's how this market works --- regardless of the apparent legality or probity of such maneuvers under license.
Look and Feel (Score:4, Insightful)
I suspect that significant number of you assume that a common look and feel means a common theme, style, appearance, etc. But that's just the look. The sticky part is the feel. A common feel means that KDE and GNOME behave identically. Think about that one a bit. In order for the goal of a common feel to be successful there has to be major surgery on one or both of the desktops.
Here is one example that should bring the point home. Lets imagine the Fubar Dialog. Both GNOME and KDE have a Fubar Dialog that allows the user to set their snafu level. Under KDE, this dialog is modeless applies to the application snafu level. Under GNOME it is modal but operates on the global snafu level. So how do you make a common Fubar Dialog? Do you make the KDE version act globally? And what about all those applications that used the Fubar Dialog? Will you change them as well? After all, a modeless dialog is pretty useless if the application still thinks its modal. And what about third party applications (that don't come with Redhat) using that dialog?
The point I'm trying to make here is that a common feel between two desktops is a MAJOR undertaking. It's so great a task that I seriously doubt Redhat is going to be able to pull it off.
Instead of assuming that we need a common look and feel just because the convicted monopolist has one, why not treat the existance of multiple desktops as an inherent advantage to Free Software operating systems?
All we are saying (Score:2)
.
Re:The Goal? (Score:2)
Newbies don't realy care what they use. The use what you use because that means they have help at hand. Companies can standarize on one or the other. Again, just take your pick. (as RedHat basicly did with Gnome)
Old hands made their choise for a reason and are not going to like it when a distro screws up "their" gnome/kde.
Changing the picture doesn't make the programs inter-operatable either.. I wish them all the luck, but I guess it's time to pick an other distro once again here too..
Re:I agree. (Score:2)
Re:bad news for Linux? (Score:3, Interesting)
Would you care to explain exactly which KDE features are hidden? I'm using (null) now, and other than the theming I do not see any differences (I still can access the KDE control center to change my settings for example).
Re:Make the switch (Score:4, Informative)
>anymore. They go to the edge...
>
>Postfix over sendmail
Postfix was added to Red Hat in 7.3.
>Postgres over MySQL
Postgres has been in since 5.0, about five years ago. (On a side note, MySQL didn't make it in until 7.0).
>i586 over i386
Red Hat compiles -mcpu=i586 -march=i386, which means optimization for i586, but without using instructions that are incompatible with i386. The performance increase for doing -march=i586 is negligable except in a few corner cases.
However, the kernel and glibc are shipped with optimizations for multiple architectures, so as to provide most of the benefits without locking out non-pentium architectures.
Matt