Godwin's Law Invoked in Linus/Gnome Spat
lisah writes "The flame wars between Linus Torvalds and the GNOME community continue to burn. Responding to Torvalds' recent claim that GNOME 'seems to be developed by interface Nazis' and that its developers believe their 'users are idiots,' a member of the Linux Foundation's Desktop Architects mailing list suggested that Torvalds use GNOME for a month before making such pronouncements. Torvalds, never one to back down from a challenge, simply turned around and submitted patches to GNOME and then told the list, '...let's see what happens to my patches. I guarantee you that they actually improve the code.' After lobbing that over the fence, Torvalds concluded his comments by saying, 'Now the question is, will people take the patches, or will they keep their heads up their arses and claim that configurability is bad, even when it makes things more logical, and code more readable.'" Linux.com and Slashdot are both owned by OSTG.
I really think that Linus is a cool guy no doubt about that, sending in those patches to the Gnome community sure was the way to prove who is the over-geek here and how to get something done instead of wasting valuable time arguing over something as unimportant as Gnome (pun intented), if Linus is right.
;)
But Linus does really seem to have a bit of an attitude problem at times. Which is many times good if you are a boss for employees, but the problem just is that is not what Linus is, he is the boss of volenteers, they can quit if they don't like their boss.
I can't help but get a little worried, had it been anyone else but Linus I wouldn't mind, let people have their strange ways as long as they do not bother me or anyone else to much.
I am just worried for Linus, I sure hope he does take care of himself and stay mentally fit, that flamewars like the one he appearently had with the Gnome people here does not bring him out of balance somehow.
If Linus somehow gets sick and overloaded then it will lead to a whole lot of mess with the development of the Linux Kernel which really would not be nice.
So please Gnome people start behaving, be humble, accept the patches and do not upset Linus, we really need him, even if he isn't always the nicest person around
Sorry kneejerkers, but its going to require a much more detailed description of those patches than simply "cleaner and more capable" before we can make a good evaluation of whether Linus's patches should be accepted.
After all, if someone submitted patches to the linux kernel to grab the local weather report and print it out on boot, that would be adding capability that Linus would never accept in a million years because it is outside of the scope of the kernel. If Linus's patches are similarly outside the scope of the official design goals of Gnome, then any expectation that they would be accepted is just a red herring.
When information is power, privacy is freedom.
Linus, that is.
The whole point of the open source movement is to allow alternative approaches to flourish and be chosen (or not) on their merits. It's what OSS does to raise quality. The biggest problem KDE and Gnome always had was that they continually trod on each others' toes. So, let them go their separate ways - let KDE be configurable and Gnome be "designed for idiots". See who wins. Either which way the variety is good for OSS itself.
Dave
I write a blog now, you should be afraid.
This argument has nothing to do with the background or what gnome looks like morons, it has to do with the way it responds to actions, the way it presents options to the user.
The fact that linus had to take time to submit patches means the gnome developers are doing something incredibly stupid, this isn't a turf war, it means linus is concerned that the kernel he spends shitloads of time on is being trivialized by idiot programmers refusing to accept what the rest of the world wants in the systems they use.
KDE does the same shit, its annoying. I use linux daily but i have to say this is classic linux bullshit, KDE has too much, gnome has too little and no one wants to talk to each other or solve shit because everyone is in their own little camp.
Prefixes are gay as well, kstfu, ggbye
To all those Gnome fans:
There are tons of things that can be configured/fixed in Windows just like Gnome.
With some configuration tool that's only suitable for an elite bunch to use.
So, I don't see Gnome as an improvement over Windows in terms of usability.
That don't match up too well with reality. Recent GNOME is bigger, slower, and has more layers of complication than recent KDE. If you want to talk about bloat, how about using a complete deadend technology like CORBA under the hood, or using XML in places where text would do because "you just don't know"? GNOME has been working on "performance enhancement releases" for the past year or so, but KDE has gotten faster with every release since 2002 and KDE4 is expected to cut overhead even more significantly. Have you compared the dependency trees for kubuntu-desktop vs. ubuntu-desktop? The GNOME one is considerably, um, bushier. Installing a GNOME app from zero takes so much downloading, I'm glad it's automated at least. I feel real pity for the person who actually has to compile all that crap.
;)
Incidentally, spatial file management is one of the worst things ever to come out of the "if it agrees with common sense it can't possibly be right" school of interface design.
"there will be hell to pay for ignoring it"
I can't believe Linus, who has probably dropped more patches than anyone else alive, would think that sending in unwanted patches along with a *fuck you too* for good measure would think that somehow the GNOME people would suddenly change their minds.
Furthermore, projects should avoid contributors that are unable to get along even if they would make a valuable contribution. Having the additional useful developer doesn't balance out loosing the contribution of others who are offended and the loss of community around your project. I'm not making this up, just ask any HR department whether they would hire an all around offensive individual regardless of how good he is.
Honestly, I have a lot of respect for Linus, and respect someone who cares so much about the right solution. However in this case he has gone way over the line from being passionate about technology and perhaps a little quirky, into being embarrassingly out of touch with the norms of human interaction in a public forum.
-- http://thegirlorthecar.com funny dating game for guys
How do you expect a desktop environment to "discover" how quickly someone wants their panel to auto-hide or when the battery meter should change from green to yellow? Do you even know what this discussion is about, or did you just throw a generic Windows vs. Linux user-friendliness reply at it? The difference between Windows and Linux that you've mentioned is wether or not manual configuration of things like hardware is required; the issue here is developers arbitrarily removing the ability to configure software.
Everyone is born right-handed; only the greatest overcome it
Here's the link: (it was posted a bit earlier)o p_architects/2007-February/thread.html
.... But I do think that Linus needs to chill and let the GNOME core developers run the way they want to and accept or postpone (if there's a freeze) or reject his patches as they deem appropriate. If Linus want to contribute to GNOME (I hope he does), he has to do it by GNOME's rules or fork, or pass it on to someone who *is* willing to play by GNOME's rules (I'd be surprised if there weren't are more than a few developers and distros who would be willing to work as intermediary between Linus and GNOME). That's the way open source works.
http://lists.linux-foundation.org/pipermail/deskt
Basically, Linus wants to have fine grained control over what the mouse buttons do.
Sounds like a simple request, but he doesn't reveal it until *after* he submits a patch and in that same email goes on to rant about how no-one listens to him and how GNOME developers make excuses instead of just doing whatever he wants. In a later email he comments that he sent the patches to a developer's only email address (that he admits may or may not have been able to see his patches) because he doesn't like bugzilla and says that the patches must be accepted or GNOME developers are a bunch of hypocrites even though an API freeze is in effect for about a month ( http://live.gnome.org/TwoPointSeventeen ).
Personally, I find it a bit interesting that Linus has repeatedly flamed (or sidelined) people on the Linux kernel mailing list for acting like he is now, not following the kernel submission procedure, assuming that freezes don't count, and assuming that if the core architects of the Linux kernel think that a feature (done in a certain way) is a bad idea then they must be a bunch of hypocrites.
I personally don't know if the patches are any good or in keeping with GNOME's design or need changes or
It's not unreasonable to expect this. GNOME core developers don't go on the Linux kernel thread and whine and submit attitude patches to Linus, 'tho if they did, they would (and should) be flamed. Linus has said repeatedly on the kernel mailing lists that submitters must either follow the kernel rules, or fork (e.g. if you don't like the license), or pass on your patches to someone who is willing to do things that kernel developer's way (none of Reiser's patches would have gone if it weren't for this later option).
Are there problems with the GNOME way of doing things? Sure. Linus brought up a good point about the ease of submitting patches. But all projects have issues. There was a time, not too long ago, when the submission process for the Linux kernel was "send Linus your patches and if he doesn't respond then keep resending them because the patches might have gotten lost". But the issues won't get better if you complain to the wrong people.
Just my 2 cents worth.
Ironic, we're advocating choice and alternatives in the big picture by supporting an option (Gnome) that does neither.
Both of these are actually obscenely easy to deal with. If I let other people use my machine, I give them their own account and put them on GNOME. (I run straight Beryl with elements of Fluxbox.) And if you're reading an introductory book, you'll be dealing with defaults anyway.
Sane defaults, but configurability, is the way to go. And by the way, this is true of more than just Linux. I've tried to use someone else's Mac, and couldn't find the program I wanted easily because his desktop was absolutely fucking PILED with documents, something like 10 deep on top of the "hard drive" icon, making it kind of difficult to get to "Applications". Someone else's Windows, and you find they've got the status bar auto-hiding at the top of the screen. And for that matter, I use the dvorak layout, so...
I mean, I understand the point of that. That is why, for instance, game consoles are designed the way they are -- you can toss a controller to anyone and have them join the party.
But configurability can be done in such a way that it doesn't hurt usability. And, in fact, it has to be done that way, because if you nix configurability, you kill usability.
Don't thank God, thank a doctor!
So - let's see what happened here.
a) Linus bitches about something he doesn't like
b) Somebody says "Use it for a month and THEN see if you like it (which totally ignores the fact that what he's bitching about shows that he HAS, in fact, used it). Others tell him that if he's not using it, or doing something about it, he has no right to complain.
c) Linus turns around and does what he's told to - he submits patches to fix what he thinks is broken
I don't see anything wrong here. I don't see evidence of an ego. What *I* see is somebody with very strong opinions, and grounded with a basis in fact (even if you don't agree with his conclusions - which I don't), doing something about it instead of just whining.
I wish MORE people had this particular "ego problem" of Linus' - Open Source would be much further along.
I'll tell you who are Interface Nazis. The developers for software that ends with an 'imp' and starts with a 'G'.
And GNOME was developed on the UI toolkit originally developed for which famous piece of software?
Unlike you, the Gnome developers don't actually decide things based on their opinions alone, they apply widely used principles of UI design and they test their interfaces on "real people".
Gnome is doing a good job at what they're doing. If people like Linus and you want to help, learn something about UI design first. Then, you can either contribute suggestions for specific improvements justified based on accepted UI design criteria, or you can participate in user testing. Your and Linus's opinions, on the other hand, are pretty much worthless.
If you make things up you shouldn't link content which proves you wrong.
Right now, people who find Gnome 95% perfect are suffering, because it won't let them fix the last 5% and get their dream environment. And you are not doing these people any favours by telling them they should use some other environment instead, because if Gnome is 95% perfect then KDE, Xfce, Blackbox, etc. will all be worse for them.
I see your point, but it's not that simple. Like it or not, Gnome is the first thing that many people see on their way to using the software Linus does care about, which is the Linux kernel. It's like the lobby of the Linux hotel. And it's hard to blame Linus for saying "Clean up that fucking lobby, you stoners! I've dedicated my life to the internals of this hotel, they're aswesome, but once people see the filthy lobby, they run away without even noticing the good stuff!"