Slashdot Mirror


The Full Story Behind the Canonical vs. GNOME Drama

supersloshy writes this followup to our Thursday discussion of friction between Canonical and GNOME: "I've seen a lot of GNOME bashing for various reasons here on Slashdot as well as several other websites. The problem with all of this is that you never hear GNOME's side of the situation, making a lot of disrespectful comments about GNOME (or the others involved) rather baseless and illogical. Dave Neary has an extremely thorough blog post which details problems on all sides that make the issue much more complicated than 'GNOME is being idiotic by not accepting our technology.' The points covered in the blog post include, among others, how Freedesktop.org is broken as a standards body, that Mark Shuttleworth doesn't understand how GNOME works, that GNOME is not easy to understand, and that open discussions from the very beginning are important for specification development and adoption. Another blog post by 'Sankar' also covers similar points while defending GNOME."

170 of 247 comments (clear)

  1. For those without the patience... by Spyware23 · · Score: 4, Informative

    For those without the patience to read this article (which is much longer than I intended it to be when I started!), here are the headline points:

    -FreeDesktop.org is broken as a standards body
    -Mark Shuttleworth doesn’t understand how GNOME works
    -GNOME is not easy to understand
    -Deep mistrust has developed between Canonical, GNOME & KDE
    -Difficult people are prominent in each of these projects
    -Behind closed doors conversations are poison
    -For people to work together, they need to be in the same place

    Pulled from http://blogs.gnome.org/bolsh/2011/03/11/lessons-learned/

    1. Re:For those without the patience... by peragrin · · Score: 1, Interesting

      If people need to be in the same place to work how does telecommuting work?

      all conversations are behind some door that is closed, that is called being inside.

      Difficult people are behind every project it is called pride, get over it

      Mistrust develops because one side does all the work while the other complains about it.

      If GNOME isn't easy to understand then I suggest you fix your design issues. it is a GUI not a rocket ship.

      if GNOME isn't easy to understand how can anyone including mark shuttle worth understand it?

      --
      i thought once I was found, but it was only a dream.
    2. Re:For those without the patience... by Daniel_Staal · · Score: 3, Informative

      If GNOME isn't easy to understand then I suggest you fix your design issues. it is a GUI not a rocket ship.

      if GNOME isn't easy to understand how can anyone including mark shuttle worth understand it?

      GNOME is two things: It is an set of code, and it is the organization and group that writes and maintains that code. It is the latter that the article is referring to. It's not easy to understand how the community of GNOME operates. And trying to get something done without understanding the community is likely to mean you'll not get anywhere, because you haven't convinced the community that it needs to be done.

      --
      'Sensible' is a curse word.
    3. Re:For those without the patience... by segedunum · · Score: 5, Insightful

      Which is kind of what you'd expect from Gnome - claim that Freedesktop doesn't work and that no ne understand how Gnome works, it's all just a big misunderstanding and everyone is equally to blame.

      Bullshit.

    4. Re:For those without the patience... by Tranzistors · · Score: 1

      Reminds me of aliens, who land on Earth, goes to the neared bar and says "Take me to your leader". To solve this problem, we need new world order!
      Also, Gnome is not a distro. I haven't seen a trend of them trying to adopt every peace of code there is.

    5. Re:For those without the patience... by Daengbo · · Score: 3, Interesting

      Perhaps most the most telling thing about your summary is that you don't understand that "freedesktop.org is not a standards body," which is clearly stated on the FD.o website. It helps with inter-desktop collaborations through specifications and their hosting. The process is very open and devs are welcome to contribute, fork, and modify specifications. You said "Mark Shuttleworth doesn’t understand how GNOME works," but apparently, GNOME doesn't understand how FD.o works. "The log in your own eye ..." and all that.

    6. Re:For those without the patience... by Anonymous Coward · · Score: 5, Informative

      Freedesktop.org is not a standards body. From their website, "freedesktop.org is not a formal standards organization[...]" Anyone can get subscribe to the mailing list and propose a "standard." Anyone can get a Bugzilla account and a git repository there. They encourage "de facto specifications" - if you're already doing it and think someone else should do it too, write it up and send it out.

      Mark Shuttleworth does not understand how GNOME works. He believes there is technical leadership, either somewhere in the GNOME foundation or elsewhere. There isn't. New directions are taken in GNOME by people who are able to motivate. If you can't code and can't convince someone else to code with you, you won't get anything done in GNOME.

      GNOME is not easy to understand. This is evidenced by Mark Shuttleworth, a very smart man and a leader of one of the largest GNOME-pushing Linux distributions, not understanding how GNOME works. For that to happen, GNOME must be difficult to grok. It's also evidenced by the chatter on Slashdot and elsewhere that suggests that GNOME's leaders should step up and lead. There are no leaders. No one is in control. Maintainers of individual modules do what they want, guided by consensus, intuition, and experience.

      Deep mistrust has developed between Canonical, KDE, and GNOME. The last few weeks' explosion has made that clear. Everyone mistrusts everyone else.

      Difficult people are prominent in each of these projects. GNOME has their fair share of jerks. Check the mailing lists around the time of the StatusNotifier spec proposals and you'll see who's who. KDE also has their fair share of jerks. See the same mailing lists at around the same time. Canonical also has jerks, although this may be less clear. Their employees tend to have less of a presence on public mailing lists than GNOME or KDE people. To many in the free software community, not developing upstream or contributing upstream makes you a jerk. That's up to you to decide.

      Behind doors conversations are poison, as we can see from Mark Shuttleworth's blog post. He claims that Ted Gould (a Canonical employee) had a conversation with Jon McCann (a GNOME developer) and that in that conversation, Jon said libappindicator sounded great. Mark wasn't present at this conversation. Jon McCann claims the conversation never happened. As far as I know, Ted hasn't weighed in yet (but I doubt he'll contradict Mark). We outsiders can have no idea what really happened. What we do know is that, without a public record, this is a huge clusterfuck of a communication problem. If they had held the conversation on IRC with a logger, or on a mailing list, or documented the conversation on a mailing list or a Wiki afterwards, this whole blow up might not be so painful. in the free software world, conversations must be public.

      For people to work together, they must be in the same place. The Ubuntu Developer Summit, GUADEC (GNOME coference), aKademy (KDE conference), and regular hackfests (often sponsored jointly by Canonical and the GNOME foundation) show that being together in the same place helps.

      I'm not sure what you're calling bullshit in your post. You didn't really explain. I've tried to show that the claims in the original article seem to be true. Perhaps you think the claims don't go far enough, and the author should have singled out GNOME for punishment or blame?

    7. Re:For those without the patience... by MrvFD · · Score: 1

      Did you happen to notice that the section 5 in that blog post was possibly talking about you? Read especially carefully the last paragraph of it. The article was well-thought and was not to defend GNOME but actually the best piece of writing I've seen in a long time. Too bad there are dismissive and nonconstructive people in at least /. discussion boards, always.

    8. Re:For those without the patience... by Alef · · Score: 1

      Uh... how is this +5 Insightful? The parent has clearly not RTFA, and is contributing nothing to this discussion except making broad statements about people associated with Gnome and assuming bad will.

      The article, which I actually found was a rather good read, states that "FreeDesktop.org is broken as a standards body". Considering that the front page of freedesktop.org says "freedesktop.org is not a formal standards organization", this doesn't seem like an overly controversial statement.

      And by the way, how can Gnome even claim anything? It is a project, not a person. It would be more to the point to say "what you'd expect from Dave Neary" (the article author), although equally uninformative unless you tell me why.

      I am personally not involved with any Linux desktop development, but as an "outsider" reading about this debate and trying to understand what is going on, the parent's post doesn't give me any insight.

    9. Re:For those without the patience... by segedunum · · Score: 1

      Exactly what you've described in your post, that's what. The 'Freedesktop isn't really a standards body' is the usual excuse that has always been wheeled countless times to justify decisions that have made things more difficult for free desktop developers and users. It doesn't answer or solve anything.

      Unfirtunately, you haven't shown anything. You've simply repeated Dave Neary's blog post.

    10. Re:For those without the patience... by segedunum · · Score: 1

      Ha, ha. I love it when people write stuff like 'clearly not RTFA'.

      Stating that Freedesktop is a broken standards body doesn't help anyone or anything, and is the usual classic excuse - as I'd stated. Guess who one of the main partes are who has made Freedesktop 'broken'? The blog doesn't address that. Using the Freedesktop disclaimer is just an excuse basically. It won't cover the fact that certain things were being agreed, and then simply reneged on and left to stagnate.

      It's the usual wishy washy nonsense you get to cover up what the real issues are.

    11. Re:For those without the patience... by Alef · · Score: 1

      Stating that Freedesktop is a broken standards body doesn't help anyone or anything, and is the usual classic excuse - as I'd stated.

      If you're going to discuss how to improve collaboration, doesn't it help to establish what the facts are?

      I'm also not sure why you interpreted it as an excuse. Maybe my lack of involvement in any of the Linux desktop camps robs me of the ability to properly read between the lines. But if there is ambiguity, why choose to interpret it in the worst possible way and assume bad intentions, instead of responding to what is actually being said?

      The fact that TFA is met with that kind of non-constructive attitude actually rather lends the author credibility that anything else. Maybe the Gnome people are the only unreasonable ones, but you don't make it seem that way by calling what at least appears to be a well reasoned article "expected bullshit".

    12. Re:For those without the patience... by Ginger+Unicorn · · Score: 1

      Difficult people are behind every project it is called pride, get over it

      No, it's called insecurity, and since you don't understand this, it is probably something you should try to get over too.

      --
      (1.21 gigawatts) / (88 miles per hour) = 30 757 874 newtons
  2. The problem is that both sides are wrong ... by tomhudson · · Score: 5, Insightful
    GNOME has a long history of "NIH" (not invented here), and Canonical has developed a reputation for trying to boss developers around (like when they wanted all the major projects to sync their release schedule with Ubuntu).

    In the end, they're both going to be irrelevant. GNOME shell is too late, and doing it their own way, going further away from what most people want in a desktop, and Unity is already outdated when you compare it to what's happening in the tablet world.

    So a pox on both their houses. They sort of deserve each other.

    1. Re:The problem is that both sides are wrong ... by MrEricSir · · Score: 2, Insightful

      They're both going to be irrelevant?

      Great, because the "screw you guys, I'm doing it my own way" mentality has worked SO well in the past for Linux on the desktop.

      --
      There's no -1 for "I don't get it."
    2. Re:The problem is that both sides are wrong ... by ChunderDownunder · · Score: 1

      GNOME shell is too late, and doing it their own way, going further away from what most people want in a desktop, and Unity is already outdated when you compare it to what's happening in the tablet world.

      I tend to agree in that phones and tablets will see a general erosion of the relevance of a desktop OS. 'Apps' are in vogue, whether they be html5-based (webOS), embedded java (Android), objective-c (iOS) or Qt (Meego)

      In the case of Meego and, to a lesser extent, webOS the prevailing use of standard Linux components under the hood raises the question of whether we need a traditional Desktop Environment. These phone environments are set to make a splash on tablets. Does the addition of a keyboard and mouse disqualify there use in a desktop setting if they've been shown to scale up at least to XGA resolution? e.g. If webOS can host Qt and Gtk+ programs via the addition of X11, who needs a fancy 'shell', when the same card-based UI on one's palm pre becomes just as applicable on a 1080p screen?

    3. Re:The problem is that both sides are wrong ... by Stormwatch · · Score: 1

      Since "app" is short for application, you can say apps have been in vogue since the EDSAC was built, in 1949.

    4. Re:The problem is that both sides are wrong ... by ChunderDownunder · · Score: 1

      Maybe so. Language evolves; current usage centres on pocket touchscreen programs, a trend you would acknowledge?

      Semantics aside, my point being that as the phone OS successfully scales up to XGA screens (iPad, Android 3), the distinction between a tablet OS and a desktop becomes greyer. If a phone OS can seamlessly add support for hosting 'desktop' applications such as gimp, lyx, gnumeric, supertuxkart, Eclipse etc then at what point do we need a Gnome or KDE 'desktop' exactly?

    5. Re:The problem is that both sides are wrong ... by yoasif · · Score: 1

      Not even Apple (where the "app" store naming seems to be most popularized from) denies that it is about pocket touchscreen programs. Witness the Mac App store...

    6. Re:The problem is that both sides are wrong ... by ChunderDownunder · · Score: 1

      I'd agree with you if the trend wasn't towards Apple regaining the desktop in terms of redefining it away from the traditional WIMP interface they popularized way back in 1984.

      The 'OS X app store' is the adoption of a successful business model by OS X and eventual fusion the two operating system cousins. Rather than being merely a repackaging of existing desktop software, it's a gradual blurring of the distinction between phone and desktop OSes.

      Soon any iOS title will run natively on OSX, from the same app store, from the same download. OS X then just becomes a beefed up environment to run additional software titles such as Photoshop.

      The same touchscreen 'apps' on iOS will conquer the OS X desktop, via mouse and touchpad. If Apple can supply 9.7" capacitive tablets in 2010, it's only a matter of time before we'll see that as standard in their desktop displays too.

      Any wonder HP is keen to deploy webOS on every piece of hardware they ship?

    7. Re:The problem is that both sides are wrong ... by Bing+Tsher+E · · Score: 1

      How is NetBSD 'completely irrelevant'?

      I can't watch Youtube videos on my NetBSD box. Why should I have to? Why does it matter whether the companies you feel are important pay attention to it or not?

      Part of the reason I like NetBSD is the absence of hot dogs and cowboys in it.

    8. Re:The problem is that both sides are wrong ... by the_womble · · Score: 1

      That seems to be where Enlightenment is going. The current release of E17 has both desktop and small screen flavours. It is very good and I have switched my family to it (the light version of PCLinuxOS E17 to be exact).

      That said, KDE does a lot more than just provide an application launcher. I still use KDE apps with a lightweight desktop because I cannot find anything else that supports remote file browsing and editing anything like as well as Konqueror and Kate. Those work well because of the seamless support for SFTP and other protocols provided by KDE.

      Less importantly, I also cannot find a Linux RSS reader as good as Akgregator that does not have at least as heavy dependencies as its on KDE. Again, it uses common KDE components such as KHTML.

    9. Re:The problem is that both sides are wrong ... by GooberToo · · Score: 4, Interesting

      GNOME has a long history of "NIH"

      That was all started back when Miguel was creating the project. Don't get me wrong, I prefer Gnome to KDE but Miguel really screwed things up with one exceptionally poor decision after another - almost all of which is firmly rooted in the NIH-mantra. Its a tradition many were seemingly happy to carry on. Sadly, NIH is almost always a sign of significant personality flaws. This is turn easily feeds back into the lack of leadership, lack of formalization, lack of documentation, and lack of communication. All are traits of people who are actively trying to hide their work from peers until, hopefully, it can be forced down their throat within minimal review and criticism. Though admittedly, there are other factors which can justify this type of behavior too; especially if you're trying to jam it down the throats of completely unreasonable NIH personalities. Doesn't make it right, but it doesn't make it understandable.

      Again, I use Gnome daily but it doesn't change the fact that Miguel created a really bad architecture, creating poor implementations of various technologies because of NIH, then created a collection of like-minded yes men, who then proceeded to create one kludge after another trying to fix the cluster fuck of bad ideas and implementations originally created by Miguel. Literally, the project has been primed for this cluster fuck since its inception. And you note, both editorials clearly say, "NIH" and that the GNOME project is structurally broken. I've been literally saying this for years now. I've not followed Gnome for several years now and none of this is the least bit surprising to me. Not one bit.

      While the telecommute comments are pretty dumb, he is correct in that communication for any large project is required - though physical presence absolutely is not., contrary to his assertions. Regardless, they desperately need to adopt some formalized process if they hope to salvage the project. Looking at projects like Python's PEPs would be an excellent start. But then again, for them to move in that directly likely isn't possible with the current mix of personalities because it means being reviewed and criticisms early and often, which all too often is in stark contrast with the personalities involved.

      I seriously hope they get things resolved. But if they don't, KDE is looking pretty strong these days. I just don't want to have to have both sets of widgets and frameworks loaded to maintain my preferred applications.

    10. Re:The problem is that both sides are wrong ... by ladoga · · Score: 1

      It's been working pretty doggone well for me on my desktop (variously dwm, e17, and awesome on different machines over the past 7 years), but then I don't see the need to engage in a dick-waving contest about marketshare -- it's not like, even if the year-of-Linux-on-the-desktop never comes, it will lose its utility for us who do use it.

      I wish I had some mod points to mod this very important comment up. Too many people today are treating Linux as some sort of popularity contest.

      People coding open source should continue to fork and create whatever they need or want. One of the main advantages of Linux used to be that there was no need to make compromises due to market. Having everyone and his mum to do the same thing kills the innovation and limits the choice. If our niche is gone many of us could as well be using Windows.

    11. Re:The problem is that both sides are wrong ... by moonbender · · Score: 1

      Ridiculous snap judgments there, with zero explanation to make them any more valuable.

      How the hell do you know what people want in a desktop and who are the people you're referring to? Since Gnome Shell is too late, would it have been more successful a couple of years ago? So the people you're referring to wanted a shell-like desktop earlier, and now they don't?

      And how can Unity be outdated compared to the tablet world? At first glance, that's just nonsensical -- Unity is not, primarily, a tablet environment, it's designed to work with very different hardware -- medium to (multiple) extremely large displays, keyboard+mouse, existing desktop applications. That setup is here to stay for a long time still, and it needs some kind of software driving it; that software is not iOS or Honeycomb.

      Ignoring all that, a comparison can be made between the two worlds of desktop environments and tablet environments; but I don't think the desktops have a lot to be worried about in that regard. Tablets are nice -- nicer than desktops -- for a number of tasks, but working with multiple applications at the same time, organizing files, things that are at the core of desktop environments (along with providing other central utility applications) are not strong points for tablet environments. Sure, you can argue that most people prefer single-tasking and not having to worry about the file system -- though you didn't, you just obliquely referred to Unity being outdated in some manner -- but I think multi-tasking is here to stay for a long time and in the end you do have to organize your stuff somehow, whether you do it via the filesystem or in iTunes and Picasa.

      --
      Switch back to Slashdot's D1 system.
    12. Re:The problem is that both sides are wrong ... by tomhudson · · Score: 1

      Unity is not, primarily, a tablet environment, it's designed to work with very different hardware -- medium to (multiple) extremely large displays

      It was originally designed for netbooks.

      Ubuntu founder Mark Shuttleworth unveiled a new lightweight user interface shell called Unity. The new shell is designed to use screen space more efficiently and consume fewer system resources than a conventional desktop environment. It will be a key component of the Ubuntu Netbook Edition and a new instant-on computing platform called Ubuntu Light.

      In other words, it's designed for a dying market - netbooks, squeezed out on both sides by tablets and cheap laptops.

      And there's no reason why the current tablet environments can't use a mouse and keyboard, same as the current desktop environments can use a touchscreen.

    13. Re:The problem is that both sides are wrong ... by moonbender · · Score: 1

      And there's no reason why the current tablet environments can't use a mouse and keyboard, same as the current desktop environments can use a touchscreen.

      Yes and there's no reason why a dog can't wear shoes and a suit. They don't, though. And from what I've read, using a keyboard/mouse in a tablet OS -- to the degree that it works at all -- is about as enjoyable as using a touchscreen on a Linux desktop. Which is to say, not very pleasurable at all. And using a netbook is a lot closer to using a regular PC than it is to a tablet device, obviously! I've been running regular Gnome on my desktop, I don't think that'd work on a tablet. Similarly, I can just about imagine running Unity on my dual-screen desktop -- even if it was originally deployed on netbooks. (Not that I'm a big fan: I've tried it on my netbook, and there's still a lot of polishing left; I'm just not sure if Canonical is up to the task of creating a decent shell more or less from scratch.)

      --
      Switch back to Slashdot's D1 system.
    14. Re:The problem is that both sides are wrong ... by tomhudson · · Score: 1
      Why would using a mouse and keyboard be a problem with a tablet OS on a desktop? HP is doing it with WebOS.

      As for Canonical, expect to see layoffs and cost-cutting like crazy within the next 2 to 3 years.

    15. Re:The problem is that both sides are wrong ... by ToasterMonkey · · Score: 1

      GNOME has a long history of "NIH" (not invented here), and Canonical has developed a reputation for trying to boss developers around (like when they wanted all the major projects to sync their release schedule with Ubuntu).
      In the end, they're both going to be irrelevant. GNOME shell is too late, and doing it their own way, going further away from what most people want in a desktop, and Unity is already outdated when you compare it to what's happening in the tablet world.

      So a pox on both their houses. They sort of deserve each other.

      Errrrrrmm.. *SHUDDER* Listen, "NIH" might be a real problem.. somewhere.. in some circles where engineers are spending too much time reinventing the wheel.

      NIH was a big thing I've heard thrown at Sun a lot, and Gnome, and other OSS projects even. "Maintain the status quo" is unfortunately not a strategy for long term success. Building frankensystems out of existing parts isn't going to move anything forward. You wind up with "Linux" which is hard to define because it has so many discrete parts moving in every different direction. If Sun had heeded everyone's advice on "NIH", Solaris 10 might look like Debian with SunOS kernel I imagine. Hardly innovative.

      I cringe when I see it tossed around at Unix systems. I know we're all proud of its decades old way of doing things, and I'm wary of the "throwing the baby out with the bath water" type problem that plagues reinvention, but come on already. The "Unix Way of Doing Things" (TM) is not enough by itself. There are huge parts of the typical Linux distro and Solaris that need do-overs. We can keep the everything is a file mantra, the under the covers openness, and the online documentation and still wind up with a totally different system.

      Look at how Unix systems have evolved from a few multi-purpose, multi-user to very many, single purpose, isolated, very few user systems. Flat files are OK, but we need programatic interfaces to them, and standardized syntax. Applications should be segregated, exportable, versioned, and out of that, WAY more protected. Services need more than a standard start, stop, status. They need export configuration, edit configuration, import configuration, quiesce, and instead of merely syslogd, they need real performance metric reporting - work/latency. Then, remote instrumentation of all the above. These are pretty basic. These are all blindingly obvious things we need. Maybe these aren't suitable for the desktop, but I'll remind you that I'm talking about UNIX here. There is no part of UNIX tradition that is worth beans on the desktop, and we can't have a serious discussion of UNIX fundamentals while raising "but, the desktop".

      I really, really hate to say this to the Unix fanclub, but try to Think Different, please.

    16. Re:The problem is that both sides are wrong ... by Desler · · Score: 1

      And there's no reason why the current tablet environments can't use a mouse and keyboard,

      You mean other than the pure inconvenience of doing so? How many people outside of nerds on slashdot have you heard go "well I'd buy a tablet if only it came with a mouse and keyboard!"?

    17. Re:The problem is that both sides are wrong ... by Desler · · Score: 1

      But GNOME itself is nothing but NIH. GNOME was founded based on FUD over Trolltech's license for Qt which was completely bunk.

    18. Re:The problem is that both sides are wrong ... by tomhudson · · Score: 1
      Who cares about "the desktop?" My kids sure don't. The desktop is dying. It doesn't matter if linux never wins the desktop wars (though I think it will, sometime before the end of the century). The desktop is already the minority computing platform in terms of sales - both laptops and smartphones already outsell desktops. Within 2 years tablets will be outselling desktops as well. Most people are probably going to want a desktop or laptop that emulates what they're using on their tablets and smart phones, not the other way around (Microsoft tried to sell PC-OS-based tablets for almost 2 decades - nobody wanted them). As for the rest, again, I have to disagree.

      They need export configuration, edit configuration, import configuration

      Just copy the appropriate files from /etc/$WHATEVER. That's a lot simpler in the long run than having to teach someone how to use a different GUI for each service ... and having to maintain them ... and having to keep them in sync between /etc/WHATEVER versions. If you can't do a simple file copy you shouldn't be touching it.

      instead of merely syslogd, they need real performance metric reporting - work/latency. Then, remote instrumentation of all the above

      Not really. Just run it in a vm and see how loaded-down your vm is, if you're into performance tuning. When you've got 12-16 cores on a single chip on desktop machines (~ 2014), you'll be giving important services their own vm simply because using processor affinity is a good way to get the best performance.

      On a side note - I decided to test the latest opensuse on my old single-core desktop. KDE, Gnome, Gnome3 - all broken video. So I'm using Enlightenment - and that old desktop is now FAST again, and no video problems at all. So I don't have icons in my program launcher. So what? Everything works faster than it does on my much newer, multi-core laptop, just because there's less bloat. I don't care about "the desktop" - I just want to run my programs :-) I think most people are like that.

    19. Re:The problem is that both sides are wrong ... by tomhudson · · Score: 1

      And there's no reason why the current tablet environments can't use a mouse and keyboard,

      You mean other than the pure inconvenience of doing so? How many people outside of nerds on slashdot have you heard go "well I'd buy a tablet if only it came with a mouse and keyboard!"?

      Please read what I wrote. I didn't say "tablets", but "tablet environments" - like when you run a tablet environment on a desktop or laptop.

      Also, look at how many people buy an external mouse and/or keyboard for their laptops, along with secondary displays.

    20. Re:The problem is that both sides are wrong ... by tomhudson · · Score: 1
      The idea of open-source projects committing to a fixed schedule of release just shows that Shuttleworth hasn't got a clue as to how linux, and open-source in general, works. Take the most core of the core components in a linux distro - the linux kernel

      Unlike at traditional software companies, there are no deadlines. The Linux kernel is done when Torvalds decides it's ready.

      Canonical would like everything to be synchronized because that helps their marketing. However, open source is a meritocracy. Good code gets picked up because people find it useful, not because of billion-dollar marketing campaigns for things like WP7..

      Ubuntu is a good example of the slip in quality when you try to meet an artificial schedule. People are complaining about how every new release breaks something. Contrast that with the market leader - RedHat. Look how long they've been between release cycles. Canonical might want more rapid releases because they need the hype. RedHat doesn't. And unlike Canonical, RedHat is profitable.

    21. Re:The problem is that both sides are wrong ... by Desler · · Score: 1

      Also, look at how many people buy an external mouse and/or keyboard for their laptops, along with secondary displays.

      And by "many people" you mean almost no one? Outside of an external mouse, I've yet to see a single average user buy an external keyboard or monitor for their laptop outside of at work possibly having a dock.

    22. Re:The problem is that both sides are wrong ... by tomhudson · · Score: 1
      Try using a large external monitor - you'll quickly add an external keyboard so that you can use the external monitor as your primary focus.

      And wireless mice are quite popular for laptops.

      Heck, mine even came with a remote control.

    23. Re:The problem is that both sides are wrong ... by snadrus · · Score: 1

      Both KDE & Gnome's footprints are shrinking with the increased sub-component sharing (display, notifications, config, packaging). Running apps from both toolkits simultaneously (Canonical's intent) will cause more sub-pieces memory sharing while encouraging devs to use the best of both toolkits likely resulting in a Gnome desktop that's mostly QT-based (See Unity-2D) with GTK being another obsolete tk to leave.

      --
      Science & open-source build trust from peer review. Learn systems you can trust.
    24. Re:The problem is that both sides are wrong ... by mldi · · Score: 1

      It matters so I can use shit that already exists and is very widely adopted. Pretty simple.

      Sure, I don't have to watch YouTube videos, but if I want to, it's really fucking nice that I was using something Big Enough to get enough attention to get some kind of Flash player (or hell, even an HTML5 browser) installed on it without much fuss.

      --
      If you aren't suspicious of your government's actions, you aren't doing your job as a responsible citizen.
    25. Re:The problem is that both sides are wrong ... by GooberToo · · Score: 1

      While true, it doesn't invalidate my comment in the least. Do an ldd several KDE and Gnome applications. Heck, even do it on what people typically think is a Gtk+ application. You've notice both tend to pull in lots from their respective Gnome/KDE environment. Which means, despite COW and shared lib sharing, you're using massive amounts of extra memory which would otherwise not be required. Granted, with larger amounts of memory becoming common these days its not the end of the world, but for the low end it can literally be a show stopper.

    26. Re:The problem is that both sides are wrong ... by snadrus · · Score: 1

      Thanks for replying. I never intended to invalidate your points as lightweight devices must consolidate on a toolkit and generally avoid things like Python that requires an extra layer of adapters. I'm fascinated about a QT-based Gnome with QT apps since none of the "experience" requires GTK specifically. A Unity-2D desktop may soon not load GTK for simple startup.

      Open-source also spreads developer brilliance across toolkits, so having all the greatest software requires running multiple toolkits which is optimizing for the user's time (given a capable machine).

      --
      Science & open-source build trust from peer review. Learn systems you can trust.
  3. Re:Kubuntu by Anonymous Coward · · Score: 1

    Seriously. I respect KDE and everything but I don't want to work with a playskool desktop manager.

  4. How it works by SuperKendall · · Score: 3, Insightful

    If people need to be in the same place to work how does telecommuting work?

    It doesn't. That's why people working remote often go visit the people they are working with, or at least they have one person who does if there are a group of them.

    Telecommuting works because there is a buffer of understanding built up by in-person meetings and actions.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:How it works by Capt.+Beyond · · Score: 2

      and I suppose the telecommuting done with most open source projects doesn't work either?

      That makes both kde and gnome are non working projects, but it seems both of them have been working for years, eh?

      How many real open source projects are done in the same building?

      --
      -- "Perceptions create reality. By changing your perceptions you change your reality."
    2. Re:How it works by SuperKendall · · Score: 1

      and I suppose the telecommuting done with most open source projects doesn't work either?

      I'll bet with way more of them than you think, the people involved have met in person.

      It doesn't work well, no. Just witness the mess here where if everyone had met in person and hashed this out you'd not see the Greater Internet Fuckwad Theory spring to life in project management clashes between projects.

      People are much more humane to each other once they have met in person.

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
    3. Re:How it works by AK+Marc · · Score: 1

      Telecommuting works because there is a buffer of understanding built up by in-person meetings and actions.

      And in the standard telecommuting situations, there is a written contract of expectations, priorities, chain of command, and such. Four volunteers who have never met each other can't work together effectively. The first opinion disagreement will result in resentment by at least one member, and more likely all four. Who is the leader? And if they just elect one, what happens the first time that leader is wrong and the other three can see it? In a business situation, if all three tell their manager he is wrong, they then do what he said anyway. In a volunteer situation, often they'll veto the "boss" leading to the "boss" quitting. But what's better for the project, doing one thing wrong (and documented well so that others can fix it) or to lose 25% of the workforce because the opinion of one person doesn't match the other three?

      Telecommuting causes lots of problems for anyone. And it greatly magnifies some of the weaknesses in volunteer collaboration.

    4. Re:How it works by Anonymous Coward · · Score: 1

      Unfortunately, the social aspect of work is as or more prevalent in open source projects than in commercial. IOW, the best way to get on the team is still to meet up, hang out with and suck up to the senior developers.

      My particular experience has been with the FreeBSD core team, which has spent the last two decades making "RTFM" an impossible choice for all but trivial contributors (contrast Linux, where at least some people are interested in creating a fair playing field, and where great success has followed).

    5. Re:How it works by jbengt · · Score: 1

      If people need to be in the same place to work how does telecommuting work?

      It doesn't.

      Except that TFA talks about developing in different "places" like freedesktop.org, Launchpad, GNOME git, Bazaar, etc. It does not talk about developing in different geographical locations or telecommuting in general.

      Canonical has a policy that Canonical development is done in Launchpad, using Bazaar. Sometimes that’s fine – if you’re originating a project, then you get to choose the infrastructure. Bazaar & Launchpad are working just fine for a plethora of projects. But when you are working with other projects, you need to be where they are.

    6. Re:How it works by Daniel+Phillips · · Score: 1

      It doesn't. That's why people working remote often go visit the people they are working with, or at least they have one person who does if there are a group of them. Telecommuting works because there is a buffer of understanding built up by in-person meetings and actions.

      You are an iTroll who has never telecommuted. Would you please quit spouting about things you know nothing about. I have telecommuted most of my professional career, at least since the internet was invented. The occasional in-person meeting is nice, but not necessary. Video conferencing works fine, IRC or similar work even better because they get the same job done without wasting as much collective time. Conferences and face to face are mostly fun junkets that are expensive time wasters. But fun, and sometimes needed to avoid cabin fever. Otherwise, telecommuting makes the open source world go round. Most of the big names work from home, as is their well earned prerogative.

      --
      Have you got your LWN subscription yet?
    7. Re:How it works by s1lverl0rd · · Score: 1

      Mozilla has a building. The Wikimedia Foundation has a building. They seem to be doing pretty well.
      Granted, that's not 'many' by any standard, but still.

    8. Re:How it works by Curtman · · Score: 1

      People are much more humane to each other once they have met in person.

      This is a good point. People are also more receptive to criticism from someone they have met in person too. For some reason in the Gnome community there is this bizarre phenomenon where strange UI decisions are enforced on their users.

      <RANT>Think: Spacial Nautilus. It was a terrible idea, nobody liked it except the developers who implemented it. The more users complained about it, the deeper they hid the settings to turn it off. I'm feeling this again with the Gnome 3 beta's. It's extremely hard to get used to this UI, and I wonder why they are trying to turn my desktop computer into a cell phone. For example they have this new "feature" called a hotspot which shuffles your screen into an "overview" mode when you move the mouse to the top left corner of ANY monitor. There are many ways to open the overview, such as clicking the button that is present at the top left corner. The hotspot more times than not happens as I click the button, so that clicking the button actually closes the thing that I wanted open.</RANT>

      Its been my impression that things like this are driving the GNOME -vs- Canonical hostility. When Canonical does research to show that its users dislike a feature, they should damn well be able to turn it off on their desktop without pissing off some Gnome developer who thinks it's really really cool.

  5. Fork it, minus all the whining by ChunderDownunder · · Score: 4, Insightful

    Gnome weren't interested? If it matters to Canonical so much, why not just contribute the necessary support into the core libs? Refactor the gnome library so it supports both the gnome way of doing things and this new-fangled KDE/unity way and can be pluggable. Strict Gnome implementations can do it their way or link your lib.

    If Ubuntu Gnome desktop (even running gnome-shell) is nicer that official Gnome, your fork will be adopted by other distros and thus 'win'.

  6. Aaron Seigo (from KDE)'s perspective by chrisl456 · · Score: 5, Informative

    blog post 1 and blog post 2.

    Enjoy.

    --
    -chris
    1. Re:Aaron Seigo (from KDE)'s perspective by GauteL · · Score: 1, Interesting

      It seems to me that Seigo could do with minding his own business in this situation. Instead his post reads like he is attempting to portray himself as more edible to Canonical than GNOME in an attempt to win them over to KDE instead. This is somewhat distasteful, although nevertheless completely legitimate. It would be a boon to KDE if Canonical decided to focus on it.

      I'm personally very disappointed with Canonical recently. The mess with regards to the Banshee referral fees was bad enough. Developing Unity behind closed doors and then expecting everyone else to adopt it afterwards was worse. The worst, however, is the insistence on copyright assignment for contributing to Ubuntu, which I sincerely hope nobody is foolish enough to fall for. Assigning copyright to a company for your own voluntary contributions is a very bad idea and this alone should suffice to explain why libappindicator has received a lukewarm reaction from GNOME developers.

    2. Re:Aaron Seigo (from KDE)'s perspective by segedunum · · Score: 4, Insightful

      Well, it is his business considering that he and lots of other people within KDE have contributed greatly to Freedesktop and it has meant that those of us trying to use desktops with applications with differing toolkits that can actually work reasonably together. For some Gnome people to then wander along and say 'Freedesktop is broken and doesn't work' is simply not helpful in the slightest, nor does it cover them in any glory.

      Oh, and Aaron has consistently been critical of Canonical over a long period of time over a lot of what they've done. That hasn't changed, although they share a little common ground here.

    3. Re:Aaron Seigo (from KDE)'s perspective by roju · · Score: 1

      he is attempting to portray himself as more edible to Canonical

      Whoa, if the problem is that the people at Canonical are cannibals, someone should have brought that up way earlier! No wonder they're not getting along!

  7. Re:Kubuntu by MrEricSir · · Score: 2

    As pointed out in the Dave Neary's blog post, the same issues of opaque communication, people who are hard to deal with, and difficulty in implementing system-wide changes exist in KDE and many other open source projects. It's not limited to Gnome or Ubuntu.

    --
    There's no -1 for "I don't get it."
  8. Don't forget the modifier by Froboz23 · · Score: 3, Funny

    If I remember correctly, Trolls get a +3 when bashing Gnome.

    --
    Take off every Sig. For great justice.
    1. Re:Don't forget the modifier by Tiger+Smile · · Score: 1, Redundant

      +3 for bashing Gnomes? I'm confused. Isn't that only for Rangers?

      --
      -- Prepared at the direction of, or to be sent to Legal Counsel, in anticipation of litigation. Attorney Client Pri
    2. Re:Don't forget the modifier by martinX · · Score: 1

      I haven't been keeping up with the latest, but do the Smurfs have any involvement here?

      --
      When they came for the communists, I said "He's next door. Take him away. Goddam commies."
    3. Re:Don't forget the modifier by anyanka · · Score: 1

      But don't forget about Gnome's size bonus to its AC...

  9. Why is gnome hard to understand? by nzac · · Score: 1

    Its not like windows, but all of the layouts i have seen (default and opensuse being the main ones) are somewhat obvious where everything is and extra features are pretty easy to ignore. Is the multiple desktops that are confusing or the bar on top?

    KDE also has some confusing interface differences form windows in some of its applications. Such as the default single click opening of files and folders.

    I am a long time gnome user and i never heard complain that the layout is confusing.

    Or did i miss the part that is about gnome 3?

    1. Re:Why is gnome hard to understand? by Gaygirlie · · Score: 2

      You're confused. They don't mean the UI is hard to understand, they mean GNOME as a loose organization of developers and goals.

    2. Re:Why is gnome hard to understand? by moonbender · · Score: 1

      Apparently arguments about how GNOME is hard to understand are hard to understand.

      --
      Switch back to Slashdot's D1 system.
    3. Re:Why is gnome hard to understand? by Grishnakh · · Score: 1

      KDE also has some confusing interface differences form windows in some of its applications. Such as the default single click opening of files and folders.

      That's only confusing if you're stuck in the Windows mindset for every little thing you do on a computer. For everyone else, single-clicking makes way more sense. If you want to open a file or folder in a graphical view, you move your mouse pointer over it and click it. If you don't want to open it, then don't click it. How hard is that to understand? The paradigm where you have to double-click on it to do something, and single-clicking does nothing, makes no sense at all.

      If it irks you that much, it is a configurable option, but for sane and intelligent people, the default makes much more sense. This is one of the things Apple has done right since the 80s. (The app-specific menu bar at top, however, is not. It made some sense in 1987 on a 12" screen, but not now when you may be using several apps across several large-screen monitors at once.)

    4. Re:Why is gnome hard to understand? by nzac · · Score: 1

      I think you missed my point (and I completely missed the point of the article thank to the opening sentence, so no one was actually calling gnome hard to understand). I was saying that if you get over the windows habits they are both reasonably intuitive on how to do things and the gnome interface is not significantly harder to understand.

      With reference to the single click opening i think its initially quite confusing if you are using it for a first time in a rush especially if you want to select something. While i agree that for normal folder browsing it could make sense. making it harder to select things (i know you can click in corner) and not being able to arbitrary single click in the file manager (to say change focus) and including that if i know what file I’m looking for i will generally use a CLI. I can see from an RSI and mouse longevity point of view it would be a good thing though a single click for a large action is not intuitive. I use gnome for would i guess you could call a more 'passive' desktop.

  10. Poorly if at all by sjbe · · Score: 4, Interesting

    If people need to be in the same place to work how does telecommuting work?

    Poorly in most cases. Telecommuting can work in some cases but only for cases where the need to communicate is either minimal or well defined. I've telecommuted (worked from home) and I'm nowhere near as productive. Most jobs involve a significant amount of communication and it is MUCH easier to communicate in person. Emails and phone calls are great but there is no substitute for face to face communication and close proximity when collaborating on a project. There are exceptions where telecommuting works great but they are and will remain exceptions for most of us.

    Difficult people are behind every project it is called pride, get over it

    There is pride and there is arrogance and they are not the same thing. Being proud of what you have done doesn't give you or anyone else the right to be a jerk.

    Mistrust develops because one side does all the work while the other complains about it.

    Mistrust is caused by many things. Every argument has two sides and in almost every case both sides have a least some (though rarely equal) legitimacy to their arguments. People are political animals by nature and if they aren't able to talk about what they are doing AND their motivations for doing so in an efficient manner, mistrust is the inevitable result.

    1. Re:Poorly if at all by garaged · · Score: 1

      Instant messagging

      Most people have enough bandwidth to even have video and audio, if that would make things easier for the team

      I have worked remote most of the time the las few years and it does work, and yes, you do need presential meeting from time to time, but those end up being quite unproductive, it's a matter of getting used to that kind if work

      --
      I'm positive, don't belive me look at my karma
  11. Yawn.... another FOSS soap opera by Anonymous Coward · · Score: 2, Informative

    After seeing similar dramas play out in other high profile FOSS projects over the years, it makes me wonder if this is how all semi-successful FOSS projects eventually end up. Politics exist in any organization, but at least in software development corporations, people have incentives to try to work things out. This certainly doesn't help the case for Linux on the desktop.

    1. Re:Yawn.... another FOSS soap opera by Anonymous Coward · · Score: 1

      No, the real difference here is that a lot more open source bickering takes place in public, while proprietary disagreements are largely kept behind closed doors.

  12. Re:Gnome does it again. by hedwards · · Score: 1

    To be honest, I used to use gnome a bit, and KDE, but I've found that they're both just way too much. I don't need or use most of the stuff they insist on installing. One of the things that I'm digging about Archlinux is that they aren't forcing you to install anything in particular as a WM.

  13. Gnome made the right choice by anomaly256 · · Score: 1

    Frankly, seeing how Ubuntu totally gimped gdm-setup, removed the ability to use remote-x and a chooser and other such *digressions* they've implemented, I'm on Gnome's side.

    1. Re:Gnome made the right choice by fwarren · · Score: 1

      How can you help. Gnome pulled the features. You could submit patches to add them back. But Gnome is not really interested in them, are they? And as long a Canonical is a gnome shop, GDM is going to be the greeter. GDM 1 still kicks butt over GDM 2.

      There is always LightDM, but you would not like that, it can be found at freedesktop.org and Dave over at Gnome has clued us in to the fact that the folks at freedesktop.org really don't have their act together.

      --
      vi + /etc over regedit any day of the week.
  14. Re:Kubuntu by clang_jangle · · Score: 4, Informative

    I don't use ubuntu but I support a bunch of people who do, and usually recommend xubuntu, which has the xfce4 desktop. Ubuntu users might want to get familiar with it now so that when gnome follows kde in snatching defeat from the jaws of victory you'll be undisturbed. sudo apt-get install xubuntu-desktop for ubuntu or kubuntu users.

    --
    Caveat Utilitor
  15. Re:Gnome does it again. by happyhacker6 · · Score: 2

    KDE is interesting and all but GNOME lets me actually get work done; it wasn't designed to appeal to a 3-year-old.

    Its not about pretty interface. It is about easy to use interface, and less options, mean less chance the interface will fit you. Remember that peoples are different, remember that small fact, that tends to be forgotten. Something that is easy/intuitive for one user, isn't for another and vise versa. Settings is exactly that, they allow the computer to be fitted for the user needs. If user doesn't know how to use them, then he uses defaults, just like in case of no settings.

  16. Re:Gnome does it again. by Gaygirlie · · Score: 4, Insightful

    KDE is interesting and all but GNOME lets me actually get work done; it wasn't designed to appeal to a 3-year-old.

    Indeed. I have myself tried KDE every now and then, all the way from KDE 3.x, and I still don't quite like it. It feels like they are simply trying to include way too much stuff and every imaginable configuration option. GNOME on the other hand feels much more consistent and clean and thus it suits my taste much better. I have only wished they'd switch over to Qt because it's quite a bit more powerful than GTK+, but in such a way as to keep the current feel to it all.

    However, it is a moot point now: with GNOME3 removing minimize and maximize buttons and more-or-less forcing people into using workspaces I will have to seek a replacement. I just happen to like minimize and maximize buttons and my current workflow, I don't want to have to learn a new one just for the sake of it being new. It would be a different matter if it was somehow more powerful and efficient than my current one, but it isn't.

    Oh well.

  17. Wait, what? by Seumas · · Score: 1

    Just a few days ago, we were told that everyone is bashing Ubuntu and then a couple days later, we all bashed the crap out of Ubuntu regarding news about their interactions with GNOME. Now we're being told that we're bashing GNOME, even though we were bashing Ubuntu/Canonical all week?

    Anyway, when I do need to use Ubuntu, I opt for XUBUNTU.

  18. Re:Gnome and KDE both suck by Anonymous Coward · · Score: 1

    Window Maker rocks!

    http://windowmaker.org/

    Rocks my eyes with utter fuglyness...

  19. GNOME's own alternative? by ThePhilips · · Score: 5, Interesting

    Dave Neary has an extremely thorough blog post which details problems on all sides that make the issue much more complicated than 'GNOME is being idiotic by not accepting our technology.'

    Let's cut the chase: does GNOME provide an alternative notification area spec?

    From all written, I can really comment only on the part about "fd.o is broken as a standards body". And all I can say is that pretty much all standard bodies work like that: they rely on cooperation. GNOME didn't take part in talk and later sent list of complaints - instead of drafting new (version of) spec. And GNOME has stopped there, at sending complaints. Standards and specs are not immovable targets, while apparently GNOME childishly refuses to take part in the process by only complaining and calling it "broken." Or I miss something?

    --
    All hope abandon ye who enter here.
    1. Re:GNOME's own alternative? by Anonymous Coward · · Score: 2, Informative

      You're sort of missing something. FD.o is a neutral place for developers from disparate desktop environments to hold discussions and throw around ideas that can be used by everyone. The discussion about the notification spec took place on the xdg@ list after it was proposed in mid-December, 2009. You can find the thread in the archives. Before being proposed as the StatusNotifierSpec, it was the KNotifierSpec. Mostly KDE developers participated in the discussion, because they had already been discussion the spec for a while. Canonical developer Ted Gould sent a message to GNOME's desktop-developer-list@ in mid-January, 2010 to GNOME developers know that a new notification spec was being developed. Dan Winship, a GNOME developer, reads the spec and voices his concerns with in on the xdg@ list. He and Aaron Seigo from KDE lightly flame each other for a while.

      A month later, GNOME developer Colin Walters (from Red Hat) asks about Canonical's libappindicator (an implementation of the StatusNotifierSpec) and its relation to GNOME. There aren't too many posts, some people like it and some people don't. Later that day, Ted Gould formally proposes the library for inclusion as an external dependency. (Note: in GNOME, an app is free to use any library it wants as long as it is dynamically loaded. Proposing the module as an external dependency allows an application to statically link the library.)

      So it seems like Dan Winship was one of the few GNOME people actually aware that the spec was being drafted and subscribed to the xdg@ list. Canonical began implementing the spec way before it was formally drafted, and way before they notified any GNOME people that development was even going on. By the time someone in GNOME who was qualified to implement the spec heard about it, it was already well on its way to done. When he went to talk about it with the authors, flaming ensued. You can decided who started it.

      There's no conspiracy or childishness on Canonical or GNOME's part. They just weren't communicating well.

    2. Re:GNOME's own alternative? by Daengbo · · Score: 2

      Why isn't every serious GNOME dev subscribed to the XDG mailing list? Heck, I am, and I'm not even a real developer. Heck, it's not even high volume, having fewer than twenty posts a month.

    3. Re:GNOME's own alternative? by Daengbo · · Score: 1

      But since we're talking about 5-20 messages per months, what good would splitting the list do? I realize that devs are over over-subscribed (which is why I pointed out the extreme low volume in my original post), but this is a particularly important list for GNOME core devs to be subscribed to. That they feel it's not important says a lot about their commitment to cross-desktop.

    4. Re:GNOME's own alternative? by martyros · · Score: 2

      Canonical began implementing the spec way before it was formally drafted

      I'd say this is the right way to do things. Before deciding on a "spec" that everyone's going to try to use, you should actually build something and try it out, to see if it's actually as useful as you think it is, and to work out any kinks.

      Of course, if you're doing that, you have to still be open to your idea being changed significantly when it encounters other people.

      --

      TCP: Why the Internet is full of SYN.

    5. Re:GNOME's own alternative? by ThePhilips · · Score: 1

      There's no conspiracy or childishness on Canonical or GNOME's part. They just weren't communicating well.

      Then the Dave Neary's claim that FD.o is broken is a clear exaggeration. Standards bodies are forums where people communicate, often providing only assistance in organizing the communication (aka standardization process). Interested parties should be willing to take part in the communication for the process to work - no standards body can force some party to attend. The goal of standardization is to help formalize the agreement within the industry - not force the agreement out of/onto the industry. (Think of standardization body as of a secretary: they can't do the standardization work for you, they can only help with the process and send the press releases.)

      --
      All hope abandon ye who enter here.
  20. Where's the benevolent dictator? by Troll-Under-D'Bridge · · Score: 4, Interesting
    From TFA:

    But then again, over the years I have heard similar feedback from GNOME Mobile participants, and people in Nokia --so it's not all Mark's fault. As Jono says here: GNOME does have a reputation of being hard to work with for companies -- no point in denying it (then again, so does the kernel, and they seem to get along fine).

    Leaving aside the question of whether it's good for an open source project to have macho leadership, I think the comparison with Linux (the kernel) isn't valid. Linux, as every slashgeek well knows, is ruled by benevolent dictator. What Linus wants, Linux gets. Or you fork the kernel, which is what most everybody does. I think the last Gnome BD was a guy named Miguel, who has since gone on to other interests.

    But perhaps more substantively, Linux differs from Gnome in that Gnome tends to be modular, while Linux is modular only in the sense you can do "modprobe fu ; rmmod bar". So even if Linux didn't have Linus, people are forced by the monolithic nature of the kernel to be more careful with the bits they insert or remove from the kernel. Modifying the kernel is a more surgical operation when compared to the more Lego-like nature of Gnome.

    Gnome's modular nature thus makes casual forking (as practiced by Canonical, et al) easier than it is in projects of a more monolithic nature like Linux and, to a lesser extent, KDE.

  21. The Desktop is Dead by HRbnjR · · Score: 1, Interesting

    Am I the only one finding myself increasingly detached from caring about the desktop shell anyhow? It's like, can we just replace the whole desktop shell with a browser and be done with it (even if all the apps are still served from localhost)?

    1. Re:The Desktop is Dead by diegocg · · Score: 1, Troll

      Indeed. Android is killing both Gnome and KDE. It is more succesful by all measures, it is already the leading "Linux desktop" (as in: "Joe User uses it"). KDE and Gnome are no better than XFCE - hacky and not very successful projects for people that doesn't want the mainstream.

      It is happening much faster than everyone expected, and I'm very happy about it - Android knows what the user want and they know how to provide it and how to compete with propietary platforms, they are not a bunch of mental masturbators who spend their time with flamewars and continuous rewrites of everything. I really hope Android extends some day their APIs to allow desktop apps and not just touch stuff, so that we can forget this old G/K stuff.

    2. Re:The Desktop is Dead by phantomfive · · Score: 1

      How would you like to run photoshop in a browser? That's a good test for how close the browser is to replacing the desktop. For myself, I also try to think of what it would be like to get a programming environment going from a browser. Right now, it's not a pleasant thought.

      --
      "First they came for the slanderers and i said nothing."
    3. Re:The Desktop is Dead by smoothnorman · · Score: 1

      And then the browser becomes the desktop and we can hate and dump that. (e.g. Cr-48) CLI projected on the left lens of my glasses and chorded keyboard inside my right shoe. Until then just watch the wrestling match over the blinky lights.

    4. Re:The Desktop is Dead by mangu · · Score: 1

      It's like, can we just replace the whole desktop shell with a browser and be done with it

      KDE is very much like that if you use konqueror as the default file manager. The way I use it is having konqueror open in the file manager profile and maximized all the time.

      Konqueror also has some nice shortcuts, like CTRL+SHIFT+L splitting the window so you can see two directories at the same time, that's great for moving files and for comparing stuff.

    5. Re:The Desktop is Dead by Sri+Ramkrishna · · Score: 1

      But your firefox browser doesn't have any options which a lot of you claim you need. If the linux desktop is indeed dead dying to the browser then GNOME has nothing to lose by that logic, does it?

    6. Re:The Desktop is Dead by Microlith · · Score: 3, Interesting

      It is happening much faster than everyone expected, and I'm very happy about it

      I know. It's so awesome that a (previously proprietary) platform is killing FOSS platforms. It'll be awesome to just burn the last decade worth of effort for a new (and totally controlled by Google, hardware vendors, and telecom carriers) platform incompatible with everything that exists.

      Android knows what the user want

      Actually, I think Apple has a better idea of what the user wants. People generally take what works well enough, and Android is extremely simplified.

      they are not a bunch of mental masturbators

      Ah, the ad-hominem. How wonderful.

      who spend their time with flamewars and continuous rewrites of everything.

      Instead, they don't communicate with the community except after the AOSP is released to the second class open source community, and there aren't any rewrites because no one else has the authority to push new things, good or bad.

      I really hope Android extends some day their APIs to allow desktop apps and not just touch stuff, so that we can forget this old G/K stuff.

      I'd care about Android being on desktops if they put control of the platform into a 3rd party's hands, rather than entirely in the hands of a corporation who could take future versions proprietary at a moment's notice. Oh and if they went back and scrubbed all the garbage like /system and /data that are left over from Android's early closed source days.

    7. Re:The Desktop is Dead by itsdapead · · Score: 1

      How would you like to run photoshop in a browser? That's a good test for how close the browser is to replacing the desktop. For myself, I also try to think of what it would be like to get a programming environment going from a browser. Right now, it's not a pleasant thought.

      The point is not the browser - we're getting to the point where you can implement almost anything in JavaScript/DOM with, maybe, some server-side scripting thrown in. Even without the browser, large software suites are getting monolithic. Photoshop is part of a huge "creative suite" with its own workflow tools and plug-in ecosystem, a graphic artist need never go near the desktop (and if a lightbox application serves your needs better than a regular filing system, why should they?) . Eclipse is another example where you could potentially handle all the workflow for a complex development job within Eclipse (again, why browse your work by file when its better organised by class/object?) - heck, you could say the same for EMACS - and either of those could be implemented within a browser. The last time I played with this - a cloud/browser-based IDE it looked promising (and rather sensible for collaborative projects).

      --
      In a survey of 100 programmers, 111111 thought that duck-typing was a good idea.
    8. Re:The Desktop is Dead by moonbender · · Score: 1

      You're not the only one. Most people who only use a computer for sending email, watching movies and updating Facebook probably feel the same way.

      --
      Switch back to Slashdot's D1 system.
  22. one, two, three, many desktops! by bcrowell · · Score: 2, Interesting

    One of the many reasons why I would never consider using an OS other than Linux these days is that on Windows or MacOS there is no (realistic) choice as to which desktop you're going to run. I use fluxbox. My wife and daughter use Gnome. I've used xfce on low-end hardware sometimes. Some people like KDE.

    If Gnome has problems, just don't use it. It's not a big deal. Apt-get install fluxbox, or apt-get install xfce4, or whatever desktop you like.

    1. Re:one, two, three, many desktops! by Nerdfest · · Score: 1

      ... and the added bonus is that you can install them all and just switch at login, with all of the software still working (for the most part). It really is hard to beat for flexibility, but loses a lot on consistency for the average user.

    2. Re:one, two, three, many desktops! by Rennt · · Score: 2

      If Gnome has problems, just don't use it. It's not a big deal. Apt-get install fluxbox, or apt-get install xfce4, or whatever desktop you like.

      I get what you are saying, choice is good rite? But no man (or OSS project) is an island. What if you love Amarok but run Gnome? Or want to use GIMP in KDE? The current hoopla is that the direction these projects are moving in will make such choices harder or even impossible in the future. It is vitally important for everyone that they sort this basic shit out.

  23. Re:Gnome does it again. by imthesponge · · Score: 1

    Yes, but it makes no sense to make things annoying for 90% of people to please the other 10%, when those 10% can change things to the way they want anyway.

  24. Re:Gnome and KDE both suck by clang_jangle · · Score: 2, Informative

    Spoken like someone who doesn't know how to configure wmaker. It's as fugly or beautiful as you make it. Fluxbox is extremely good as well.

    --
    Caveat Utilitor
  25. tl;dr by Anonymous Coward · · Score: 1

    We're a disaster, but I can point out defects in others, therefore everything's fine!

  26. Re:Gnome does it again. by bcrowell · · Score: 5, Insightful

    However, it is a moot point now: with GNOME3 removing minimize and maximize buttons and more-or-less forcing people into using workspaces I will have to seek a replacement. I just happen to like minimize and maximize buttons and my current workflow, I don't want to have to learn a new one just for the sake of it being new.

    Yeah, it is annoying how they keep taking functionality out when there's no rational justification in terms of usability. My 11-year-old daughter was running Gnome on Ubuntu Lucid, and she had her login screen all customized so it looked cool according to her 11-year-old criteria. Then I upgraded her to Maverick, and her customization went away. I spent some time trying to help her get it working again, and basically learned that it's impossible (or would require more wizardry than I possess). Try explaining to an 11-year-old why an upgrade has removed a feature that she was using and wanted. Is there some usability improvement due to removing this capability for customization? Of course not.

    But that's the beauty of open source. We have fluxbox, xfce, KDE, ...

  27. Re:Gnome decides to remove minimize/maximize butto by phantomfive · · Score: 1, Insightful

    OK, I thought that was bad, but they have a reason. They want people to use desktop pagers instead of maximize and minimize. After I read that, I tried it out to see what was so great, and indeed, having a separate pager for each project you're working on is amazing. So if it works like they expect, they will be pushing a lot of people to a better world (it drives me crazy when I see someone with a 21 inch monitor who maximizes every single window and uses the task bar to switch between them. Totally defeats the point of a large monitor).

    Overall I'd rather have those buttons included, but I rarely use them anyway.

    --
    "First they came for the slanderers and i said nothing."
  28. Jeff Waugh's Summary by Anonymous Coward · · Score: 3, Informative

    Jeff Waugh worked at Canonical until 2006 and was a member of the GNOME board until 2008. Since then he hasn't had a role in either project. He's been pumping out a series of blog posts cover this whole saga for the last few days.

    Part 1
    http://bethesignal.org/blog/2011/03/12/relationship-between-canonical-gnome/
    Part 2
    http://bethesignal.org/blog/2011/03/12/thoughts-on-gnome/
    Part 3
    http://bethesignal.org/blog/2011/03/12/the-libappindicator-story/
    Part 4
    http://bethesignal.org/blog/2011/03/13/love-flies-under-the-radar/

  29. Gnome and the gulag mentality by Anne+Honime · · Score: 5, Insightful

    The biggest trouble I have with gnome is the designers constant push to force me using my computer their way 'for my own good'. No, sorry, I won't, thank you very much. I've used almost every other GUI / desktop manager around, none has tried so constantly to take away my freedom to organize the way I want to work. To add insult to injury, Gnome color schemes and icon design always seem to lag 10 years behind current fashion. Gnome reminds me of my childhood in the cold war era. Although I was born in western europe, it feels like soviets are rolling their tank divisions through my computer. You wait months in a line waiting for next release, just to hear : 'there's no more resize button, get away, and if you're not happy, praise tell me, comrade, why would you need one ? Didn't you know resize buttons are antisocial ?'. And you end up living in a concrete shack, decorated by shades of gray, praising the vision of the komintern. Just say no.

    1. Re:Gnome and the gulag mentality by Anne+Honime · · Score: 4, Insightful

      Case in point, why on earth then, did they dropped the minimize / maximize button ? Oh, yeah... sorry to speak about consistency, everybody should know by now that consistency isn't part of Gnome's roadmap. I'm not arguing that things should be kept around forever by default, neither do I think things must change for the sake of changing. What I want is the freedom to decide what I want to keep, and what i want to drop, and the way it's displayed. Easy enough. KDE, for all its shortcomings, does that very well. You have personalities, pagers, as much buttons as you like in title bars, wherever you like, arranged as you want them to be ordered, and you can suit your keyboard shortcuts to your needs. Stuff that, Gnome.

    2. Re:Gnome and the gulag mentality by Grishnakh · · Score: 1

      While you have a point about the lack of freedom and all, the color scheme thing is totally bogus. It's the job of the distro to deal with color schemes. For instance, in Ubuntu until more recently, the default was their "human" color scheme (shades of brown), and they did this themselves rather than get it from Gnome. Same goes for KDE and anyone who complains about the colors there. If you don't like the colors, complain to your distro, or select a different distro (or just customize the colors yourself). The Desktop Environment is a framework for presenting and controlling applications, and the colors are just a configurable veneer on top of it. A distro's job is to put everything together, make sure it all works right, and make it look pretty, usually with custom colors and distro-specific logos. If your distro isn't doing that, it's not doing a very good job.

    3. Re:Gnome and the gulag mentality by Grishnakh · · Score: 1

      Sure it has. In the old days, there were 12 buttons: 1-9, 0, *, and #. Now, there's a directional pad with center button, a back button, green and red "phone" buttons, and two menu buttons, and that's on the cheap phones. And some of the buttons have additional functions, like * also being a space button. On the expensive phones, there's no buttons at all, just a touchscreen.

      Even so, they're wrong, because they always have the 1-3 buttons on the top row, and the 7-9 buttons on the bottom row. It should be reversed from that, to be consistent with calculators and computer keyboards.

  30. A pox on both houses by Anonymous Coward · · Score: 1

    I am in desktop overload. Between the Mac re-inventing the concept of "pointless flash," Microsoft ripping it off, and Gnome and KDE running in wildly divergent directions "just because they can" I have had about all I can take. I don't want some radically different Gnome Shell. I fucking HATE KDE's Plasma (what ever happened to having stuff run outside of KDE guys?)

    We have reached the point where we're all happy imitating each other, and now we're looking for excuses to be different where no reasons actually exist. We won, guys. We all have desktops on our respective platforms. We're all functional. We have window managers, file managers, a fleet of tools that do the work we need, and most of us are happy.

    Well some of us. The desktop devs can't sit still it seems. We've all imitated the Microsoft Experience (TM) to the point where it's all too predictable, and we just can't HAVE that...let's pretend we are innovators! To boldly go and all that...and to hell with the users who just want something familiar.

    Well I've had enough. I'm sick of the complexity. I'm sick of the SLOWNESS and the memory bloat. And I'm sick of having to dread the next iteration and the flights of fancy of the free desktop community.

    So I'm going back. Back to a simple window manager, and the tools needed to make it laptop-ready. My recipe is simple: X-windows + MWM. Xterm for console. Dolphin or Nautilus as a file manager, when needed. To make it laptop-ready, I need Trayer so I can run nm-applet for my network, and gnome's power manager (sorry KDE, your damn plasmids won't work outside KDE.). And hell, that's about all I need.

    Smart. Simple. Clean. And under my control.

    To hell with the desktop wars.

  31. Re:Gnome does it again. by wuzzerd · · Score: 1

    But that's the beauty of open source. We have fluxbox, xfce, KDE, ...

    IMHO that sums it up, we can all stop posting now. Both KDE and Gmoan have made my setup unusable when upgraded. Always feels like a downgrade to me.

    Now Flux: It has a nice menu that I can edit in xterm with my favorite text editor. It does NOT have a bunch of junk cluttering the screen like a desktop to annoy my ancient eyes.

    For some reason anything I install just works[tm].

  32. Canonical must take control by Anonymous Coward · · Score: 1

    If Canonical put forth the effort, they could drive GNOME wherever they wanted. Red Hat and Suse dominate GNOME because their developers step up and take charge. They become members of the release team, they become maintainers of important modules. They develop, in the open, technologies that become integral to GNOME. There's no one inside of Canonical that has bothered to do that. One ex-Canonical employee admitted that he was forced to stop contributing to upstream GTK+, stop using upstream's source control system, and stop using upstream's bug tracker. Canonical wanted the development done exclusively in Launchpad with bazaar. [1] That lessens Canonical's influence. If they had allowed that developer to continue contributing upstream, they would have 1) gained goodwill 2) improved GTK+ 3) gotten help from all the other GTK+ developers 4) positioned one of their developers in a position to take a leadership role in the GNOME project. Instead, they shut him down and forced him to work in a little walled garden. Canonical never finished the project, and it was eventually completed by other companies and volunteers.

    That was a big missed opportunity.

    [1] http://aseigo.blogspot.com/2011/03/collaborations-demise.html?showComment=1299807005600#c2417381301530751354

    1. Re:Canonical must take control by theangryswede · · Score: 1

      I agree. Placing developers in positions to become members of upstream project's release teams is something red hat does well and should be emulated. Canonical has to realize Unity sucks, and for all of Gnome's shortcomings it is far superior.

    2. Re:Canonical must take control by bkor · · Score: 1

      Pretty sure you're saying the same thing, but just to make things really clear.

      From http://live.gnome.org/ReleasePlanning/Membership:

      The release team is not directly elected, but should be representative of the GNOME community. Membership is normally by invite and recommendation when one person leaves. In theory, the GNOME Foundation board has the power to select its members and influence its decisions, but they usually don't fix stuff if it isn't broken. Not more than two release-team members can directly or indirectly have the same affiliate (similar to section 2.d of the GNOME foundation bylaws).

      Red Hat did not place anyone on the release-team. Matthias Clasen was invited. The only way Red Hat made that happen is because 1) Matthias rocks 2) he works for Red Hat. I think this matches with what you wrote, but just want to make it really clear.

  33. Re:Gnome does it again. by MichaelSmith · · Score: 1

    I upgraded iOS on my son's ipod and many of this apps stopped working. This problem is not unique to OSS.

  34. On the other hand... by IANAAC · · Score: 1

    One point you forgot to obviously include.

    - People are too lazy to read whole articles that explain everything and instead base their opinions on someone else's summary.

    When I read anything that starts with "The Full Story Behind..." I tend to discount it as just one side's agenda.

  35. I Am In Amazement by hduff · · Score: 2

    The big story is that many in leadership positions are asshats? And these egocentric farts are acting like a bunch of bitchy little girls? And their constant need for self-aggrandizement has held back the development of FOSS in general (and GNOME and KDE in particular)?

    Wow.

    That's not news.

    To summarize Neary's rant for the non-GNOME-KDE-Canonical-oriented:
    1. the leadership is not well organized
    2. the leadership does not communicate well
    3. the leadership does not cooperate well

    And Neary's solution?
    1. bring all discussion into the open (good)
    2. eliminate the riff-raff amateurs (elitist)
    3. anoint the leadership through invitation-only (even more so)
    4. coerce the asshats into behaving and cooperating with a code of conduct (delusional)

    Really? And he expects success with a group consisting in large part of infantile prima donnas?

    The current model works well enough with all those personalities involved. It's just messy and inefficient and unprofitable and not likely to lead to world domination. But it's a world where anybody can make a copy of the football and take it home with them and Neary's plan doesn't accommodate that. It attempts to offer the imprimatur of what a corporate world needs, to marginalize the 'amateurs' and consolidate power in a select few all at the expense of the chaos that makes FOSS a living thing.

    --
    "I believe in Karma. That means I can do bad things to people all day long and I assume they deserve it." : Dogbert
    1. Re:I Am In Amazement by shutdown+-p+now · · Score: 2

      To summarize Neary's rant for the non-GNOME-KDE-Canonical-oriented:
      1. the leadership is not well organized
      2. the leadership does not communicate well
      3. the leadership does not cooperate well

      I think the point #0 was that there's no leadership as such. There are a bunch of more or less influential people "driving" different areas, but there's little overall coordination. Basically, if you had a bright idea for which you'd need integration throughout Gnome, there's no single person or committee to which you can come and start a discussion (from where they can then loop in people who work on things that would be affected).

    2. Re:I Am In Amazement by hduff · · Score: 1

      That's why I work with MacOS-X now .. because I've got tired to wait KDE/GNOME/whatever never truly invent but slowly trying to catch up and getting slower and slower to implement what's state-of-the-art

      That's what you get with a developer-driven model because they only see from the code up and not the user down. They implement a better wheel rather than create a new mode of transportation. They re-arrange deck chairs on the Titanic.

      They do create new things, but those things are rarely of practical use to users. (Tabs on top, anyone?)

      --
      "I believe in Karma. That means I can do bad things to people all day long and I assume they deserve it." : Dogbert
    3. Re:I Am In Amazement by hduff · · Score: 1

      The prima donna syndrome has ruined many a software project and product. If we could harness the power of all the egos in the software development world they could meet the world's energy demands in perpetuity. The amount of energy we constantly pour into coaxing people into cooperative behaviors seems like an inefficient waste of time. And yet the problem persists.

      You can't coax these massive egos; you must shove foot up their ass.

      You get them to cooperate by requiring that all discussions be done in public, that all decisions be made in public; that all issues be solved in public; that nothing is decided behind closed doors. Then the system will work..

      Then the prima donnas can fork or cooperate. And life goes on.

      --
      "I believe in Karma. That means I can do bad things to people all day long and I assume they deserve it." : Dogbert
  36. Re:Gnome decides to remove minimize/maximize butto by Kjella · · Score: 2

    (it drives me crazy when I see someone with a 21 inch monitor who maximizes every single window and uses the task bar to switch between them. Totally defeats the point of a large monitor).

    Every time I've tired to work differently I've found that positioning windows is more work than it's worth. With efficient keyboard/mouse cooperation I can cut and paste between apps with practically zero lag and I don't typically run any monitoring apps that I'd need to keep a permanent eye on. The upside is that all the menus/buttons/panels are in exactly the same place each time. Sometimes I have some docs or specs I'd like to look at and throw that up on my other monitor, but that's more a replacement for looking at a printout.

    Complex applications tend to have rather complex interfaces of their own, I have apps with a "main" area in the center with toolbars on top, two levels of menus on the left, toolboxes on the right and status/output windows on the bottom. It's not just one double-ultra wide block of text, it's actually very nice to have a 24" monitor to fit it all.

    --
    Live today, because you never know what tomorrow brings
  37. I read the article. by drolli · · Score: 1

    and if that guy is characteristic for the gnome community, then i understand why people have problems with that community.

    1. Re:I read the article. by drolli · · Score: 1

      The style. He essentially does not ask: "What is wrong with gnome?" But he asks: "The world seems not like gnome, so what is wrong with the world?"

      IMHO these are not good starting points. I don't say he is wrong, but lets say i think his ways of dealing tith the situation dont help to spread the gnome desktop.

    2. Re:I read the article. by drolli · · Score: 1

      Can you read: i don't say that the guy is wrong, i just say the way he is addressing the problem does not help the situation.

  38. Re:Gnome does it again. by Sri+Ramkrishna · · Score: 1

    And that's exactly what is being done. You can change most things inside dconf/gconf. But designing the default GUI should be geared towards don't care which is about 90%. The default should be able to take care of 90% of what you're going to do with your desktop. Some of you people just like the comfort of being able to tweak everything. It is a hold over from the days of fvwm and twm where you had all these options. Most normal people don't interact with their user environment so intimately. They use it for tasks. The idea is to appeal to the other 75% of the planet who aren't geeks otherwise we cant' grow. So we need to change the game. sri

  39. Some criticisms of Gnome are not baseless by Daniel+Phillips · · Score: 1, Flamebait

    ...you never hear GNOME's side of the situation, making a lot of disrespectful comments about GNOME (or the others involved) rather baseless and illogical

    Some negative comments about Gnome are not at all baseless, for example the one I am about to make. Gnome is based on an outmoded hack of an attempt to build an OOP based GUI without the benefit of an object-oriented compiler. Instead is uses a collection of nasty hacks and conventions, which which I am deeply familiar because I once was deluded enough to think also that C is just as capable of writing object object oriented code as C++. It isn't. What you end up with is an unholy unmaintainable mess. Full of messy casts, and full of bugs, as Gnome has always been. And unable to express reasonable defaults for things in any powerful or consistent way, the result being that Gnome tends to have lousy defaults for just about everything. Add in a liberal does of hubris from certain Gnome maintainers, and have blinkers on regarding the limitations of the GUI toolkit, and you have a recipe for the nasty mess that Gnome has been from the get-go, and will be until somebody finally does something about it. Thankyou Mark.

    Incidentally, these comments apply equally to glib, dbus and various other crappy decorations the Gnome guys have forced on the Linux desktop over the years. At least Bonobo is gone, that goodness for small mercies.

    --
    Have you got your LWN subscription yet?
    1. Re:Some criticisms of Gnome are not baseless by shutdown+-p+now · · Score: 2

      Some negative comments about Gnome are not at all baseless, for example the one I am about to make. Gnome is based on an outmoded hack of an attempt to build an OOP based GUI without the benefit of an object-oriented compiler. Instead is uses a collection of nasty hacks and conventions, which which I am deeply familiar because I once was deluded enough to think also that C is just as capable of writing object object oriented code as C++. It isn't. What you end up with is an unholy unmaintainable mess. Full of messy casts, and full of bugs

      Funnily enough, someone realized that, and they've actually made a programming language (syntactically largely a C# derivative) that is based on the GObject object model, but which hides all of the ugliness that is inherently exposed in C. It's pretty neat, as the output you get is still usable directly from C, but your code is high-level and bug-free (at least in parts which have to do with GObject plumbing).

    2. Re:Some criticisms of Gnome are not baseless by Daniel+Phillips · · Score: 1

      Some negative comments about Gnome are not at all baseless, for example the one I am about to make. Gnome is based on an outmoded hack of an attempt to build an OOP based GUI without the benefit of an object-oriented compiler. Instead is uses a collection of nasty hacks and conventions, which which I am deeply familiar because I once was deluded enough to think also that C is just as capable of writing object object oriented code as C++. It isn't. What you end up with is an unholy unmaintainable mess. Full of messy casts, and full of bugs

      Funnily enough, someone realized that, and they've actually made a programming language (syntactically largely a C# derivative) that is based on the GObject object model, but which hides all of the ugliness that is inherently exposed in C. It's pretty neat, as the output you get is still usable directly from C, but your code is high-level and bug-free (at least in parts which have to do with GObject plumbing).

      What a perfectly horrible idea, a not-quite-C#-wanabee to hack around the fact that C is not C++. Ranks right up there with Corba, Bonobo, Gconf and a long string of bad Gnome ideas. Stupid question: if you're going to rewrite, how about rewriting in proven language rather than yet another experimental flight of fancy?

      --
      Have you got your LWN subscription yet?
    3. Re:Some criticisms of Gnome are not baseless by 21mhz · · Score: 1

      Some negative comments about Gnome are not at all baseless, for example the one I am about to make. Gnome is based on an outmoded hack of an attempt to build an OOP based GUI without the benefit of an object-oriented compiler. Instead is uses a collection of nasty hacks and conventions, which which I am deeply familiar because I once was deluded enough to think also that C is just as capable of writing object object oriented code as C++. It isn't.

      It's capable of implementing a better object-oriented system than what C++ provides, without getting distracted to the broken ways the base language does what it claims to be OOP features. And as a previous response says, you don't even have to deal with the GObject boilerplate these days if you don't have a particular need to descend into C.

      What you end up with is an unholy unmaintainable mess. Full of messy casts, and full of bugs, as Gnome has always been.

      Funny, I haven't had bugs related to improper GObject usage for quite a while. You did not really get past writing your first bits of code using GObject and learning from this, did you?

      And unable to express reasonable defaults for things in any powerful or consistent way, the result being that Gnome tends to have lousy defaults for just about everything.

      Any specific examples, with clarification on what you consider to be "reasonable defaults expressed in a powerful and consistent way"?

      you have a recipe for the nasty mess that Gnome has been from the get-go, and will be until somebody finally does something about it.

      Like what, a corporate executive steps in and cancels the open community project? You sound ridiculously like somebody who has an axe to grind and wants some retribution, but has no real ways to exact it. Sorry that GNOME developers don't meet your high demands with their work, provided for free or on someone else's money than yours.

      --
      My exception safety is -fno-exceptions.
    4. Re:Some criticisms of Gnome are not baseless by 21mhz · · Score: 1

      Stupid question: if you're going to rewrite, how about rewriting in proven language rather than yet another experimental flight of fancy?

      And what proven language would that be, honey? Surely not C++, for which hardly two compilers have been made to produce mutually compatible binaries, and which is damn hard to make bindings for any other programming environments out there? Vala code produces APIs usable from C and anything else that can link to C code, and automatically generated introspection makes it easily usable from dynamic runtimes.

      --
      My exception safety is -fno-exceptions.
    5. Re:Some criticisms of Gnome are not baseless by Daniel+Phillips · · Score: 1

      And what proven language would that be, honey? Surely not C++

      Surely c++, which rules the world at the moment. To say otherwise would be delusional.

      --
      Have you got your LWN subscription yet?
    6. Re:Some criticisms of Gnome are not baseless by billhuey · · Score: 1

      They should have built an object glue to GObject into a very mature Objective-C system and called it a day. They'd then have a migration path for existing C code and the ability to use dynamic message passing without shit like CORBA. It's a really simple solution that the GNOME community has completely ignored since development in that organization is stalled. Maybe Ubuntu will be able to pushing some changes with all of this dissent.

    7. Re:Some criticisms of Gnome are not baseless by billhuey · · Score: 1

      That's bullshit, you look at the bug list and you see all sorts of pointer object mashing bugs. Strong evidence of the ineffectual nature of GObject is how limited the OOP is in that system. Collection classes anybody ?

      You should have just eaten it and use one language like Objective C that would have allowed for migration of existing code since it's still C but with a proper dynamic messaging system. I've made this point for years but the nits in GNOME community just don't fucking get it while investing tons of work into a deadend technology like C# for these purposes

    8. Re:Some criticisms of Gnome are not baseless by 21mhz · · Score: 1

      That's bullshit, you look at the bug list and you see all sorts of pointer object mashing bugs.

      I'm sure it would be easy to provide references. Have any?

      Strong evidence of the ineffectual nature of GObject is how limited the OOP is in that system. Collection classes anybody ?

      Yup.

      You should have just eaten it and use one language like Objective C that would have allowed for migration of existing code since it's still C but with a proper dynamic messaging system. I've made this point for years but the nits in GNOME community just don't fucking get it while investing tons of work into a deadend technology like C# for these purposes

      The GNOME developers don't use C# as far as I'm concerned, unless you mean the Mono crowd which stands a little on the side.

      --
      My exception safety is -fno-exceptions.
    9. Re:Some criticisms of Gnome are not baseless by 21mhz · · Score: 1

      BTW, Vala allows integration of existing C (or C-linkable) code, as long as type information is provided for it.

      --
      My exception safety is -fno-exceptions.
    10. Re:Some criticisms of Gnome are not baseless by Daniel+Phillips · · Score: 1

      Yes, objective C would also be viable, maybe better from a Gnome mindset.

      --
      Have you got your LWN subscription yet?
    11. Re:Some criticisms of Gnome are not baseless by Daniel+Phillips · · Score: 1

      Some negative comments about Gnome are not at all baseless, for example the one I am about to make. Gnome is based on an outmoded hack of an attempt to build an OOP based GUI without the benefit of an object-oriented compiler. Instead is uses a collection of nasty hacks and conventions, which which I am deeply familiar because I once was deluded enough to think also that C is just as capable of writing object object oriented code as C++. It isn't.

      It's capable of implementing a better object-oriented system than what C++ provides...

      You're smoking something or you have never written any respectable amount of C++. C++ just provides you the mechanism, it's up to you whether you abuse it or leverage it. C simply doesn't provide the necessary mechanism and the nasty hack called GObject does not come close to fixing that.

      --
      Have you got your LWN subscription yet?
    12. Re:Some criticisms of Gnome are not baseless by 21mhz · · Score: 1

      You're smoking something or you have never written any respectable amount of C++.

      I have, that's how one learns to avoid it.

      C++ just provides you the mechanism, it's up to you whether you abuse it or leverage it.

      Yeah, right. The only useful things it provides are the member syntax and virtual methods. The rest is broken and misguided: encapsulation fail, ill-designed multiple inheritance, ludicrously complicated resolution of overloaded methods playing funny games with other language features, RTTI designed to be either slow or broken, lack of any dynamic introspection. It's very easy to misuse, and requires a lot of discipline to get right.

      --
      My exception safety is -fno-exceptions.
  40. Yay for tribalism by macraig · · Score: 1

    I see tribalism is alive and well even in the open source community. Go tribalism! Where would reality TV and genocide be without it?

  41. Re:Gnome does it again. by Sri+Ramkrishna · · Score: 1

    You can put the minimize and maximize buttons back if you want. Also if you right click on the title bar you will also be able to get minimize. Finally, as for using workspaces, what makes you think you will be forced to use it?

  42. Re:Gnome and KDE both suck by fwarren · · Score: 1

    They can have it when they pry it from my cold dead fingers.

    Heck, I have been porting my shortcut keys forward since the days of Windows 3.1 By the time 1998 came around I had been using the same set of hotkeys for 6 years.

    --
    vi + /etc over regedit any day of the week.
  43. Re:Kubuntu by eugene+ts+wong · · Score: 1

    Will doing that uninstall Kubuntu?

  44. Re:Gnome and KDE both suck by Bing+Tsher+E · · Score: 1

    And I just keep using the same old ~/.fvwm2rc file, year after year after year.

    It ain't supposed to be a fashion statement, people. geez.

  45. Re:Kubuntu by Lehk228 · · Score: 1

    i already use xubuntu on my main laptop and my netbook with automotive diagnostics harware

    --
    Snowden and Manning are heroes.
  46. Re:Kubuntu by Sparx139 · · Score: 1

    No, you select which desktop environment you wish to use (It's a drop-down list from memory) before you log in

    --
    Our culture doesn't get smarter, it just finds new ways of being retarded.
  47. Why not just fork GNOME? by pimpsoftcom · · Score: 1

    Not trolling; Conical has the resources and community though ubuntu to do it. The open source community - as far as I have seen - has always said that gnome has a heavy case of NIH. Problem with that is it leads to the idea - correct or not - that everybody in the gnome leadership are heavy handed snobs, even if that's not necessarily the case (I'm not calling them that, just noting the perspective I have seen most voiced) and I personally have never met anybody who actually LIKED the gnome-way of doing things (even people in the gnome community), only parts of the end result. Seems to me, the end result could be much better if somebody forked gnome and made them compete with themselves and not "kde verses gnome" a little.

    --
    - d
  48. Works better in person by perpenso · · Score: 1

    and I suppose the telecommuting done with most open source projects doesn't work either?

    I think the point others are trying to make is that working face to face in a common environment works better. Telecommuting in an open source project may be less optimal but it may also be the only option.

  49. Re:Gnome does it again. by Gaygirlie · · Score: 1

    You can put the minimize and maximize buttons back if you want

    Alas, there is no window list or panel and as such minimizing windows will feel completely out of place.

    Finally, as for using workspaces, what makes you think you will be forced to use it?

    I haven't tried GNOME3 myself, but from all the videos and articles on it it does indeed seem like there is no sane way of using it without using workspaces. I need to make up a final opinion once I get to try GNOME3.

  50. Does emacs have an integrated web browser yet? by perpenso · · Score: 1

    Am I the only one finding myself increasingly detached from caring about the desktop shell anyhow? It's like, can we just replace the whole desktop shell with a browser and be done with it (even if all the apps are still served from localhost)?

    Does emacs have an integrated web browser yet? :-)

    1. Re:Does emacs have an integrated web browser yet? by Xtifr · · Score: 1

      Does emacs have an integrated web browser yet? :-)

      Has had for years and years. w3m.el. I don't think its support for javascript is very good though, so it probably won't run many of the advanced browser apps. But who cares--emacs probably already has built in versions of most of those anyway. :)

  51. This will take some time to digest by erroneus · · Score: 1

    At first glance, this might seem like an ego infested, alpha male, big mustache, beer belly convention; that the lack of central leadership and process makes doing anything useful impossible.

    And yet, here I sit, using my GNOME desktop with all of its eye candy, stability, usability and a fair degree of uniformity. (Yeah, I know, there will be a flood of people who will disagree with my own description of GNOME and I don't care.) GNOME is sometimes difficult to figure out when I try to get under the hood though, so it's not all perfect either.

    This is just about all of F/OSS at any scale larger than a handful of developers involved. I might go as far as saying that this is not a problem! It is a fact of how the ecosystem works on larger scales. If, in contrast, you would like to compare this with a large company's operations, you will see the same things! You will see all of this in spite of "strong leadership and clearly defined procedure."

    If you want to believe that all of these projects are tearing themselves up into tiny pieces with their little ego wars, you will have to ignore the results these monkeys have delivered so far. For some, it is pretty easy to do. Looking at the comments above, you would not think that GNOME is on par even with Windows 1.0.

    There is the context of human reality that needs to be considered. This is EVERYWHERE and in every aspect of life. You will find this in charities, churches, weddings, family Christmas, amusement parks, ski resorts and just about any fun or "positive" place/event you can imagine. It's all a part of the human condition and everyone who doesn't understand it seems to resent and reject it as if it weren't a part of their own DNA.

    This is how it works. It might seem ugly and chaotic or ridiculous, but it's how we all work pretty much everywhere. If one thing defines human animals, it would be that we can't advance without an enemy.

  52. Re:Kubuntu by thsths · · Score: 1

    I was running xubuntu on on old laptop for quite a while. But XFCE has gone the same path as all the other desktops, and it is now too bloated to run on old hardware. Especially compositing is quite a strain on a old graphics card.

    KDE 3 was fine, so I could still use trinity, but I ended up with LXDE. It does look like Windows 95, but it is light, fast, and not in the way. Perfect for running 4 lxterminals :-)

  53. If freedesktop.org is broken, fix it! by timbo234 · · Score: 1

    AFAIK fd.o only exists as a forum for co-operation between KDE and GNOME. So it's no good for GNOME developers to whine 'fd.o is broken' since it's just as much their responsibility as it is KDE's. No one wants to go back to the mind-numblingly fucked-up design decisions evident in Linux desktops ~10 years ago where, for example, you had a separate application menu for each desktop.

    --
    Pre-canned Evolution Links for all those Slashdot holy wars.
  54. Re:Gnome and KDE both suck by Teun · · Score: 1

    KDE is not Gnome so you are encouraged to modify any part to your own liking.

    --
    "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
  55. Re:Gnome and KDE both suck by RzUpAnmsCwrds · · Score: 1

    What about someone who doesn't want to?

    Configuration options are fine if the defaults are sane. The problem that KDE and GNOME both have is that the defaults often aren't sane.

    I don't want to have to turn the minimize button back on, or get rid of the awful spatial interface, or download an add-on to get rid of the damn cashew, or change a setting to turn the desktop back into a simple icon screen, or make the clock not huge, or select sane font sizes.

    KDE gives you options for everything and then chooses insane defaults. GNOME hides the options in gconf and then chooses insane defaults.

    Why can't this shit work out of the box?

    And, by the way, Microsoft isn't immune from this either. They've had some real fuck-ups like the search dog in XP and hiding file extensions by default.

  56. Re:Gnome does it again. by Siridar · · Score: 1

    Parent's ADW homescreen link is a goatse, don't click on it.

  57. For the windows users by SmallFurryCreature · · Score: 3, Interesting

    Dear Windows user,

    If all of the above is hopelessly confusing, please try to imagine this reality. When you buy your next Dell, you can choose a UI layout for MS Windows that goes anywhere from DOS to Windows 7 to Bob. While underneath it is the latest OS. Now, you might PICK your UI layout but not all programs you wish to run support it. So you might suddenly get a Windows 3.1 window mixed with your Aero display. Google says fuck you and does its own thing whatever you picked for its browser.

    Now while there are a LOT of choices, two stand out. Gnome which looks a bit like OSX but not a lot and KDE which looks like Fisher Price did a Windows 95 skin. Both can... or could be heavily modified. That is, KDE becomes ever more modible. Gnome becomes less so.

    If you have a strong stomach http://ultimateedition.info/Ultimate_Edition_2.8/8.png this blueness is a version of Ubuntu. It is actually a good attempt but the default skin is .... well... you know.

    The silly bit is that what people often like to mod is the login screen. GDM was moddible and then it was removed. LESS functionality as a feature. That is Gnome.

    The problem is that both Gnome and KDE are suffering from "what to do next". As a desktop both achieved their goal long ago, so they wanted more and more. Is it the task of a desktop package to supply a video player? Especially video player with far less capabilities then easily available packages installed along side but not made the default? Ubuntu is NOT Microsoft after all. MS just can't go including closed sources payed for products for other companies in its offerings less the true cost of running MS and closed source becomes readily apparent (you did pay for Winzip didn't you Windows user)

    Ubuntu CAN and does included countless 3rd party apps. It doesn't have to bother with its own meager zip only archive utility, it can use any of the superior opensource apps out there (Windows user, have you not replaced MS internal Zip support with anything more capable).

    KDE especially seems to want to create a complete set of utilities... and fails... it is not that these utils are bad by itself, its notepad is far superior to MS Notepad but still hopelessly inferior to other offerings. MS can't offer those others, Ubuntu and other Disro's can. That is why it seems pointless for KDE to spend its efforts on countless apps that will be replaced instantly while its core desktop is lacking behind. Its network manager is not as smooth as that of Gnome. Its multipe windows settings is neither. Yes, they are in theory more configurable (you can set different wallpapers for each screen, you can select which soundcard should be preffered).

    But all of it shows that neither Gnome or KDE are focussed enough anymore on what the end user wants. Gnome in its drive to be simple keeps removing the capability to tune Gnome to your liking. KDE remains horribly unfocussed and keeps giving me a messy early Windows experience. BOTH can be tuned to something smoother but geez gods, not everyone wants to.

    Other desktop/windows managers? Enlightenment stuck still in some alpha state. The others focusing on low resource usage when you can't even buy a single core netbook anymore. Fully tricked out Ubuntu barely makes my computer tick over, any lower consumption of resources and my computer will shutdown.

    That is the state of Linux. Is it bad? No, I still use it daily as my main and preffered desktop but only after heavy tuning. Tuning I have done for years now. I don't mind that much but having to fight Gnome everytime because they removed yet another feature seems such a waste and I just never liked KDE.

    Do I really have to do what Vista buyers did at some point and install an older OS to keep working?

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

    1. Re:For the windows users by hduff · · Score: 1

      Do I really have to do what Vista buyers did at some point and install an older OS to keep working?

      KDE 3.x was pretty sweet. It's a shame that KDE4 had to kill it off to be accepted. Likewise with GNOME.

      Both desktop environments are doomed. I abandoned both for icewm and LXDE and suggest you do the same.

      --
      "I believe in Karma. That means I can do bad things to people all day long and I assume they deserve it." : Dogbert
    2. Re:For the windows users by joshbosh · · Score: 1

      > Fully tricked out Ubuntu barely makes my computer > tick over, any lower consumption of resources and > my computer will shutdown. lol

  58. Re:Why we don't hear Gnome's side... by toogreen · · Score: 1

    You must be using Ubuntu, cuz Gnome on my Arch desktop is damn fast (on Ubuntu it was getting slow as hell though)

  59. Sad but true by itsdapead · · Score: 1

    I think you've hit the nail on the head, there, although I'm not sure that its all about the browser. In fact, I think the desktop only ever truly lived on Mac and a few minority systems (Acorn RISC-OS is a good example in which the desktop became really central).

    In the early days, a major (unsung) influence of the desktops on Mac and other systems was that it standardised the user interface. Before then, everytbody (Wordstar, Word Perfect, Lotus etc.) invented their own UI paradigm and even tried to prevent others copying it via look-and-feel lawsuits. With the early desktops, however, there was suddenly a single way to open, save, copy files, select blocks, copy, paste etc. and a fairly consistent menu layout across all applications (at least, per-platform - Apple were litigious towards competing desktops).

    That didn't last long: pretty soon all the major software houses were trying to distinguish themselves with thier own systems of floating, dockable palettes, wizzards and unique icon designs, and started suing each other over look and feel again. In my experience, typical Windows users never really embraced the desktop (thanks partly to Windows' MDI mode) and just maximised their current application - often the only file manipulation technique they know is "Save as...". Unix/Linux suffered from the usual "Standard? Yeah we have lots of standards!" phenomenon, plus your typical *nix hacker regards a desktop as a mechanism for running 6 instances of vi and 3 xterms on the same screen.

    Add to that, the tendency towards monolithic suites of programs with their own workflow management and, often, plug-in/add-on environments (MS Office and Adobe Creative Suite being the prime examples) many users who use their computer for specific jobs don't really need the desktop.

    The browser/webapp is one influence - with no standard UI paradigm (or a choice of 3-4 if you used Java) everybody rolled their own. Now "Apps" and iOS/Android have brought the idea of the monolithic app, often with its own UI paradigm (although Android/iOS do provide standard widgets) well and truly to the fore.

    Its a pity, really - without the Desktop/GUI as a standarsing mechanism, and application writers more worried about making their product visually distinctive than easy-to-use (and often confusing those things) computers can only get harder to use.

    --
    In a survey of 100 programmers, 111111 thought that duck-typing was a good idea.
  60. Re:Gnome and KDE both suck by Xtifr · · Score: 1

    And I just keep using the same old ~/.fvwm2rc file, year after year after year.

    Really? I'm pretty sure I've had to update mine at least once in the last decade. :)

  61. Re:Kubuntu by Entrope · · Score: 1

    Yes. In particular, it means there are a bunch of prima donna types among open source developers and advocates. Usually this is a good thing, but you will sometimes get these kinds of spats because both sides are convinced they're right and neither side is particularly good at communicating with people who (they think) are wrong about such important matters.

  62. Re:Kubuntu by eugene+ts+wong · · Score: 1

    Cool. Thanks.

  63. Re:Gnome and KDE both suck by clang_jangle · · Score: 1

    If you really have trouble configuring gnome or kde then slashdot probably isn't your cup of tea and this discussion is over your head. Buh-bye now, and thanks for stopping by! HTH, HAND, etc.

    --
    DUH!

    --
    Caveat Utilitor
  64. Re:Kubuntu by Daniel+Phillips · · Score: 1

    KDE 3 was fine, so I could still use trinity, but I ended up with LXDE. It does look like Windows 95, but it is light, fast, and not in the way. Perfect for running 4 lxterminals :-)

    KDE 4 is now fine as well. I run it on some pretty low spec machines (atom and worse). KDE blows the living heck out of Xfce in terms of usability, features, customization, integration and prettiness. Pretty much the same story vs Gnome to a somewhat lesser extent. I have worked with internals of both Xfce and Gnome, and they are both pretty disgusting ad hoc piles of spagetti. KDE's internal structure, based on QT and slots as it is, is relatively more approachable and capable of implementing complex component interaction with a hope of not leaking resources or getting its internal wires crossed.

    --
    Have you got your LWN subscription yet?
  65. Re:Gnome does it again. by Sri+Ramkrishna · · Score: 2

    There are some live cd's from www.gnome3.org. See how it works for you. Have an open mind. I switched from GNOME 2 to GNOME 3 and after about a week I could not go back to GNOME 2 anymore.. Also you don't need to switch until you're ready. The GNOME 2 environment is still going to be there, and GNOME 3 is going to continue to evolve adding features. What is taken away can be done a different way. As for the minimize and maximize issue.. it is a bit of an experiment. Yes, you're right that there is no window list. But you'll see your window in the overview mode. There are some things problematic specifically privacy, but otherwise in this method is better than window list. You have absolutely no distraction on that main window. You can be completely focused on the task you're working on. To understand the design decisions regarding minimize and maximize here is a blog post by Allan Day. The problem with slashdot and other venues is that they talk about lack of innovation in FOSS, but when projects strike out in a different direction they suddenly want conformity to either an apple or windows methodology. They have irrational fear that the power user will be shunted off. In many ways, nobody wants the linux desktop to succeed merely because it will no longer be in a domain of technocrats. In any case, if you want to follow the old model there are plenty of other choices I agree. But keep in mind, there is a convergence that GNOME is taking advantage of. The way I interact with my phone is very similar to GNOME 3. How many more regular users will find themselves feeling quite comfortable in the GNOME 3 because of that familiarity? sri

  66. Re:Gnome does it again. by supersloshy · · Score: 1

    1. sudo cp -t /usr/share/gdm/autostart/LoginWindow/ /usr/share/applications/gnome-appearance-properties.desktop /usr/share/applications/gconf-editor.desktop
    2. Logout
    3. Customize GDM as wanted
    4. Login
    5. sudo rm /usr/share/gdm/autostart/LoginWindow/gnome-appearance-properties.desktop /usr/share/gdm/autostart/LoginWindow/gconf-editor.desktop
    6. ???
    7. Profit!

    I hope that helps :)! You could also use gdm2setup, a program that can configure the new GDM.

    --
    "Our country is not nearly so overrun with the bigoted as it is overrun with the broadminded." -Archbishop Fulton Sheen
  67. Re:Gnome does it again. by Grishnakh · · Score: 1

    Indeed. I have myself tried KDE every now and then, all the way from KDE 3.x, and I still don't quite like it. It feels like they are simply trying to include way too much stuff and every imaginable configuration option.

    So what? What exactly is the problem with this? If you like the defaults, and don't want to change millions of configuration options, there's no one forcing you to go through them all and select your favorite one. Just don't go to the configuration menus, and leave everything at the defaults. How hard is that?

    Do you feel that, for some reason, if configuration options are present, that you absolutely MUST go through them all?

    Normal people just leave them alone, unless there's something that irks them enough to go figure out how to change it.

    The job of a good distro is to determine what the best default settings are so that users won't feel compelled to mess with the config options and will be happy with it out-of-the-box.

  68. Re:Gnome does it again. by Grishnakh · · Score: 1

    You might want to try out one of the new distros with KDE 4.6 when it finally comes out. I'm using 4.5, and it's fixed most of the stuff they screwed up in the giant 4.0-series transition, and from what I hear, 4.6 is even better and should make most people happy. Sucks that it took all this time to get stuff back to a decent state, but hopefully they've learned their lesson and won't do something like this again.

  69. Re:Gnome does it again. by Gaygirlie · · Score: 1

    Do you feel that, for some reason, if configuration options are present, that you absolutely MUST go through them all?

    I don't like clutter, simple as that. The few apps I've tried present you with a dozen toolbars, a menubar with gazillion menu entries, 3 tabs and atleast 3 different content boxes, so it is distracting.

    I could also mention how I just installed KDE4 again two days ago just to give it another try, but as soon as I logged in and tried to move the panel to top of the screen the whole thing crashed on me.. I simply left it at that :/

  70. Re:Gnome does it again. by mldi · · Score: 1

    They force on you to suspend your system on lid close,
    They decide that you don't need toolbar applets, like cpu monitor.

    OK, I was aware of the buttons thing, but I was not aware of these two things. Can you provide a source for this information? Thanks.

    --
    If you aren't suspicious of your government's actions, you aren't doing your job as a responsible citizen.
  71. Re:Technology.. by GooberToo · · Score: 1

    This is in fact, one of the areas where Miguel screwed up. There were already several very fast CORBA implementations available. Rather than using theirs, it was NIH and a much, much slower implementation was created. This had the effect of CORBA's role being dramatically reduced because so many believed CORBA was woefully too slow for any practical use. The truth is, they frequently inappropriately used CORBA (bad architecture) and wrongly blamed CORBA when in fact, it was their NIH-implementation of CORBA which was slow rather than CORBA itself.