Slashdot Mirror


Bounties for Gnome Optimization

Eugenia writes "Novell and OSNews are sponsoring the memory reduction project led by Novell's Ben Mauer by providing bounties to developers to help to clean up bloat in GNOME and related programs."

469 comments

  1. cat Gnome /dev/null by Anonymous Coward · · Score: 0

    I did this long ago by switching to xfce, what do I win?

  2. i must be crazy by soimless · · Score: 1, Insightful

    I use gnome 2.4 with about 100MB of ram

    1. Re:i must be crazy by Miffe · · Score: 1

      Nah, I use gnome 2.8 with 128MB of ram

    2. Re:i must be crazy by mickyflynn · · Score: 1

      I remember before 1.0, on 256MB of RAM with Enlightenment and the goodies like the ripple effect and stuff going on...first on a 400Mhz AMDk6II, which was hot shit at the time, then on dual Celeron 366Mhz. the lastest GNOME on this 1.2Ghz Duron with 1GB of RAM is nothing to be pleased with. Windows 2000 Pro does a snappy job, however.

    3. Re:i must be crazy by Anonymous Coward · · Score: 1, Interesting

      If you think your RAM total is 100MB, you probably are crazy :) Base 2, remember? ;)

      But yeah, GNOME is really inefficient, imho. I blame it on C and CORBA: in KDE, which is based on C++ and DCOP, it's obvious that components are integrated, and that code is shared in an object-oriented fashion. By comparison, GNOME feels like a few apps sharing a framebuffer and a widget renderer.

      It's a shame, I really want to see GNOME take off, but I think the underlying technology choices really hold them back.

    4. Re:i must be crazy by Anonymous Coward · · Score: 0

      2**6 + 2**5 + 2**2. Base 2, sir.

    5. Re:i must be crazy by Anonymous Coward · · Score: 0

      If you think your RAM total is 100MB, you probably are crazy :) Base 2, remember? ;)

      intergrated graphics controller uses system RAM.

    6. Re:i must be crazy by Tribbin · · Score: 1

      RAM-disk?

      --
      If you mod this up, your slashdot background will turn into a beautiful sunset!
  3. Gnome Optimization by Decaffeinated+Jedi · · Score: 5, Funny

    I tried to optimize my gnome once with a suit of +2 leather armor and a new red hat, but he still ended up getting slain by a bunch of kobolds.

    --
    DecafJedi
    my weblog: apropos of something
    1. Re:Gnome Optimization by game+kid · · Score: 2, Funny

      Maybe he refused to make friends with the penguin and the nautilus in the party.

      --
      You can hold down the "B" button for continuous firing.
    2. Re:Gnome Optimization by Lihtan · · Score: 1

      My gnomes all turned into cement golums. They all seem to happy out on the front lawn though.

      --
      Divide by zero hurts my brain.
    3. Re:Gnome Optimization by TrixX · · Score: 5, Funny

      That's because you used a Red Hat. You could have had better luck if you had bought him a Fedora.

    4. Re:Gnome Optimization by Anonymous Coward · · Score: 0

      Kobolds?! Eeek!
      Mine got taken over by hordes of daemons
      (the kind with sneakers, pitchforks and stuff...)

    5. Re:Gnome Optimization by OAB_X · · Score: 1

      As we all know, the red hat is not a fedora.

    6. Re:Gnome Optimization by po8 · · Score: 1

      I don't know. I think the real problem was the not giving him the right languages. Made it hard to deal with Kobold...

    7. Re:Gnome Optimization by ScrewMaster · · Score: 1

      You're lucky it wasn't a bunch of Diebolds. That would have been really scary.

      --
      The higher the technology, the sharper that two-edged sword.
    8. Re:Gnome Optimization by DAldredge · · Score: 1

      Are they one of the companies that bans most accounts before they have to pay out to those accounts?

      "March 3, 2005

      We have had lots of requests to un-suspend accounts after we run our security checks. Please remember that suspensions made by our system cannot be appealed.

      Account reviews are now taking place and we will begin making payments tomorrow as promised! Thank you for your continued support!"

    9. Re:Gnome Optimization by MyIS · · Score: 1
      See, next time you'll try to buy mail for your little paladin.

      (Score:-1 Obscure)

      --
      http://zero-to-enterprise.blogspot.com/
    10. Re:Gnome Optimization by OAB_X · · Score: 1

      I dont know, but ill let you know in 9 days, besides, I rocognized a legit site on the list of ones it rotates through (www.swirve.com).

  4. This can work both ways by AdityaG · · Score: 2, Insightful

    Money is sometimes a very good incentive, but sometimes things you work for money don't seem as much fun. It's hard to explian but it's true. When you get paid to build a system, it's not as much fun as when you build your own system. Myabe its the whole intrinsic vs. extrinsic motivation thing. My two cents.

    1. Re:This can work both ways by Drantin · · Score: 1

      It's also a different feeling when working for a contest/bounty and a day job... This is a Good Thing (tm).

      --
      Actio personalis moritur cum persona. (Dead men don't sue)
    2. Re:This can work both ways by ggvaidya · · Score: 3, Insightful

      The way I see it, the money will just make sure that it gets on top of Slashdot :) and thus a lot of geeks, some with free time, will see it and go, "hey, that sounds interesting - and there's even something in it for me if I do it right!"

      People who wouldn't have otherwise thought of trying to clean up Gnome will give it a shot. Go, Novell!

    3. Re:This can work both ways by Doc+Ruby · · Score: 4, Interesting

      There's no reason why a team of people couldn't work together daily, in a traditional "day job", to produce software to submit to these bounties. In fact, given that the risk of the code not making into acceptance by deadline is now borne by the coders, a team that's working on several bounties at once (perhaps in different projects) a better way to spread the risk. This model lets a team work on what they want, when they want, for whom they want, with whom they want. Without all the baggage that's bundled with a day job at the buyer of the code, including the mixed bag of projects assigned to team members.

      --

      --
      make install -not war

    4. Re:This can work both ways by witcomb · · Score: 1

      Two cents? No wonder you don't see it as an incentive you have to give more than that.

    5. Re:This can work both ways by Anonymous Coward · · Score: 0

      yes, actually there have been well controled psycological studies confirming this observation. Basically, if you don't mention money, people perform task beter than if you do mention money. But, once money is offered, more money does make people work harder. And finaly, people don't seem to realize that paying some one nothing at all is better than paying them insuficenltly. http://www.hrpost.com/lib/comp_can/rust.html

    6. Re:This can work both ways by Rahga · · Score: 4, Interesting

      Here's a reason: Most people with the experience needed to do this work easily make well over the ammount these bounties offer (~$200 for something that is very non-trivial) in less than a day or two at their day job. The bounties are simply added incentive to fix messy problems, very rarely will you see somebody take them on unless they already wanted to scratch that itch.

    7. Re:This can work both ways by Doc+Ruby · · Score: 1

      I agree. The bounties are too low for the sole motivation of a good programmer. Opening the market like this could produce an efficiency in code reuse that we'd all welcome - programmers "doing it already" (for some other payment) would be incented to send it to the distributor which can send it to more consumers, justifying their investments in the bounties. Or it could send the programming work to either worse programmers, resulting in worse code, or to poorer programmers, deflating the cost of coding - at least temporarily, while the supply/demand curve changes. The real governing question, that can't be answered by economics, is whether the project communications (design/management) are effective with this casual/remote a relationship between the specifier and the coder.

      --

      --
      make install -not war

    8. Re:This can work both ways by ergo98 · · Score: 1

      Money is sometimes a very good incentive, but sometimes things you work for money don't seem as much fun.

      When monetary rewards are offered in these sorts of events, it's often the sense of competition rather than the actual purse that draws people in. e.g. You want to win basically because you believe that other people are really motivated by the money, so a win would be that much more legitimate. Of course most of them are playing out the same logic in their heads. Look at the xprize as a good example - for most of the projects the actual win money was a token amount, and a couple of the projects were funded by very deep pockets, yet it created a fierce tournament.

      This is the reason why many people get such enjoyment out of card games or bets where small stakes are up for grabs. Real money, even a token amount, seemingly makes it more "real" of a contest.

    9. Re:This can work both ways by Anonymous Coward · · Score: 0

      Yes, studies have shown this very effect. I can't remember the source, but if you give children a certain amount of free-play time where they can choose any activity, a certain percentage will choose coloring. If you then start paying the children to color, lots of them will color for money. But then when you stop paying them, almost none of them will continue coloring, including the ones who used to like doing it.

      I doubt we'll see that effect with Gnome though, since the amounts are so trivial that no one will actually be doing it for the money.

    10. Re:This can work both ways by MoogMan · · Score: 1

      Well, with a lot of work, you don't have a choice what you are coding. You code what you are given, and you get paid. This, on the other hand, is different. You choose what you want to code and get paid for it. Or you can leave it.

      But you are kindof right - money is not a motivational factor in business terms.

    11. Re:This can work both ways by JohnnyBigodes · · Score: 1

      I think when doing something, most "geeks" (term used loosely) either charge whatever their time is worth (lots, usually) or simply don't charge at all, meaning they do it for the fun of it.

    12. Re:This can work both ways by Curtman · · Score: 1

      I think these bounty type ideas could work very well in a university setting, where teams would register with Novell or whoever, and compete against teams from other schools for prizes. If the schools were to receive the money, and the students involved would get a small break on tuition or something, this would be a great way to bring new/fresh developers into the community, and the schools would do most of the work of getting people involved. Also it would be a great way for Novell, RedHat, and others to spot new talent, and for students to have their talents recognized.

      Obviously it would be very difficult to come up with a fair system to score points, but I think the model would work much better than offering bounties to people who are already familiar with open source. Perhaps a panel of judges could be assembled with representatives from the major distro's, and larger companies who are using Linux on the desktop.

      Could something like this work?

    13. Re:This can work both ways by Anonymous Coward · · Score: 0

      You are assuming that the programmers involved are based in the first world; $100 is a significant amount of money in the developing world.

      I can see this encouraging, for example, Indian hackers to work on the Gnome project.

      CO

  5. Re:cat Gnome /dev/null by Anonymous Coward · · Score: 0

    That should be "cat Gnome > /dev/null"

  6. Re:cat Gnome /dev/null by shamilton · · Score: 0, Troll

    Unix for Dummies, Second Edition.

    --
    "[A] high IQ is like a Jeep; you will still get stuck, just farther from help!" --Just d' FAQs, c.g.a
  7. Eye Candy by Nino · · Score: 1, Interesting

    Take out all the GUI eye candy and that will speed up about 50% on older systems.

    1. Re:Eye Candy by thryllkill · · Score: 1

      Which gnome do you use? I use 2.8 and it is a pretty basic desktop setup, no real eye candy. Unless you consider transparent terminal windows damn sexy.

      --

      Note to self: No more arguing with the faithful.

    2. Re:Eye Candy by PoprocksCk · · Score: 2, Interesting

      Yeah I agree. I would certainly not call GNOME as a whole bloated these days. Since 2.6 or so they've begun to clean things up quite a bit, especially with Nautilus. It's actually usable now...

      And as for the people complaining about memory usage... if you're running "top" with 512 MB of RAM and go "omg, 431520k used! It's GNOME's fault!" -- well then I don't know what to say to you. That is simply how Linux allocates its memory -- it uses almost all of it at any given time and distributes it between applications.

    3. Re:Eye Candy by Tribbin · · Score: 1

      You are right about the upper part. But, did he say anything about memory usage?

      --
      If you mod this up, your slashdot background will turn into a beautiful sunset!
    4. Re:Eye Candy by Aldric · · Score: 1

      Huh... I'm running SuSE 9.2 with KDE 3.4 RC1 and it's only using 209MB of memory out of 512MB at the moment. It can't just be "that's the way Linux is".

    5. Re:Eye Candy by Mr+Z · · Score: 1

      It all depends on how you interpret the output of the various tools. For instance, if you run 'free', you'll get something that looks like this:

      . . . . . . .total. . . .used. . . .free. . .shared. . buffers. . .cached
      Mem:. . . . 255236. . .246452. . . .8784. . . . . 0. . . .8028. . . 66036
      -/+ buffers/cache:. . .172388. . . 82848
      Swap:. . . .999896. . .107880. . .892016

      If you look closely, 246MB of my 256MB is "used," but of that, 74MB are disk buffers. Only 172MB are used by applications at the moment.

      So, by one measure, all but 8MB are in use, and by another measure, all but 82MB are in use.

      --Joe
  8. Its about time by laffer1 · · Score: 5, Insightful

    This is great news. I switched from KDE about a year ago because of the newer gnome interface. (2.4+?) I run gnome on FreeBSD 5-stable and found that my biggest complaint is the memory usage. I have a dual xeon 2.0 gig with 1 gig of ram and gnome + xorg eat up at least 200-300mb of the ram. Maybe while they are at it they can fix some other problems with gnome like the fact the default stack size needs to be increased in many non linux systems when porting it!!!!!

    1. Re:Its about time by Anonymous Coward · · Score: 0

      Why is open source software always so memory-hungry?

      I just had a look at what's using memory on my Windows box. Windows itself is using about 40-50 mb, but that's for everything - kernel, GUI, services (the Windows equivalent of daemons), and so on. Of the rest of what's running, Firefox is using 50 mb... no, 51 mb... no, 52 mb... oh, that's just that memory leak they haven't got round to fixing yet. Thunderbird is doing better, it's only using 22 mb to sit idle in the taskbar and check a couple of POP3 accounts every hour.

      Okay, so it's not just OSS. My closed-source text editor is taking up 12 mb. And it's only got a little 12kloc project open in it.

    2. Re:Its about time by Espectr0 · · Score: 5, Informative

      Kde has improved dramatically in speed , memory reduction and html rendering in konqueror in the last year.

      You may want to give it back a try.

      We use kde in our offices, which are pentium 2, 400mhz and as little as 128mb (!) of ram.

      On my development box, i have a dual 400mhz P2 with 320mb in ram, and i can run eclipse with tomcat

    3. Re:Its about time by MPHellwig · · Score: 1

      Windows itself 40-50 MB? That is only possible if you got 64 MB ram and windows 95/98, otherwise it will be much more.
      Typical windows will at least eat half of your ram regardless if you got 265MB or 4 GB.

    4. Re:Its about time by Earered · · Score: 3, Informative

      I was able to use gnome 2.8 on a Celeron 433 with 64Mo of RAM. Though you either need to tweak your configurationhttp://www.gnome.org/learn/admin-guid e/2.6/ch09.html/
      or to use a dedicated distribution like Beatrix http://www.watsky.net//
      which include gnome and use dirty trick with the kernel to improve performance.

    5. Re:Its about time by Anonymous Coward · · Score: 0

      That's a lie.

      Windows XP uses 75-200MB of memory (commit charge) with one user logged in and nothing running but system tray programs and services, regardless if you have 256MB or 2GB of RAM installed. This depends on what software you have installed, what starts up when you log in, and what services you have running. On school computers (which have web design and programming related software installed, along with their anti-virus and "security"/"spy" software, Windows XP takes 160mb after I've logged in.) On a default install on a system with a lot of hardware connected (wireless, printers, TV-capable video card), memory usage was close to 120MB after installing.

      Linux will use very close to all the memory in a system, even if the programs you're running aren't anywhere near however much you're using. It uses this memory for caching.

    6. Re:Its about time by Mike+McTernan · · Score: 3, Insightful

      Why is open source software always so memory-hungry?

      I really don't know the answer, but would expect that is is partly due to different apps and code blocks being written by lots of different people in some amount of isolation. This could lead to a limited view of the project/distribution and as such the various inefficencies in the system may get missed.

      --
      -- Mike
    7. Re:Its about time by PsychoSid · · Score: 0, Offtopic

      Hooray for Apple !

    8. Re:Its about time by MPHellwig · · Score: 1

      Indeed your right, my fault was that half of the memory is reserved for windows (the OS) and the rest can be used for applications but that doesn't need to be allocated.

    9. Re:Its about time by XO · · Score: 3, Insightful

      Everyone's tried to make use of the bazillions of different libraries available, that have all become extremely bloated over time, so that we're to the point where as is explained in one of the linked articles, "Yes, we are loading 300 kb of data from an xml file at bootup time to control the volume of the computer", and other wonderful things. Also the developers computers tend to have a lot more resources available perhaps than do many of the people who are just users.

      I had been reporting memory leak problems with gaim since like v0.8something, and was repeatedly told along the lines of "i dont have any problems, and there haven't been any memory leaks found in several versions", and was summarily dismissed. Surely enough, in a recent versions changelog, "* large memory leaks plugged" or some such. Until the problem bites the authors of the project, no one cares.

      Also, the absolute insane complexity of many of the things (layer upon layer upon layer upon layer upon layer of abstraction for no good reason at all except to have a high-level interface to a high level interface to a high level interface to a medium level interface to a low level interface)

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    10. Re:Its about time by roystgnr · · Score: 5, Informative

      It uses a proprietary widget toolkit

      Qt is dual licensed under the GPL. It's no longer any more proprietary than gcc.

    11. Re:Its about time by m50d · · Score: 2, Interesting

      I run kde successfully in 62mb of ram

      --
      I am trolling
    12. Re:Its about time by Anonymous Coward · · Score: 0

      You've gotta get some facts to back up your arguements, son. I can make up numbers all day too.. My linux box uses 18MB of RAM, and that's with both KDE and Gnome runnnig, 4 different media players playing 4 different movies and songs... and all the services possible in the linux world, and even some windows ones run through wine, just to be truely leet.

      fucking clown shoe.

    13. Re:Its about time by Yokaze · · Score: 1

      You say gnome+xorg: Is that the number from top or ps, which includes the memory from mmapped I/O devices, like, say, a 128Mb graphics card?

      --
      "Between strong and weak, between rich and poor [...], it is freedom which oppresses and the law which sets free"
    14. Re:Its about time by Yokaze · · Score: 1

      Or Gnome for that matter.

      --
      "Between strong and weak, between rich and poor [...], it is freedom which oppresses and the law which sets free"
    15. Re:Its about time by abigor · · Score: 2, Interesting

      It's not proprietary. Get your facts straight, please.

      Also, KDE 4 will be very interesting: it's undergoing a complete HIG review, and there will be a lot of deep changes. Luckily, the features and solid architecture are already there for the new interface to take advantage of - unlike Gnome.

    16. Re:Its about time by iamwahoo2 · · Score: 1

      Qt is GPL. That is all that matters. It is every bit as free as GTK or Gnome.

    17. Re:Its about time by einhverfr · · Score: 1

      First, you are correct in saying that it is not necessarily an open source issue. For example, many of the really mature OSS applications use very little memory. Look at OSS server software, for example.

      But....

      If the question is re-phrased to "Why is the *nix desktop so memory-intensive?" the answer should be clear. The UNIX desktop is designed around a modular windowing system which favors flexibility over performance. As you start expanding this idea into a full desktop, you get a large number of pieces which offer different function. This is by necessity a memory-intensive approach. Add all that eye-candy and it takes up even more.

      But look at what this flexibility buys you: So you have that new system with 1GB RAM and a few really old 80486's? You can install really old distros on those old 80486's and use them as thin clients to the new system. You can access the same apps anywhere, even on computer systems that cannot run them at all.

      Also lets look at another issue too. Applications like Mozilla got very bloated as they became featureful and then were slowly reduced in size so that they would run better on older systems. The same is happening on GNOME. So does GNOME need to be optimized? yes. But it will happen.

      --

      LedgerSMB: Open source Accounting/ERP
    18. Re:Its about time by jwitch · · Score: 1

      i'm interested in knowing where you obtained a 62mb chip of ram from?

    19. Re:Its about time by Knnniggit · · Score: 3, Funny

      Easy. Just buy a 64MB chip and break it in half like a graham cracker.

      --
      Brain kills internet cells.
    20. Re:Its about time by Anonymous Coward · · Score: 0

      Yes, my 33MHz 386 box with 4MB of memory and a 250MB disk runs both Gnome and KDE at the same time without any problem. Please.

    21. Re:Its about time by mormota · · Score: 1

      Maybe it was a 64 MB module, but the videocard allocated two megabytes?!?

    22. Re:Its about time by drsquare · · Score: 2, Insightful

      I'm not so sure about that, I have 512MB of RAM, Athlon 2000, and it takes 10 seconds at least for KDE to start up. This just for a very small part of the OS which doesn't really do an awful lot other than put borders and titlebars on Windows.

      As for Konqueror, well I think Firefox has taken the open-source browser crown. Saying that, I use Konqueror for browsing images on the local filesystem. As a general file-manager it's not really up to it, and it's not really up to it as an Internet browser. I think the misguided idea to merge the Internet and file-manager was a bad one. You don't see people trying to merge word processors and e-mail programs.

    23. Re:Its about time by Anonymous Coward · · Score: 0

      "Every bit as free?" Hardly... using the GPL for a library like Qt means that any KDE apps that are not GPL are subject to the TrollTech tax of a few thousands dollars PER DEVELOPER PER YEAR. GNOME's libraries are LGPL -- and you may use whatever license you like for your own GNOME software.

      This doesn't even get into the legal minefield of TrollTech's triple licensing nightmare -- and the fact that SCO and Canopy (infamous companies for any Linux users) are part owners and sit on the board of directors at TrollTech. No thanks... "just as free" is bullshit.

    24. Re:Its about time by Bert64 · · Score: 1

      It could if you ran the software from NFS and used your 250mb disk entirely for swap, ofcourse it would be horrendously slow.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    25. Re:Its about time by Anonymous Coward · · Score: 0

      > You don't see people trying to merge word processors and e-mail programs

      "Use Microsoft Word to edit email messages" is pretty popular option at work...

    26. Re:Its about time by Anonymous Coward · · Score: 0

      Everyone's tried to make use of the bazillions of different libraries available, that have all become extremely bloated over time, so that we're to the point where as is explained in one of the linked articles, "Yes, we are loading 300 kb of data from an xml file at bootup time to control the volume of the computer", and other wonderful things. Also the developers computers tend to have a lot more resources available perhaps than do many of the people who are just users.

      Oh well done moron. You know how to misquote a GNOME developer's blog. What the fuck does this have to do with "bazillions of different libraries" -- and why is lots of smaller libraries "bloated", as opposed to sticking all the code in one or two big blob-o-code libraries (like KDE).

    27. Re:Its about time by strider44 · · Score: 1

      "Why is a linux box so memory intensive?" apt-get install * That's my problem.

    28. Re:Its about time by Anonymous Coward · · Score: 0

      People who work on OSS tend to have top of the line computers. Gnome was always especialy bad for this... I remember back in 2000 I couldn't use the latest version of sawfish because the configuration dialog required at least 1152x864.

      I'm sure a lot of theme designers would be shocked if they saw the percentage of users who only have 17" monitors.

      If all the programmers have a look and decide "It works for me" there's no incentive to optimise performance.

    29. Re:Its about time by Eil · · Score: 2, Interesting


      I can vouch for this, the KDE desktop and all of its apps are nice and snappy on my aging Athlon 750. To put this in perspective, Firefox--a widely acclaimed "small footprint" browser--feels like bloatware in comparison. I use it over Konqueror only because I can use the Adblock and Googlebar plugins with it.

    30. Re:Its about time by XO · · Score: 1

      Because it was something almost completely unrelated to the ability to control volume that was causing the 300kb of XML to be loaded into memory.

      The initial part of that though is commenting about the tons of intermingled libraries that don't ahve a damn THING to do with whatever is going on - it's like Dependency Hell, or DLL Hell, but for the code dependencies.

      The second part was supposed to be somewhat more seperated from the first part.

      But , basically, it comes down to this:

      I want to use function C from library A just because it has it! Oh, that causes the entire library A to be loaded initialised, load all of the things it needs, so on so forth, when all I really want is a function to *insert some relatively easy task here*, but instead, I just triggered the demand loading of 22MB of code and 48MB of data by asking for something from library A! yay!

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    31. Re:Its about time by Pseudonym · · Score: 2, Funny

      I run it in 640kb which, after all, should be enough for anybody.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    32. Re:Its about time by Poeir · · Score: 1

      There's a configuration option to control the volume of your computer? Sweet! Now I can take my desktop anywhere.

      --
      Sigs are like bumper stickers.
    33. Re:Its about time by Anonymous Coward · · Score: 0

      There's always one of you people around, trying to prove they can fit their penis, sorry, software into a smaller space than everyone else.

    34. Re:Its about time by drsquare · · Score: 1

      That's not really what I'm on about, one program opening another to perform a particular function, like slrn or mutt opening up vim to edit a message. I mean Outlook and Word are still two different program.

      There isn't a file manager I'm personally satisfied with. All the different functionality seems to be spread out across different programs. Yeah I know, it's open source, I can do it myself. But I'm not a programmer, I don't have the knack, it doesn't come to me. And even if I were a programmer, file managers are just one thing I'm not satisfied with, there's all sorts of other things I don't like, hundreds, I can't dedicate my free time to fixing every single thing I don't like. Even just one would take years to perfect. Many projects have many many people working on them, and have done for years, and they're still flawed, what chance do I have?

    35. Re:Its about time by Anonymous Coward · · Score: 0

      Because it was something almost completely unrelated to the ability to control volume that was causing the 300kb of XML to be loaded into memory.

      You don't need to load 300Kb of XML... if yo udo it correctly, and you won't end up using 300Kb of cache memory if you use mmap -- the problem wasn't using XML or your bizarre claims about "unrelated things" (hello.... config data... duh!). It was a bug.

      The initial part of that though is commenting about the tons of intermingled libraries that don't ahve a damn THING to do with whatever is going on - it's like Dependency Hell, or DLL Hell, but for the code dependencies.

      No... it's nothing to do with a dependency hell. The dependencies in GNOME are well understood, documented and careful built that way to ensure the proper seperation of code -- which helps to ensure code reuse by other projects and a thriving development scene. Compare this with the unspeakable bloat and incompetence of KDE blob-o-code-let's-tie-everything-to-Qt approach -- which has only one attribute: it makes it easier for wannabe-l33t dickheads to compile it. It certainly doesn't make development easier.

      I want to use function C from library A just because it has it! Oh, that causes the entire library A to be loaded initialised, load all of the things it needs, so on so forth, when all I really want is a function to *insert some relatively easy task here*, but instead, I just triggered the demand loading of 22MB of code and 48MB of data by asking for something from library A! yay!

      Ah... the considered opinion of a fool who has never written a piece of software longer than 5 lines: Quote a pathological case of software development idiocy as if actually means something. You're one of those morons who thinks that 15 small libraries is bloat... whereas one huge-ass fucking library is somehow smaller because it's just one line in your compile script. God you're fucking stupid.

    36. Re:Its about time by Anonymous Coward · · Score: 0

      While that's true, it's effectively proprietary on any OS that isn't able to run the GPL version (everything but Linux and the BSDs, if I'm not mistaken). You can make GPL'd programs with Qt, certainly, but no one can use the code unless they're using one of the blessed OS's.

      While Qt is, technically, as legally unencumbered as GTK, it's far less free in practice.

    37. Re:Its about time by Bob+Uhl · · Score: 1
      You don't see people trying to merge word processors and e-mail programs.

      Well, actually you do...

      My big problem with KDE (now that the qt licensing issues have been resolved) is that it uses C++ rather than C.

    38. Re:Its about time by shellbeach · · Score: 2, Interesting

      There isn't a file manager I'm personally satisfied with.

      Have you had a look at ROX? It's small, fast, and has some nice shell integration (eg. you can navigate directories/files as you would in bash, with tab completion, etc; you can run shell commands in a minibuffer; a command to open a terminal at the directory you're browsing ...) - it even provides a desktop and will automatically mount and unmount devices, if that floats your boat (you don't need to have it enabled)

      Personally, I use IceWM for windowmanagement (it's fast, more themeable than *box variants and provides a nice taskbar) coupled with ROX. I noticed the other day that this combo is what VectorLinux provides as an alternative to KDE, so obviously I'm not the only one using the two.

    39. Re:Its about time by Mr+Z · · Score: 1

      Incidentally, that's how Sun used to do it with their dick^H^H^H^Hdiskless workstations. Everything would run via NFS, and if the working sets were too large, you might attach a small disk to hold swap, /tmp, and maybe a read-only copy of the OS.

      What's sad is I have actually NFS mounted a directory over a 14.4Kbps modem link, because I was running on a 386 with 4MB of RAM and no HD.

      I was writing SVGAlib hacks while at work at the computer hotline in college. We had network-booted machines w/ no HDs. I'd boot from a floppy, running a modified "rescue disk." I was telnet'd in one window (so I could run vi/gcc/etc. directly on the remote computer), and logged in locally in the other so I could run the resulting app...

      That would've been in, oh, 1994 or 1995. :-) And yes, it was damn slow, even though the executables I ran were relatively tiny. (I had SVGAlib and libc locally, so I was only bringing my tiny 10K or less a.out over the wire.)

      --Joe
    40. Re:Its about time by Mr+Z · · Score: 1

      Just remember, as volume decreases, temperature increases. If you decrease the volume too quickly (ie. non-adiabatically), the temperature will increase dramatically due to the increased entropy.

      --Joe
    41. Re:Its about time by Anonymous Coward · · Score: 0

      I Could run KDE 2.2.2 on a Celeron 500MHz with 60MB of RAM (4MB was alocated to the video card). It ran pretty decently actually, better than Windows ME on the same system.

      However, I'm not sure I'd like to try KDE 3.4 on such a system. Maybe with everything toned down, just about every service turned off, etc it would be okay...

    42. Re:Its about time by be-fan · · Score: 1

      I don't think you really understand what KDE does. KWin is the part that draws borders and titlebars on windows. It also consists of an entire application framework to make writing applications easier to write. KDE is an enormous amount of code, implementing a lot of functionality.

      --
      A deep unwavering belief is a sure sign you're missing something...
    43. Re:Its about time by iamwahoo2 · · Score: 1

      Trolltech has spoken out openly against SCO/Canopy and have regretted that SCO sits on their board. However, there is not a lot that they can do about that. Trolltech makes great software and releasing it as GPL helps to ensure the growth of "free" software more than something that is LGPL by forcing derived works to also be GPL. The name "lesser" GPL is used by gnu.org to convey the meaning that "It does less to protect the users freedom" (from their website).

    44. Re:Its about time by swillden · · Score: 1

      You can make GPL'd programs with Qt, certainly, but no one can use the code unless they're using one of the blessed OS's.

      Currently, Qt/X11, Qt/Mac and Qt/Embedded are all GPL'd. Only Qt/Windows is not under the GPL. They have, however, announced that when Qt version 4 is released (Q205), all versions of Qt will be under the GPL.

      So this FUD, too, shall pass. And I do think it qualifies as FUD, because while some GTK/GNOME programs do run well on Windows, it's hardly ever a decision-maker for people planning to write a cross-platform app. And it certainly has no real effect on someone's choice to use KDE.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    45. Re:Its about time by Anonymous Coward · · Score: 0

      Trolltech has spoken out openly against SCO/Canopy and have regretted that SCO sits on their board.

      And? I mean, they would say that... wouldn't they. It doesn't change the fact that behind the scenes at TrollTech you will find the smiling face of SCO and Canopy.

      GPL helps to ensure the growth of "free" software more than something that is LGPL by forcing derived works to also be GPL. The name "lesser" GPL is used by gnu.org to convey the meaning that "It does less to protect the users freedom" (from their website).

      Really? If TrollTech really believed in that, they wouldn't sell commercial licenses to allow companies to use whatever license they like, but they do do. You see, the FSF can make an argument like that... TrollTech cannot.

      Besides, if the KDE/Qt people *really* did believe that... then why will they not allow other GPLed libraries into KDE? Why aren't other KDE core libraries full GPL rather than LGPL? Of course we know why... it's because TrollTech is the only company allowed to charge license fees for commercial apps, and KDE is a loss-leader for them. It's got nothing to do with promoting freedom, it's about snaring developers into paying TrollTech's licensing fees/terms a giving SCO/Canopy control.

    46. Re:Its about time by m50d · · Score: 1

      It's like running in treacle, but it's doable, even without much stripping down (I left services and things at their defaults). Be prepared to wait a while for things to load, and make sure you don't try and use more than one app at once.

      --
      I am trolling
    47. Re:Its about time by Anonymous Coward · · Score: 0

      Now the truth comes out. For me, and probably many others, "running successfully" and "running in treacle" aren't even remotely the same thing. If you have to wait for apps all the time, and can't run more than one, then it's nowhere near "successful".

    48. Re:Its about time by m50d · · Score: 1

      It is for what I'm using it for. I only need one app at a time (and more do run, especially if they're small, it's just other people tend not to like the performance), and can leave it for a few mins if it's churning.

      --
      I am trolling
  9. Re:cat Gnome /dev/null by Anonymous Coward · · Score: 0

    Isn't that the Gnome2.x manual?

  10. This is a realy good idea by Masq666 · · Score: 2, Insightful

    This is a realy good idea, something like this should be done not only to GNOME but also to other window managers such as KDE. Even non linux based systems could need some work when it comes to memory leakage and optimization. This does'nt only help people with little RAM but helps everyone.. Hope everyone are willing to help.

    --
    Bits of News Giving you the latest bits.
    1. Re:This is a realy good idea by Dan+Ost · · Score: 4, Informative

      Please don't call KDE a window manager.
      Both KDE and Gnome use window managers, but neither of them are window managers
      (the fact that you can change which window manager is used by KDE and Gnome
      is a good indication that they, themselves, are not window managers).

      xwinman.org gives an excellent introduction to both window managers and
      desktop environments. Give it a look.

      --

      *sigh* back to work...
    2. Re:This is a realy good idea by Masq666 · · Score: 1

      Thanks for pointing this out for me, i'll take a look at xwinman.org. But my point was that not only GNOME needs optimizations, not trying to flame here but i think it's to little focus on optimization in the software industy now a days(Commercal and Open Source). Hardware is cheap, but in some parts of the world they still use old computers.

      --
      Bits of News Giving you the latest bits.
    3. Re:This is a realy good idea by evanbd · · Score: 1
      xwinman.org gives an excellent introduction to both window managers and desktop environments. Give it a look.

      FYI, anything that is talking about the recent release of KDE 2.0 is just a tad dated. The concept is neat, but somehow I doubt the site is at all maintained.

    4. Re:This is a realy good idea by Anonymous Coward · · Score: 0

      KDE 2 was the same as KDE 3 in this aspect, so I don't see how that changes anything.

    5. Re:This is a realy good idea by ScrewMaster · · Score: 1

      It's not not just older computers. One of the reasons to switch away from Windows to Linux or BSD or some other more stable alternative is to run multiple applications reliably. I mean, Windows multitasks but not particularly well. You may have a fast machine with plenty of memory, but multitask a few major applications and that 1 Gb of RAM doesn't look so big anymore. Memory and resource efficiency is always a worthy goal but it takes time and effort to achieve, and for commercial software getting to market quickly is a bigger priority. On the other hand, since the open source world is generally less driven by market concerns and more by the needs of the development process itself there is less excuse for inefficient, bloated code. The folks and KDE and Gnome are certainly cognizant of this, and hopefully they will devote some resources to optimization. It's not particularly glamorous work, from a developer's standpoint (about as much fun as auditing code for possible security flaws) but ultimately results in substantially better products. I can't tell you how many times I've done the fine-toothed-comb routine on code and found easy ways to speed things up, or just realized that there was a better way to do it.

      The Windows world has, unfortunately, trained us to see system resources as effectively infinite. Hey, system too slow? Swapping too much? Just buy a faster CPU or more RAM. No problem. Who cares if your code takes five times as much memory as a more efficient (but harder to write) algorithm would. It works, doesn't it? Microsoft has always marketed its software to users with the latest, greatest hardware and has never exhibited any qualms about adding "features" (desirable or otherwise) that require user to replace their equipment. The problem for the Open Source crowd, however, is that widespread adoption of alternative environments will be slowed or killed if those environments can't offer similar features, functions and, yes, resource-hungry eye candy. But there's always room for improvement.

      --
      The higher the technology, the sharper that two-edged sword.
    6. Re:This is a realy good idea by Bohemoth2 · · Score: 1

      It still doesn't explain the difference between an enviroment and a window manager. It just says an eviroment is sort of like a WM but with added functions. What does one do that the other doesnt?

      And what does X do? I doubt that it can tranfer the screen image pixel by pixel. So it must be incharge
      of graphial elements too right?

  11. Next Bounties by buckhead_buddy · · Score: 4, Funny

    And the next set of bounties will be offered for cleaning up bugs introduced by rapidly encouraging people motivated only by money to make changes to Gnome without fully considering the ramifications of these memory reductions. :-)

    1. Re:Next Bounties by Rahga · · Score: 2, Insightful

      Well, those patches would no only have to pass scruitiny by those offering the bounties, but more importantly, the package maintainers as well. I'm not concerned.

  12. Feasable Career? by dingo · · Score: 5, Funny

    I wonder if there will ever be enough bounty's on offer to make a career out of it.

    I can just see all the coder bounty hunters with their boba fett helmets on.

    --
    The Borg assimilated my race & all I got was this lousy T-shirt
    1. Re:Feasable Career? by Anonymous Coward · · Score: 0

      If there were bounties on every fucktard that uses apostrophes to make a plural, I'd be rich.

    2. Re:Feasable Career? by Anonymous Coward · · Score: 0

      Imagine if there was bounties for people who made up words. I would be proactively shooting every fucktard in sight.

    3. Re:Feasable Career? by Anonymous Coward · · Score: 0

      Utterancely impossitard!

    4. Re:Feasable Career? by skraps · · Score: 3, Insightful
      I wonder if there will ever be enough bounty's on offer to make a career out of it.

      Not at $100 or $200 a pop, notta chance. I think these are mostly to encourage the existing gnome hackers to attack some less-than-glamorous problems they would rather not do normally. I doubt we'll ever see a wild wild west bounty hunter who just roams around between vastly different projects. If the improvements were that easy to make, someone already on the team would just make them instead of giving up money. If they aren't that easy, like these, then you wouldn't be able to solve enough of them to pay your rent.

      --
      Karma: -2147483648 (Mostly affected by integer overflow)
    5. Re:Feasable Career? by vkewstv · · Score: 1
      I wouldn't have enough money to live from those bounties even if I'd fix all these assigned bugs in a month.

      Cheap work power for Novell.

    6. Re:Feasable Career? by Anonymous Coward · · Score: 0

      Yeah, you'd have to shoot the grandparent for "feasable". I think it's a lot worse to massacre something as simple as a plural, than to make up words. Making up words is part of the language, but basic rules should be followed.

    7. Re:Feasable Career? by Anonymous Coward · · Score: 0

      No, you wouldn't. You would do nothing. You're just some pussy sitting at his computer whining about nothing. Might I suggest you do the world a favor and drink a bullet?

    8. Re:Feasable Career? by xenocide2 · · Score: 1

      Sure, there are guys who wander the wild west of California. They're called independent contractors.

      --
      I Browse at +4 Flamebait

      Open Source Sysadmin

    9. Re:Feasable Career? by drsquare · · Score: 1

      I don't know if anyone's willing to throw that much money at something that's supposed to be 'free', i.e. done for pleasure in your own time. And at $200 a time, you'd have to do like one a week to make a proper living out of it. Are there that many projects worthy of putting bounties on that could be completed by a single person in a week?

      But on the bright side, there'd be no income tax or anything, as you'd be effectively unemployed.

    10. Re:Feasable Career? by DarkTempes · · Score: 1

      errr, $200 would be exactly enough to pay my months rent...
      now food, that would still be a small problem.
      oh and the power and water bills.

    11. Re:Feasable Career? by skraps · · Score: 1

      Holy crap where do you live for $200/month?

      --
      Karma: -2147483648 (Mostly affected by integer overflow)
    12. Re:Feasable Career? by DarkTempes · · Score: 1

      in a decent apartment in good old baton rouge, louisiana; birthplace of serial killers and rapists

    13. Re:Feasable Career? by greenrd · · Score: 1
      But on the bright side, there'd be no income tax or anything, as you'd be effectively unemployed.

      No, you wouldn't. Bounties are still income for work done, so they'd still be taxable, as far as I can see.

      Unless you mean "you'd be earning so little you'd be effectively unemployed" - in which case, I agree with you - you might not make enough to start paying any income tax, depending on your jurisdiction.

    14. Re:Feasable Career? by drsquare · · Score: 1

      No, I mean that it would be cash in hand, i.e. you wouldn't have to declare any income.

  13. gnome-terminal by karmaflux · · Score: 4, Informative

    Gnome-terminal is going to make someone ridiculously wealthy. Seriously, there's so much room for optimization that a good coder will be able to retire off that one program.

    --

    REM Old programmers don't die. They just GOSUB without RETURN.

    1. Re:gnome-terminal by schleyfox · · Score: 2, Interesting

      aterm is GPL, right? excellent

      1. Rip out gnome-terminal and piss on it
      2, slide xterm or aterm into its place
      3. Profit?

    2. Re:gnome-terminal by b374 · · Score: 2, Interesting
      From TFA:
      Aivars Kalvans has submitted two great patches on bugzilla. One of them cuts 250 kb of malloc'ing for each tab you open in gnome-terminal. This will save me at least 5 MB on my desktop. It is still pretty messy (it was 500 kb per tab before his patch), and much worse than konsole (which takes 50 kb per tab).
    3. Re:gnome-terminal by Anonymous Coward · · Score: 0

      I'm assuming that you won't reply to this, but do you have any documented examples of bad coding practices in KDE? I'm just curious to actually see an example of it...I've waded through bits and pieces of the code for it at one time or another, but a pointer to some known section would be helpful.

    4. Re:gnome-terminal by serviscope_minor · · Score: 1

      Gnome-terminal is going to make someone ridiculously wealthy. Seriously, there's so much room for optimization that a good coder will be able to retire off that one program.

      I call bullshit. I've benchmarked a few terminals, since sometimes my programs spew out tons of crap. Gnome terminal won in terms of speed (as long as you don't use antialiased fonts). rxvt was not far behind. XTerm was pitiful, especially if you have a large scollback buffer. KTerm was far behing xterm, unless XTerm has a large buffer, since it seems to slow down linearly with buffer size.

      To my real suprise gnome-terminal won.

      --
      SJW n. One who posts facts.
    5. Re:gnome-terminal by Anonymous Coward · · Score: 0

      > Gnome terminal won in terms of speed
      > To my real suprise gnome-terminal won.

      Now look at the memory usage, there's no excuse for it!

    6. Re:gnome-terminal by Anonymous Coward · · Score: 0

      Konsole is a better desktop terminal than [aex]term, we need a lightweight, tabbed terminal emulator for GTK based DE's. Gnome terminal is a pig.

    7. Re:gnome-terminal by Anonymous Coward · · Score: 0

      Gnometerminal opens only one process no matter how many terminals you have open, of course that process uses much memory.But open up 16 eterms and it will also take alot of memory.

    8. Re:gnome-terminal by dhfoo · · Score: 1

      Go to edit->keyboard shortcuts and tick the "disable menu shortcut key" box. Where's my bounty? Cheers

    9. Re:gnome-terminal by Deagol · · Score: 1

      Screw the tabs. Give me a lean term window and I'll run screen for my multi-term needs. Tabs, what a lame idea for a terminal program.

    10. Re:gnome-terminal by martinde · · Score: 1

      > KTerm was far behing xterm, unless XTerm has a large buffer, since it seems to slow down linearly with buffer size.

      If by "KTerm" you mean Konsole, I will say that it was only recently that I could switch to Konsole - probably KDE 3.2.x because it used to be too slow. It's now indistinguishable compared to xterm in my opinion. Mapping multiple sessions to ALT-F1-F6 like the linux console inside of konsole makes it more functional than xterm... I've switched for good.

      (Although for remote sessions I've still be using xterm. Any good tips for remote konsoles, anyone?)

    11. Re:gnome-terminal by Anonymous Coward · · Score: 0

      Gnome-terminal's problem lies in the unmaintained "vte", which has recently been patched for Gnome 2.10. Unfortunately, speeding it up, and "cheating" to only render changes (like many terminals do) causes some rendering problems on some machines.

    12. Re:gnome-terminal by drinkypoo · · Score: 1

      I vehemently disagree, especially if it would integrate with screen. Typing ^aa to go to the beginning of a line all the time is tiresome.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    13. Re:gnome-terminal by Anonymous Coward · · Score: 0

      Sorry mate, I'm out.

      Settle for a Mars?

    14. Re:gnome-terminal by Anonymous Coward · · Score: 0

      It's "feasible", you moron.

    15. Re:gnome-terminal by _Sprocket_ · · Score: 1

      I'm not so sure. I use both Konsole and Screen regularly. Though, to tell you the truth... I'm not entirely sure why. And if I had to give up one or the other, it would definately be the tabs. But having said all that... if Screen fit all situations, one would think I'd be using only Screen.

    16. Re:gnome-terminal by pjrc · · Score: 1
      I've benchmarked a few terminals, .... Gnome terminal won in terms of speed

      Obviously, your benchmarks aren't anything like the tests in this thread, where rxvt-unicode is MANY times faster than gnome terminal.

    17. Re:gnome-terminal by Langley · · Score: 1

      Ever thought of remapping your screen escape key-sequence?

      Try this in your .screenrc:
      escape ^\\\

      Now Ctrl-\ can be used to invoke screen commands, and Ctrl-a works like it used to.

    18. Re:gnome-terminal by Abcd1234 · · Score: 1

      Indeed. In fact, in my experience, good ol' xterm is *vastly* quicker than gnome-terminal. Simple test: take a gnome-terminal, make it quite large (130x50 will do), then load up a text file in less, go to the end, and start scrolling backward, and watch gnome-terminal choke.

    19. Re:gnome-terminal by Storlek · · Score: 1

      Now Ctrl-\ can be used to invoke screen commands ... and when you forget you're not running screen, you hit ^\ c to open a new screen and inadvertently cause whatever you're doing to dump core. Ctrl-] might be a better choice, since it's not mapped to "scream and die" by default.

      --
      Bears don't normally eat things that talk and move backwards.
    20. Re:gnome-terminal by Anonymous Coward · · Score: 0

      That's how I felt until I had used tabs for a couple of weeks.

      Now I have to keep KDE around just for konsole...if I weren't hooked on tabs, I'd probably just use xterm on xfce.

    21. Re:gnome-terminal by cerberusss · · Score: 1

      Why not run XFCE and use Konsole or Gnome-Terminal? You don't need the whole desktop environment for those programs.

      --
      8 of 13 people found this answer helpful. Did you?
    22. Re:gnome-terminal by Anonymous Coward · · Score: 0

      #define return0 return 0

  14. Old hardware with new Linux by Anonymous Coward · · Score: 1, Interesting

    What is your experience with new Linux on old hardware? I now believe that older Linux versions should be used; or, one of the light distros.

    On a dual boot P233 with 64MB of RAM:
    Win XP feels less sluggish than 2.6 with gnome.
    The newer Linux stuff just requires more memory.

    1. Re:Old hardware with new Linux by Anonymous Coward · · Score: 0

      "Linux stuff"?

      Gnome is NOT LINUX!

      GNOME=GNU NETWORK OBJECT MODEL ENVIRONMENT.

      You are reffering to a part of the GNU Operating System, so please call it GNU, or GNU/Linux.

    2. Re:Old hardware with new Linux by Anonymous Coward · · Score: 0

      The parent is a Richard-bot. How novel.

    3. Re:Old hardware with new Linux by rsheridan6 · · Score: 1

      I installed Linux on a similar machine, my mom's ancient emachines piece of crap. Gnome runs, but it's just not suitable for use on an ancient box like that. Use xfce or icewm if you want something sort of windows-esque that's not so slow, or fluxbox is even faster if you're not afraid to try a non-windows-like window manager. But forget gnome or KDE unless you get a real computer.

      --
      Don't drop the soap, Tommy!
    4. Re:Old hardware with new Linux by Anonymous Coward · · Score: 0

      damn right. linux is a viral buzz word

    5. Re:Old hardware with new Linux by Anonymous Coward · · Score: 0

      GNU/linux on old hardware is rough. If you're thinking of upgrading from a dos based system like win98 forget it. My advice is don't even bother. I'm thinking about taking a look at FreeDOS.

    6. Re:Old hardware with new Linux by Mystic0 · · Score: 1

      ...that doesn't stop him from being accurate though.

    7. Re:Old hardware with new Linux by HermanAB · · Score: 1

      IceWM or BlackBox will get you going.

      --
      Oh well, what the hell...
    8. Re:Old hardware with new Linux by Anonymous Coward · · Score: 0

      A major part of the world's people do not have access to "real computers" like monied elites in your class. What's to be gained by dissing these folk. A thought, why don't you spring for the newer, less ancient macines they should have!

    9. Re:Old hardware with new Linux by cynyr · · Score: 1

      my install on my P100 with 192MB ram feels just fine, just to clarify i usually only have 2-4MB free and i'm running mysql, apache, nfs, smbd, ssd and a few other things.... i also do not have X installed :-) probably why it feels fine :-D

      --
      All of the above was encrypted with a Quad ROT-13 method. Unauthorized decryption is in violation of the DMCA.
  15. Novell... by cs02rm0 · · Score: 1

    ...seem to be doing great stuff for the Gnome community and Linux in general more and more.

    I know they have a vested interest but this is great stuff.

  16. bloat in gnome... by mickyflynn · · Score: 3, Funny

    'cause a bloated gnome is just a hobbit... which is actually cooler.

  17. Fine, give them money, but... by TapioNuut · · Score: 4, Insightful

    Offering money is a great way of getting people interested in many things, but do the people who are capable of creating valuable bug reports and/or patches really need these bounties?

    I wonder how many crappy bug reports and patches are to be submitted because of the "easy" money being given. I do believe that the bounties will go to the right people and for the right reasons, but more the crap, the more it takes work to find the gems.

    Nevertheless, it's about time to unbloat Gnome.

    --
    Tapio 'itn' Nuutinen
    1. Re:Fine, give them money, but... by thenextpresident · · Score: 2, Insightful

      Except you don't get the money just for coming up with something. It has to be selected, which means other people have to approve it. Which means it has to be good.

      "I wonder how many crappy bug reports and patches are to be submitted because of the "easy" money being given."

      0. Just because you submit a bug report doesn't mean it becomes a bounty.

      --
      Jason Lotito
    2. Re:Fine, give them money, but... by rbarreira · · Score: 1

      I think the grandparent meant just this - because of the money prize, there can be a flood of people who submit crappy bug reports and patches, in order to try their luck.

      This would obviously be bad, if it happened. I don't think it will be that much of a problem, though :)

      --

      The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
  18. I love this by a_greer2005 · · Score: 0, Flamebait

    Things like this make me love OSS, an effort to vut bloat? when was the last time a closed-source software outfit (Microsoft I am looking at you) acctually tried to make the packege MORE efficiant? the simple answer is Never that I can remember.

    1. Re:I love this by salimma · · Score: 1

      Apple does make OS X go faster at every release between 10.0 and 10.3 (and 10.4 should follow in the same path, minus the overhead of indexing files for Spotlight, but plus the performance benefit of CoreImage shifting a lot of graphical effects to the graphics card when supported).

      Yes, Darwin the base OS is open-source, but a lot of the improvements are in the layers they build on top of that.

      --
      Michel
      Fedora Project Contribut
    2. Re:I love this by youngerpants · · Score: 1

      I can remember a very recent one, W2K3 server; by cutting out the eye-candy and switching services off by default W2K3 server runs on significantly less resource than XP.

      I admit, not enough so that I would actually want to run windows as a server, but Microsofts strength is in usability, and that means a GUI, which means resource hogging

    3. Re:I love this by NineNine · · Score: 1

      when was the last time a closed-source software outfit (Microsoft I am looking at you) acctually tried to make the packege MORE efficiant?

      Never. Bloat is something that you work to avoid when you're still designing and archtecting the software. Chopping off sections of code after the fact only helps minimally. I think the whole project is terribly flawed, and will always be as slow as molasses (which is why I won't use it).

    4. Re:I love this by Anonymous Coward · · Score: 0

      Yes, but does the fact that every OS X release gets faster tell you that

      (a) Apple are amazing! They can make things go faster by waving the magic iWand of Jobs!

      or

      (b) The early versions of OS X were really rather crappy, but the Apple fanboys were unable to comprehend such a concept and squandered money on it anyway?

    5. Re:I love this by Anonymous Coward · · Score: 0
      Bloat is something that you work to avoid when you're still designing and archtecting the software.

      Did write the windows user, adding;

      I think the whole project is terribly flawed, and will always be as slow as molasses (which is why I won't use it).

      **cough** **cough**

    6. Re:I love this by EdMack · · Score: 2, Insightful

      So, why does XP load so quickly? By accident?

      Nope. it's because a lot of people put hard work into it.

      --
      puts ("Python r0cks\n");
    7. Re:I love this by Directrix1 · · Score: 1

      Exactly why do you think it is flawed?

      --
      Occam's razor is the blind faith in the natural selection of least resistance and in universal oversimplification. -- EF
    8. Re:I love this by Anonymous Coward · · Score: 0

      XP...load...quickly?

      Creepy man from alternate universe needs to leave.

    9. Re:I love this by Anonymous Coward · · Score: 0

      Horsefeathers.

      We've all heard the phrase "Make it work, make it fast". With the speed of new features and typical development attention spans, most of OSS is focused on "make it work".

      Only when things become annoying do we start on the "make it fast". But the focus is always on "make it work". If it's too big for a small system, then it "doesn't work".

      During project lifecycles, there are many times when a section of code is redone to make it more efficient, even years after it was first designed. If it was reasonably modular in the beginning, changing it out with a more efficient module shouldn't have a dramatic affect on teh codebase as a whole.

    10. Re:I love this by DashEvil · · Score: 1

      For what XP is, it does boot rather quickly.

      --
      -If God wanted people to be better than me, he would have made them that way.
    11. Re:I love this by NineNine · · Score: 1

      Exactly why do you think it is flawed?

      Because in order to get any kind of usable performance, you need a high-end pentium, especially when comparing in W2K.

    12. Re:I love this by Anonymous Coward · · Score: 0

      Well, because you see, Windows keeps booting after you login. It only boots some 35% of the system or so, until the login window -- just enough to actually display the login prompt. That is why it seems so fast.

      When you login, just notice how your disk will spin like crazy for another minute or so, as all the crap gets loaded and appears on your tray.

    13. Re:I love this by Directrix1 · · Score: 1

      I have a AMD T-Bird 1.2GHz, which I wouldn't call high end by any means, and it runs fine. It does like the RAM though. I found performance to be roughly comparable to when I was running W2k on this same machine.

      --
      Occam's razor is the blind faith in the natural selection of least resistance and in universal oversimplification. -- EF
    14. Re:I love this by eraserewind · · Score: 1

      "Seems fast" is all people want for a desktop environment. It can still be "actually slow", so long as it uses some psychological trick to "seem fast".

    15. Re:I love this by Aldric · · Score: 1

      It is fast. WinXP takes around 10 seconds to boot into the desktop on my machine, while Linux takes around 30-40 seconds to enter runlevel 5.

    16. Re:I love this by eraserewind · · Score: 1

      I agree you see the XP desktop faster, that's my point. The thing is, though that it hasn't finished booting when it shows you the desktop. It continues for quite some time afterwards, whereas linux doesn't show you the desktop until all the other stuff is basically done. So this quick desktop falls into the category of "trick".

      The "complete" XP boot may or may not be overall faster, but you can't tell anything about it from how fast it shows you the desktop, other than the microsoft people are smart enough to know that we don't like to wait around for 40 seconds to use the desktop.

  19. Open Source Bloat by JamesP · · Score: 1, Insightful

    Sometimes I feel Open Source stuff is even more bloated than their Closed Source counterparts...

    I have a machine at work that struggles to run XFCE with only 256Mb of memory.

    Windows XP runs fine with that... I know, I know, security sucks, blah, blah, but!

    Open Source used to be pretty good at reducing bloat, but nowadays...

    --
    how long until /. fixes commenting on Chrome?
    1. Re:Open Source Bloat by JamesP · · Score: 0

      It's not supposed to be funny! I mean it...

      --
      how long until /. fixes commenting on Chrome?
    2. Re:Open Source Bloat by Bojan+Zivanovic · · Score: 0

      Hm.. Strange. I run KDE with 256mb of memory, and it is snappy. And we know what a monster it is... GNOME and Xfce always worked fine too...

    3. Re:Open Source Bloat by ray-auch · · Score: 1

      This isn't a new thing.

      The bloat reputation (in some cases) goes back to the beginnning of the Free Software movement, before Open Source even started.

      Proof ? - EMACS.

      That's "Eight Megs And Constantly Swapping" for those still in daipers when eight megs was a stupendous amount of memory...

    4. Re:Open Source Bloat by Anonymous Coward · · Score: 0

      Win XP runs fine on 256MB? LOL.

      It doesn't run fine even with 512MB becase it seems to be way too agressive in it's swap usage. If you have a slow disk using XP is like walking in quick sand no matter how much memory you have.

    5. Re:Open Source Bloat by Mathiasdm · · Score: 1

      XFCE running slow with 256 Mb of memory? What are you smoking?

      I run XFCE with 64 Mb RAM and it works perfectly. I won't even consider WinXP with that little RAM.

      --
      Join the anonymous, help develop the network: http://www.i2p2.de
    6. Re:Open Source Bloat by XO · · Score: 1

      as an aside, I'm really hating the 2 minute post timeout, as it makes it more difficult to make several comments in different threads on discussions that I particularly enjoy. oh well.

      hee hee hee I hadn't heard that about EMACS, but that's because i've been a 'vi' man since Unix System III was the big bad system. (I was about.. uh.. 10 then, so out of diapers.. hah)

      The key combinations required of EMACS often seem to require six fingers per hand, both hands in use, and then.. why.. on earth.. would a text editor.. have the ability to be used as an IRC client? *shakes head*

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    7. Re:Open Source Bloat by Anonymous Coward · · Score: 0
      I concur.

      I run FreeBSD-Stable (SCHED_ULE + PREEMPTION), Xorg-6.8.1 (No composite or RENDER option), XFCE-4.2 on a pentium 2 348MHz with 320MB + an old ATi Rage 3D Pro (Mach64)
      last pid: 68009; load averages: 0.05, 0.18, 0.18 up 32+05:02:42 17:31:55
      52 processes: 52 sleeping
      CPU states: 3.9% user, 0.0% nice, 3.1% system, 0.0% interrupt, 93.0% idle
      Mem: 172M Active, 41M Inact, 63M Wired, 20M Cache, 41M Buf, 9456K Free
      Swap: 1028M Total, 2580K Used, 1025M Free
      so glad I am not the only one struggling with XFCE's performance, coupled with bloatware/memory gobblers that are Firefox & Thunderbird, WinXP is an absolute dream!

      I think I shall go on a:
      (cd /usr/ports/www/firefox && make deinstall clean >/dev/null 2>&1) &
      (cd /usr/ports/mail/thunderbird && make deinstall clean >/dev/null 2>&1) &
      (cd /usr/ports/www/firefox && make deinstall clean >/dev/null 2>&1) &
      Frenzy and go back to lynx, Mutt and all the console goodness.

      PS. I cannot get a new video card, as it is an "old" (1999) Compaq Deskpro NX.

    8. Re:Open Source Bloat by XO · · Score: 1

      Hmm. I run XFCE4 fairly decently in 128MB, so long as I continue using Opera 8 as a browser, and don't want to load Mozilla or Firefox.
      Particularly now that the gaim memory leaks were apparently solved.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    9. Re:Open Source Bloat by SirBruce · · Score: 1

      That's why another acronym for EMACS at the time was "Escape-Meta-Alt-Control-Shift" Bruce

    10. Re:Open Source Bloat by IamTheRealMike · · Score: 1
      It used to be that "open source" desktops were missing a lot of functionality. As it was added to catch up with Windows/MacOS (and in some cases, exceed it) the resource requirements went up too.

      It's not like the open source tooth fairy magically makes people write tighter code, after all.

      It'll get better soon, as the most recent Linux desktops are getting pretty mature these days. While they still have issues with hardware/software compatibility, in the absolute modern GNOMEs are pretty good and the list of "Huge Must-Fix Problems" is vanishingly small. At that point polish and optimisation comes to the forefront.

    11. Re:Open Source Bloat by Anonymous Coward · · Score: 0

      It's not like the open source tooth fairy magically makes people write tighter code, after all.

      If you got in a time machine and went back to 1998, you'd certainly many Linux Advocates saying that it does. Probably the number 1 complaint about Windows in the old days was that it was "bloated" ... and well look what happened.

      If you look at the current situation, while you can optimize pieces, the pragmatic Linux desktop is always going to have masses of duplicative Gnome, KDE, Mozilla/XUL, and OpenOffice libraries open. The politics have created more perma-bloat than the programmers ever could.

    12. Re:Open Source Bloat by ckaminski · · Score: 1

      If your editor can suffice as a windows manager, it's overengineered.

    13. Re:Open Source Bloat by Anonymous Coward · · Score: 0

      Why an IRC client, games, email client, psycologist or whatever else?

      Because EMACS has a functional language called elisp that allows it. Elisp was created to allow the user to extend EMACS. And you know: the people are so inventive...

      The same elisp allows you to change the key combinations and even configure it to (disgusting!) vi's key combinations...

    14. Re:Open Source Bloat by XO · · Score: 1

      So why is there an EMACS, and not just an Elisp?

      Why would you want to extend your text editor into so many different things?

      It makes no SENSE!

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
  20. Novell's attitude towards Linux desktop by unixmaster · · Score: 4, Insightful

    As you can see from Novell's actions they are totally biased towards Gnome but still they make more money out of Suse distribution which uses KDE extensively.

    Feel the irony?

    They should instead be desktop neutral and support KDE developers too...

    --
    Never learn by your mistakes, if you do you may never dare to try again
    1. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      You are right, but Gnome development needs it badly while KDE has a far better architecture and simply do more with less.

    2. Re:Novell's attitude towards Linux desktop by unixmaster · · Score: 1

      KDE would develop in a faster rate if corporations like Novell support it more. There are many big plans for KDE4 but without corporate support it just takes more time to implement those.

      --
      Never learn by your mistakes, if you do you may never dare to try again
    3. Re:Novell's attitude towards Linux desktop by digidave · · Score: 1

      It's not irony. It seems quite obvious that they are preparing to make Gnome the default desktop in Suse. I imagine while they're improving Gnome they're also porting all their configuration tools to work with it.

      --
      The global economy is a great thing until you feel it locally.
    4. Re:Novell's attitude towards Linux desktop by schleyfox · · Score: 1

      I believe that QT scares them, I can definitely see where having the LGPL GTK could have an advantage over dual licenced QT. I don't know it just almost fits.
      (This is not an insult at QT, which is a fine library, but just not as free for everyone as GTK)

    5. Re:Novell's attitude towards Linux desktop by bhalo05 · · Score: 1

      I'm the parent poster, I was not logged in. I completely agree with you, my message was in part irony. Of course they're not supporting the better desktop but the one they fit them most. It's a shame, but this is starting to look more and more like one of those frequent times where the most advanced product is not the one massively used becaused they're pushing another with better marketing and more resources.

    6. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 1, Interesting

      The key question is, why should Novell support it? Anything built with Qt needs to either be open source or be licensed to TrollTech. This isn't a big deal for Novell's own projects but when they're pushing a Novell libraries that have to be used by outside developers, they're going to want to base it on something that doesn't put additional licensing burdens on developers (Win32 development doesn't carry licensing costs).

      If GNOME didn't exist, they'd likely put their backing on GNUstep or (god help us) Motif.

      Stuff like Mono, which is heavily GNOME centric and runs on Win32/Linux/MacOSX, only makes the decision easier. They can plug "write-once-run-anywhere" for Novel libraries.

      Of course, things may change if TrollTech found a way to make money by relicensing Qt to LGPL (or modified GPL as in Classpath) and provided seemless Java binding that can be used with GCJ and other free Java tools.

      OTOH, if corporations focused on KDE, it would likely be optimized for simplified as GNOME is (and likely dump duplicate works like KOffice in favour of OpenOffice and Konq in favour of Firefox for browsing the way Epiphany/Gnumeric/Abiword is shoved in the background for more modern GNOME distributions). The KDE community is strongly against such moves, so even with these changes they may end up going back to GNOME because GNOME's culture is very receptive to KISS elegance.

      So in the end, there are several non-technical issues why corps prefer GNOME.

      No big deal. Lack of corporate support hasn't stopped GNUstep development and it would stop KDE development.

    7. Re:Novell's attitude towards Linux desktop by 10Ghz · · Score: 3, Insightful

      It might be true that Gnome gets more corporate backing that KDE does. Yet it seems to me that even with all that money and resources being thrown at Gnome, they can only keep up with KDE, not surpass it. Maybe KDE has better design, maybe their hackers are simply better, I don't know. But it seems that they do not need all those resources to compete with Gnome, whereas Gnome seems to need the resources of Novell/Ximian, Red Hat and other just to be able to compete with KDE.

      I can't help but wonder what would happen if those resources were invested in KDE, instead of Gnome...

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    8. Re:Novell's attitude towards Linux desktop by selectspec · · Score: 1

      They bought Ximian which employs the key Gnome project managers.

      --

      Someone you trust is one of us.

    9. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      Actually, KDE started a year and a half before GNOME did and they had a polished widget set (Qt) and a company dedicated to support it. GNOME has to maintain both Gtk+ and GNOME and has had to do it with more "committee" involvement because there is no central Gtk+ company (like TrollTech) or dictator for life (like Linus or what Miguel used to be). As a results decisions are slower (look how long it took to replace the stupid file dialog box).

      If GNOME has caught up to KDE as you've implied, it either means GNOME development is faster (despite its painful bureaucracy) or KDE has been resting on it's lorels too long.

    10. Re:Novell's attitude towards Linux desktop by Sweetshark · · Score: 0, Flamebait

      ... that even with all that money and resources being thrown at Gnome, they can only keep up with KDE, not surpass it.
      Yeah, right. We all know KDE is better than Gnome. Thats why nobody uses Gnome.
      Maybe KDE has better design ...
      Most certainly not.

    11. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      I can't help but wonder what would happen if those resources were invested in KDE, instead of Gnome...

      I can't help but wonder what would happen if Trolltech went bankrupt and the KDE people were left alone to develop both the desktop AND the toolkit.

      Or if trolltech made Qt LGPL on all platforms and didn't get those benefits from companies paying them development licenses more expensive than MS' to release closed source software.

      Or better, what would had happened if Suse hadn't been there all those years to drive KDE development.

      But who cares, after all KDE has miraculously evolved from 0 to where it is today from volunteer work only. Who could believe any other thing?

    12. Re:Novell's attitude towards Linux desktop by bhalo05 · · Score: 1

      Of course, quality is measured by sheer numbers. That's why we all use Windows, right?

    13. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      KDE has a dedicated (paid) company that works on its toolkit. Trolltech's business revolves around this toolkit (QT), and therefore KDE devs can focus almost solely on the desktop itself, and fewew of the underpinnings. The Gnome project has made mistakes of ignoring important framework, and kinda just "tacked it on" as they went along. Look at GStreamer... That should have been divised YEARS ago.

    14. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      > ...dictator for life like Miguel used to be...

      But instead of Miguel we do have NEW dictators on GNOME. Don't forget my words.

    15. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      > > Maybe KDE has better design ...
      > Most certainly not.

      Actually KDE has a many times better design than GNOME but while reading your reply you have only proven that you have absolutely no clue. Most rants written here are written by clueless people.

    16. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      But instead of Miguel we do have NEW dictators on GNOME. Don't forget my words.

      Ya, bro! Take down the system yoh!

      This message was brought to you by the brainless anarchist syndicate.

    17. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      while reading your reply you have only proven that you have absolutely no clue. Most rants written here are written by clueless people.

      By not giving a single proven fact apart from "KDE rulez gnomez, and u dunno a thing", I can't tell who of you two looks more stupid.

    18. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      > They bought Ximian which employs the key Gnome project managers.

      Care to name what the Ximian key project managers actually manage inside cvs.gnome.org ?

    19. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 1, Insightful

      The problem with GNOME is it's broken framework that KDE doesn't have.

      Example:

      GTK+ Window, BonoboUI Window, GnomeUI Window. GNOME is currently stuffed with applications that is either written by using one of these UI creating libraries. The last two named ones should finally and forever made deprecated otherwise people keep continuing writing stuff that look, interact and behave differently than others.

      Ever tried to open a BonoboUI Window application on GNOME and then one with a GTK+ Window or a GnomeUI Window ? Look close to the Windows itself and you will notice something.

      Another issue is hardcoded GUI elements or an improper GLADE tool to create broken *.glade files (well not mostly broken but some elements that you can not alter with the GUI you might get different or wrong properties written).

      GNOME is also a memoryhog by depending on more and more stuff and libraries. Well I can write and write and write even more stuff and could easily add countless of things.

      The benefits in KDE here is that they have a constant UI system build up on *.moc files, the GUI's generated are generated out of one system. They deal with objects and nice plugins system and makes it easy for application writers to inherit these objects and plugins into other applications.

      I recently had the pain to remove all the DEPRECATED shit in my application. What was valid during GNOME 2.2 and 2.4 got drastically changed and stuff that initially was ok to use got marked deprecated and I somehow was forced to change a huge leap of code in my programm only to play catchup with the nowadays new requirements. Changed my application from BonoboUI to use plain GTK+ which took me quite some work to remove all embedded BonoboUI controls and have them replaced with individual widgets that the GTKUIManager can't deal with and and and. Had to remove the old GTKEntry in favor of the new GTKComboBox where I can not tie a GList to it anymore and thus had to create a new Tree system for and so on.

      We developers for GNOME 3rd party apps are permanently kept in catching up in the DEPRECATION process rather than getting forward in what we want to achieve with the tools. A clear sign that the Framework in GNOME is kinda hosed and requires a lot of work to get replaced piece for piece.

    20. Re:Novell's attitude towards Linux desktop by m50d · · Score: 1

      KDE is far more popular than gnome. (by votes, and by number of distros using it as default)

      --
      I am trolling
    21. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      We developers for GNOME 3rd party apps are permanently kept in catching up in the DEPRECATION process rather than getting forward in what we want to achieve with the tools. A clear sign that the Framework in GNOME is kinda hosed and requires a lot of work to get replaced piece for piece

      We developers for Java 3rd party apps, blah blah blah, DEPRECATION, blah blah blah. A clear sign that the Framework in JAVA is kinda hosed and requires a lot of work to get replaced piece for piece.

    22. Re:Novell's attitude towards Linux desktop by m50d · · Score: 2, Interesting

      I think it's mostly pragmatism. KDE doesn't make boneheaded decisions out of zealotry or theoretical merits. And KDE people seem not to get as attached to their bad decisions as GNOME people, if they made a mistake they will fix it.

      --
      I am trolling
    23. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      Now what ? Losing arguments and switched over to sarcasm ? Go, try teaching me about GNOME, I will be able to pull all the things you counter argue into dust.

    24. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      GNOME is also a memoryhog by depending on more and more stuff and libraries. Well I can write and write and write even more stuff and could easily add countless of things.

      Yeah... silly GNOMErs... they understand things like dependency trees and good software engineering. They should go the KDE way and shovel absolutely everything into a couple of monster libraries... l33t!

      The rest of your message is equally clueless and wrongheaded.

    25. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      > The rest of your message is equally clueless and wrongheaded.

      Care to elaborate what exactly was clueless and wrongheaded ? I'd like to have the ability to know where my mistakes in my explaination were. As long as you are unwilling to come up with that I take your reply as the usual flame and rant.

    26. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      If people would like to support KDE with money, there's an easy way to do it. Just go here...

      http://www.kde.org/support/

      As to why large corporations don't seem to be as willing to support KDE development as they do Gnome development it's a mystery to me. I'm tempted to say though that corporations feel that they can gain partial ownership of gnome and steer it in a direction that suits them best, and that they would not be able to do that as easily with kde. That's just a guess though.

    27. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      Now what ? Losing arguments and switched over to sarcasm ?

      If you want to use deprecation as a proof of flaws in a framework, you're gonna bit the dust, like it or not. Not my fault if you're a brainless zealot.

      Go, try teaching me about GNOME, I will be able to pull all the things you counter argue into dust.

      It seems to be the other way, dude. Wake up.

    28. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      > > Go, try teaching me about GNOME, I will be able to
      > > pull all the things you counter argue into dust.

      > It seems to be the other way, dude. Wake up.

      Until now you are only ranting.

      By the way greetings from your mom. I am riding her ass while typing this reply.

    29. Re:Novell's attitude towards Linux desktop by Sweetshark · · Score: 0, Flamebait

      To explain my rebuttal of the "KDE has better design" claim:
      Gnome is more open in development. It allows concurrent solutions for the same problem. Later the best solution will get picked, and the other solutions are deprecated. This might sound like a pain in the ass. It is.
      But the alternative (the approach used by KDE) is even worse. The requirements are collected and after that one solution is implemented. There are no alternatives to this solution. Just as you learned in your software engineering textbook. To bad reality doesnt play by the textbook rules. Requirements change all of the time - there is just no way to know them before you have a working implementation and its learned about limitations - there is no way to fix this later.
      The different design approach resulted in a pretty crappy start for Gnome. But it is gaining speed (as you can see with the 2.X releases). KDE OTOH seems to seriously slow down the older it gets.

      Some of these points can also be found here:
      http://www.ofb.biz/modules.php?name=News&file=arti cle&sid=318

    30. Re:Novell's attitude towards Linux desktop by IamTheRealMike · · Score: 1
      Huh? You clearly never read the threads where they were considering writing their own multimedia framework from scratch because GStreamer wasn't written in C++.

      I don't get where all this stuff about "KDE doing more with less" is coming from. When I see GNOME I see a polished desktop that I'd actually give my friends and family and not feel embarassed. It's slick, easy to use, and pretty fast. Frameworks and APIs are just means to an end: in this case, it seems KDE lost sight of that and put so much effort into the APIs that they became more important than the desktop did. I mean, look at the most recent releases - they've been talking about cleaning up the control center for years, longer than I've been using Linux in fact, yet it never gets done.

    31. Re:Novell's attitude towards Linux desktop by bhalo05 · · Score: 1

      I don't get where all this stuff about "KDE doing more with less" is coming from. When I see GNOME I see a polished desktop that I'd actually give my friends and family and not feel embarassed.

      It comes from many users who miss KDE integration and features in Gnome, as simple as that.

    32. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      > When I see GNOME I see a polished desktop that I'd
      > actually give my friends and family and not feel embarassed.

      I'd feel embarassed to tell people to use GNOME inside a company.

    33. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      By the way greetings from your mom. I am riding her ass while typing this reply.

      Now, that's the way to counter-argument. I wuv ya.

    34. Re:Novell's attitude towards Linux desktop by 10Ghz · · Score: 1
      Most certainly not.


      yes, you could say that KDE had better design. Gnome has only recently started to be technologically where KDE has been since 2.x-days! Kparts, DCOP, KIO-slaves etc. etc. Those have been around KDE for a long time and they are widely used. It seems to me that comparable stuff in Gnome are not as widely used, or they are so recent developements that they haven't yset gained any foothold inside Gnome. regardless: they have been in KDE for a long time, and are widely used.

      Yes, I maintain that the two desktops progress at a more or less similar pace. Difference is that Gnome has resources of Ximian/Novell, Red Hat, Sun and others at it's disposal, whereas KDE is predominantly a volunteer-effort. How do you explain the fact that the two progress at an equal pace, even though one of them has huge amount of resources at it's disposal, whereas other does not? If Gnome has a better design (as you claim), and huge amounts of resources being thrown at it (something not done for KDE), why doesn't Gnome walk all over KDE? The two seem to progress at an equal pace. According to your logic, Gnome should rule the desktop by now, with KDE withering in to irrelevancy. Unfortunately for you, that has not happened. Why is that? There seems to be something missing from your argument.

      I also saw you complain about KDE's developement-methods in your other post. I haven't seen any of that. They seem to have steady releases, with each release being better than the last one. I haven't seen any major slowdowns or the like. I really don't see what your point is.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    35. Re:Novell's attitude towards Linux desktop by 10Ghz · · Score: 1
      GNOME has to maintain both Gtk+


      uh, no. GTK+ is maintained by the GTK+-guys. And GTK+ was there when Gnome was born, it's not like they had to come up with yet another toolkit for their desktop.

      and has had to do it with more "committee" involvement


      How is that different from KDE? KDE has NO real leader, perceived or otherwise. there is no dictator who decides anything.

      there is no central Gtk+ company


      And you could say that there is no central KDE-company like Ximian, Red Hat or Sun. So what's your point?

      If GNOME has caught up to KDE as you've implied, it either means GNOME development is faster


      What happened back when the two projects were born is more or less irrelevant these days. And besides, I do not think Gnome has caught up with KDE. The two progress more or less at same speed, but that does not mean that Gnome has caught up with KDE. KDE still has (IMO) the technological edge. I would guess that Gnome is technologically about where KDE 2.2-3.0 was.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    36. Re:Novell's attitude towards Linux desktop by 10Ghz · · Score: 1
      You clearly never read the threads where they were considering writing their own multimedia framework from scratch because GStreamer wasn't written in C++.


      AFAIK, they are still debating as to what multimedia-framework to use in 4.0. Gstreamer has alot going for it, but it's being written in C instead of C++ is a hindrance.

      Frameworks and APIs are just means to an end: in this case, it seems KDE lost sight of that and put so much effort into the APIs that they became more important than the desktop did.


      You mean stuff like DCOP, Kparts and KIO-slaves? I for one use them every day. I simply do not see stuff like that in Gnome. Or, if it's there, it's not being used. KDE has technology that lets the user get job done. And it lets developers make their apps better. And both users and developers take advantage of that technology. And that results in better desktop. So I really fail to see the problem in trying to come up with kick-ass API's and frameworks.

      they've been talking about cleaning up the control center for years, longer than I've been using Linux in fact, yet it never gets done.


      KDE is pretty conservative with changes like that. They do not want to disprupt the desktop too much (unlike Gnome-hackers, who freely do stuff like switch to spatial filemanagement in a minor release...). But rejoice: you do have alternative method of accessing the settings (at least in 3.3 and onwards)! Fire up Konqueror, type "settings:/" in the location-bar, and you can change the settings of your system. No need to use the control center. Changing the actual control-center will propably take place in 4.0.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    37. Re:Novell's attitude towards Linux desktop by quigonn · · Score: 1

      Maybe KDE has better design ...
      Most certainly not.


      Most certainly _yes_. They've got the concept of kioslaves, they have DCOP, they have great interoperation between the applications. Ever seen the integration of KMail, aKregate, KNode and the KDE address book (forgot the name)? It's awesome. And this is the kind of features that Gnome is mostly lacking. Don't get me wrong, I personally prefer using Gnome to using KDE, but from the technical point of view, KDE is definitely leaps ahead of Gnome, and they achieved an increased productivity compared to Gnome because they're using an object-oriented language and toolkit.

      --
      A monkey is doing the real work for me.
    38. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      (by votes, and by number of distros using it as default)

      Yeah, because webvotes heavily trailed on dot.kde.org and the fact that "Jeffy's Uber-Linux" has KDE as its default really mean a lot compared to Sun's JDS deployments, Red Hat's EL and Novell's business offerings.

    39. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      KDE doesn't need any help optimising. Every release since 3.0 has been faster than the previous version. Qt 4.0 + KDE 4.0 + GCC 3.5 + recent binutils will be a major improvement again. Historically, x.0 releases are a bit slower, but the recent changes to the way C++ is handled will more than counteract that in 4.0's case.

    40. Re:Novell's attitude towards Linux desktop by Klivian · · Score: 1

      You mean like the way GNOME started to write their own multimedia framework from scratch becouse aRts was written in C++?

    41. Re:Novell's attitude towards Linux desktop by zsau · · Score: 1

      I can't help but wonder what would happen if those resources were invested in KDE, instead of Gnome...

      I know you're just trolling (or at least, painting an opinion as fact) but I'll bite anyway.

      If the resources invested in Gnome were invested in KDE, then KDE would be Gnome and Gnome would be KDE. Investors like the business-friendly environment of Gnome, and the easyy-to-use interface. That's what their money would make it become. The opposite is true of the free KDE developers.

      --
      Look out!
    42. Re:Novell's attitude towards Linux desktop by Ragica · · Score: 1
      GStreamer is a project independent of Gnome. The G in front of the name does not always automatically mean GNU or Gnome. Gnome just happens to use it; major KDE apps can use it as well.

      There was some talk of putting gstreamer in KDE 4. I'm not sure of the status of this; I have also heard that KDE is going to great a multimedia engine framework that can work better with multiple engines...

    43. Re:Novell's attitude towards Linux desktop by Ragica · · Score: 1
      Not to belittle TrollTech's amazing contribution, but all indications from my non-expert perspective are that things would continue quite nicely. The GPL Qt is, from all I've heard, exceptionally well organized and engineered... and has amazing documentation.

      An argument might be made that things would go even faster (and they are already amazing fast) for KDE if the team got control of GPL Qt development. But things are going nicely as they are.

      Philosophically the partnership between KDE and Qt seems (again, just my ignorant opinion) quite ideal however. Unlike the various Gnome corporate sponsors, who seem to me to be always mostly interested in "patching things up" in various areas, the focus of Qt to commercial demands at designing a strong design and key features has provided KDE an awesome base.

      By the way TrollTech is GPL'ing the new Windows version... so once again, just like when they GPL'd the X version, there is one less argument against Qt... though that argument has always been mostly irrelevant and just a point of political pique. (And i see ignorant people on this thread still making the old non-GPL throat warbling FUD...)

      Other tidbits... QTopia 2.1 is open source. Opera is the fastest browser. Apple chose KHTML over Gecko. SuSe rocks... but personally i use Gentoo and FreeBSD.

    44. Re:Novell's attitude towards Linux desktop by Filmwatcher888 · · Score: 1

      They are being "desktop neutral". by trying to lift GNOME's memory footprint to the same level as KDE, both products end up using the same amount of resources. Then, Novell could sign up _both_ KDE and GNOME fans.

    45. Re:Novell's attitude towards Linux desktop by fungai · · Score: 1

      nat friedman said on the linux link tech show that suse wil move to gnome... it was in an interview that was linked to slashdot about a week or 2 ago.

    46. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      The requirements are collected and after that one solution is implemented.

      You don't know what you are talking about. Look at Kate/Kwrite/Kedit. Look at Amarok/Juk/Noatun/Kaboodle. Look at KPDF/KGhostscript. Look at KMobile/KMobileTools/Kandy. There are plenty of concurrent solutions.

      KDE OTOH seems to seriously slow down the older it gets.

      Bullshit. Everybody who actually uses KDE knows that it's been getting faster and faster since 2.0.

    47. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      there is no central Gtk+ company

      And you could say that there is no central KDE-company like Ximian, Red Hat or Sun. So what's your point?

      Way to dodge the point. Compare like and like, please. GTK+ to Qt, not GTK+ to KDE. There isn't a company dedicated to maintaining GTK+. There is a company dedicated to maintaining Qt.

    48. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      I can't help but wonder what would happen if Trolltech went bankrupt and the KDE people were left alone to develop both the desktop AND the toolkit.

      If that happens, there's an agreement in place to BSD license Qt. That means it's suddenly acceptable for proprietary developers and Windows and Mac developers at zero cost. The mindshare would rapidly rise, and the only real objection systems integrators have to KDE - the fact that proprietary software needs to license Qt - would disappear.

      Trolltech going bust would probably be the best thing to ever happen to KDE. No offense to Trolltech intended, they are doing a great job of maintaining and developing Qt.

    49. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      Anything built with Qt needs to either be open source or be licensed to TrollTech.

      No. Anything built with Qt needs to either be open source or license Qt. It does not have to be licensed to TrollTech at all.

      Stuff like Mono, which is heavily GNOME centric and runs on Win32/Linux/MacOSX, only makes the decision easier. They can plug "write-once-run-anywhere" for Novel libraries.

      Ever heard of Qt#?

    50. Re:Novell's attitude towards Linux desktop by 10Ghz · · Score: 1
      There isn't a company dedicated to maintaining GTK+. There is a company dedicated to maintaining Qt.


      So what? Why is that relevant? There is a company dedicated to improving Gnome (Ximian), KDE does not have such company. Why is that fact irrelevant?
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    51. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      There is a company dedicated to improving Gnome (Ximian), KDE does not have such company. Why is that fact irrelevant?

      Huh? We're talking about how KDE had a head-start because it started earlier and was based around a high-quality, professionally maintained toolkit.

      It doesn't matter what the recent developments have been, it doesn't change why KDE has had a head-start compared with GNOME.

      You seem to be stuck in a "GNOME vs KDE" flamewar mentality. Grow the fuck up.

    52. Re:Novell's attitude towards Linux desktop by m50d · · Score: 1
      If there was such a thread (and I am subscribed to kde-multimedia and didn't see it) I can't imagine it being about anything other than the practical problems mixing C and C++ causes. The primary, in fact pretty much only, reason I saw for not adopting gstreamer was its lack of stability, which is still a concern.

      Anyway, the proof of the pudding is in what they actually do, and kde looks to be about to adopt gstreamer. Even if they don't, they have adopted plenty of gnome technologies e.g. DBUS, either because they are superior or simply for integration. Wheras I can't find a single case where gnome has adopted a kde technology. Gnome went beyond mere discussion and wrote esd from scratch because they didn't want to use arts.

      The stuff is coming from the users who see it. I have actually tried my family on both, and those who notice prefer kde. As do I, because it looks far nicer and is much better integrated. Look at Linux Format's review of gnome 2.8 - they give it a high rating and the reviewer talks about having overtaken kde, yet if you read the whole thing all of the improvements he lists are things which have been in kde from 3.2 or earlier. And yet gnome is the only desktop which publicly recieves corporate support.

      The APIs may get more attention but it has paid off. Gnome has three inconsistent apis to use for your widgets, and a lot of cruft and a not insignificant performance hit that comes from them. KDE has only one Right Way to do anything, but the APIs that exist are clean and very useable. Remember the mozilla port in 48 hours? And you can do more with them. So people build the apps, and they are good. Things like K3b; an independent project that works very well, looks good and is integrated properly.

      --
      I am trolling
    53. Re:Novell's attitude towards Linux desktop by m50d · · Score: 1

      Not on kde.org, on that independent windowmanager listing site. It didn't win, but kde was well above gnome. And have you bothered to actually look at Novell's offerings? Because I think you'll find they are suse and ship with KDE as the primary desktop, although gnome is also supported. (Interestingly, kde distros tend to support gnome but gnome ones do all they can to avoid including kde. I'm biased but the obvious explanation is that they're afraid to give their users the choice). Even if you look at number of users on primarily kde distros compared to those on gnome distros, I think you'll find they come out ahead.

      --
      I am trolling
    54. Re:Novell's attitude towards Linux desktop by 10Ghz · · Score: 1
      it doesn't change why KDE has had a head-start compared with GNOME.


      Yep it did. It was started before Gnome was started. But at this point, that difference is more or less irrelevant. Few moths difference back then is irrelevant today, since both desktops have thousands of man-years of developement behind them.

      ou seem to be stuck in a "GNOME vs KDE" flamewar mentality. Grow the fuck up.


      Pot, meet ketttle. Kettle, this is pot.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    55. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      it doesn't change why KDE has had a head-start compared with GNOME.

      Yep it did.

      The fact that GNOME now has corporate sponsorship changes the reason why KDE had a head-start? Don't move the goalposts. This is how the discussion progressed:

      1. Someone else: KDE had a head-start compared with GNOME because they started earlier and had a high-quality toolkit that was supported by a company.
      2. You: GNOME is supported by companies!
      3. Me: Yes, but that has no bearing on what happened back then.
      4. You: That's irrelevent now!

      Pot, meet ketttle. Kettle, this is pot.

      Not in the slightest. I'm no DE cheerleader, you are the one turning this into a "my desktop versus yours" argument. I've not said a word either way as to which DE I prefer, although it seems obvious you've decided I'm a KDE user who is out to belittle GNOME.

    56. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      Not on kde.org, on that independent windowmanager listing site. It didn't win, but kde was well above gnome.

      Heavily trailed on dot.kde.org -- webvotes are as reliable than U.S. Presidential electons, and just as easy to ballot stuff. I wouldn't put any faith in a webvote if GNOME won it either.

      And have you bothered to actually look at Novell's offerings?

      I've bothered to look at Novell's *business* offerings (which is the point I made in the post). *ALL OF NOVELL'S BUSINESS DEVELOPMENT IS GOING INTO GNOME* This is a fact... Novell's still ships its consumer SUSE distro with KDE -- but that isn't likely to last too long.

      Even if you look at number of users on primarily kde distros compared to those on gnome distros, I think you'll find they come out ahead.

      I think you'll find you are wrong. If you restrict your sample to crazed zealots who inhabit slashdot, you may find KDE comes out ahead. But the huge commercial deployments of Sun/RH and Novell dwarf those (Sun's JDS in particular)... and they are users that actually matter, not noisy slashdot shouters.

    57. Re:Novell's attitude towards Linux desktop by m50d · · Score: 1
      Suse professional still ships with kde, and they have publicly stated that they remain committed to supporting it.

      I don't know about crazed zealots, but how do you suggest I sample other than looking at online registrations and polls? They may be a bit biased against business users, but I'm pretty sure most distros suggest people register and not very many home users do either. If you go for big publicised migrations like Munich you're going to be far more heavily biased in favour of the "business" distros. To the best of my knowledge there haven't been any large-scale "which OS do you use" surveys other than on the web.

      --
      I am trolling
    58. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      I don't know about crazed zealots, but how do you suggest I sample other than looking at online registrations and polls?

      C*O*M*M*E*R*C*I*A*L

      D*E*P*L*O*Y*M*E*N*T*S.

      When people have paid good money and based their business on it. Should I repeat it again?

    59. Re:Novell's attitude towards Linux desktop by m50d · · Score: 1

      Oh yes. Because looking exclusively at what big businesses are selling to other businesses and ignoring what home users choose for themselves will really give a fair and balanced picture of which desktop the users prefer.

      --
      I am trolling
    60. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0

      It's a lot more fucking realistic and representative than quoting rigged webvotes that have been heavily promoted on dot.kde.org and ballot-stuffed to fuck and back, and a bunch of redundant distros thrown together by teenagers in their spare time that no-one uses.

      These people paid *money*... actual hard cash... to use the software and get support. It's not some loud-mouthed KDE supporter with nothing to back up his argument... it's actual deployments with legal contracts and serious money. Perhaps when you grow up and your head clears of the all the zealotry and fanboy nonsense you'll understand this.

    61. Re:Novell's attitude towards Linux desktop by m50d · · Score: 1

      If they paid money for the support, they are likely to have taken whatever the people offering the support are offering them. Businesses are unlikely to care whether they are using gnome or kde, they care about the support and will do as the support people care. Home users are the ones who are actually choosing for themselves the OS they want to run. The actual users will likely look at both desktops and try them, and see what they prefer. Corporate users will likely take what they are given - you don't mess with the software on a corporate machine, you get on with working with it. And the fact you're resorting to insults shows you know you've lost the argument.

      --
      I am trolling
    62. Re:Novell's attitude towards Linux desktop by Anonymous Coward · · Score: 0
      I have hard data on commercial users. You have a webpoll that, even if you take it at face value (a ridiculous notion given how hopelessly unreliable they are), shows KDE just a little bit ahead. Christ you're a pathetic zealot.

      The actual users will likely look at both desktops and try them, and see what they prefer. Corporate users will likely take what they are given - you don't mess with the software on a corporate machine, you get on with working with it.

      Not met a lot of real users then, have you? You do realise that you're talking a complete load of bollocks -- as anyone familiar with Microsoft's near-total dominance of the desktop will testify.

      And the fact you're resorting to insults shows you know you've lost the argument.

      You aren't making an argument. You are stating that you believe KDE is more popular... based entirely on FAITH. You have nothing to back up your statements of faith other than assertations that fly in the face of fact. It's rather pathetic really.

    63. Re:Novell's attitude towards Linux desktop by m50d · · Score: 1
      I have hard data on commercial users. You have a webpoll that, even if you take it at face value (a ridiculous notion given how hopelessly unreliable they are), shows KDE just a little bit ahead. Christ you're a pathetic zealot.

      Not just a little bit, quite a way ahead. 181-70 in fact.

      Not met a lot of real users then, have you? You do realise that you're talking a complete load of bollocks -- as anyone familiar with Microsoft's near-total dominance of the desktop will testify.

      Yes I have. Sure many home users don't fiddle that much. But they will try different types of software, they will at least look at some alternatives for some things they do. I defy you to find a home machine where the user hasn't installed at least one piece of software since it was set up for them. Yet I can show you plenty of corporate machines where that's the case.

      You aren't making an argument. You are stating that you believe KDE is more popular... based entirely on FAITH. You have nothing to back up your statements of faith other than assertations that fly in the face of fact. It's rather pathetic really.

      I have webpolls and lists of distros. Yes, not the most reliable of data, but it's some. You claim you have solid evidence for commercial users, which I haven't seen, and are claiming that this better reflects user preferences than what people vote for and what distributions ship.

      --
      I am trolling
  21. Nah by Anonymous Coward · · Score: 0

    A good coder would just rewrite that heap of crap from scratch. Konsole is good, except I don't want to load all the libraries just to get a usable terminal in my GTK+ based WM.

    1. Re:Nah by _|()|\| · · Score: 2, Informative
      GNOME Terminal is actually a wrapper for VTE, which is a rewrite of ZVT. More than anything, I think it just needs more attention. The bugs pile up, but VTE is basically maintained by an overworked Red Hat developer.

      One person attempted a hefty rewrite, but ended up forking to the Multi Gnome Terminal.

  22. Re:horrible idea by BenjyD · · Score: 3, Insightful

    Yeah, because GNOME is only developed by volunteer hermits living in caves at the moment. It's not like there are big companies paying developers' salaries to work on it or anything.

    It's GPL therefore it's Free software. Whether people are paid to work on it or do it out of the goodness of their heart doesn't matter as long as their contributions are GPL.

  23. motivation or reward? by jd142 · · Score: 2, Insightful

    Is this motivation for people to find the bugs, i.e., there's some programmer out there thinking, "Hmm, if I do this and this, then Gnome will run three times as fast. Oh well, I'm a KDE supporter so I don't care." Or is this a way to reward all of those people who do care about Gnome and are working on it by giving them a specific area to concentrate on and then rewarding them for their hard work, in other words some programmer thinking, "Hmm, I've got some free time and I can either work on fixing eyecandy or fixing memory leaks. Guess I'll fix the memory leaks first and get a reward."

    Everyone has been assuming that this is pure motivation, appealing to the greedy nature of people who aren't already contributing. I don't think that's the case. Generally speaking, those people who are good programmers and know the code well enough to actually identify and fix problem areas are probably already doing so. This "bounty" seems to be more a way of rewarding them and helping to give them a list of priorities.

    1. Re:motivation or reward? by Steve+Cowan · · Score: 1

      ...or, maybe they're trying to reduce the bloat in Gnome.

  24. Re:horrible idea by mattyrobinson69 · · Score: 2, Informative

    the kernel development is funded by the OSDL, some are under the direct employ of redhat, and probably other companies (maybe novel, IBM, im not sure)

    trolltech is a company that makes QT, and thats duel licensed, one license being GPL.

    the firefox lead developer is employed by google.

    many large opensource projects have people being paid to develop them fulltime, its a good thing because the source stays open.

  25. Re:The best way to improve Gnome... by Anonymous Coward · · Score: 0

    no, they want to reduce bloat not increase it

  26. eugenia? by hitmark · · Score: 1

    not the eugenia from osnews now is it?

    --
    comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    1. Re:eugenia? by Anonymous Coward · · Score: 0

      smelly cunt

  27. Perhaps they want to move away from KDE? by glrotate · · Score: 1

    This would be a good way of paving the way.

  28. Re:horrible idea by Fishead · · Score: 1

    What if someone wants to work on an OSS project, yet finances won't allow them? I think this is great.

    If I was a financially troubled programmer (heck, if I was a programmer at all) I would be interested in taking on one of these projects not only because of the benifit to the community, but the extra cash can help programmers with such real world necessities as WoW registrations.

  29. A new by Anonymous Coward · · Score: 0

    I'm gonna code me a new RV...

  30. This can only be good by schleyfox · · Score: 3, Insightful

    I like this, from my observations it alwasy appears that OSS is a bit heavy on the memory while closed source tends to be heavier on harddrive and processor dependent (not to say it is bloat free, far from it). That said, I run Gnome 2.8 on my old Pentium 2 laptop with 128mb of RAM. It actually works decently well, other than the screen refreshes which can use up all my processor and still take a few days :) . It is quite usable though and future versions of gnome will hopefully perform even better. Thank You Novell

    1. Re:This can only be good by spitefulcrow · · Score: 1

      Are you referring to the fact that "top" and "free" will always show almost all of your memory being used on a Linux system? This is because Linux caches as much data as it can to avoid accessing the even-more-expensive-and-slower-than-RAM hard disks and optical drives.

      --
      Sorry, my karma just ran over your dogma.
    2. Re:This can only be good by XO · · Score: 1

      That comment is incredibly out of date. My web server typically has 64+MB of it's 384MB free at any given time (even when being pounded by a Fark photoshop contest entry). On the other hand, my desktop has 128MB and is almost always 100+MB into the swap file at any given time. Thanks!

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
  31. Time and space complexity concerns by rbrito · · Score: 4, Interesting

    Now, it seems that (finally) developers are looking at resources that our programs use.

    Unfortunately, for many in developing countries (like me, here in Brazil) having a computer filled with RAM and with the fastest processor available on the market isn't an option.

    For instance, my desktop has a Duron 600MHz with 256MB of RAM. That's the fastest computer to which I have access here and it is some years old, but still working fine.

    I can't say how happy I am with this bounty for optimization of memory.

    In Computer Science we always have this concern with both time and space complexity and it seems that if Free Software developers start caring about good data structures and good algorithms (and avoid layers and layers and layers of abstraction over and over), we can actually use our computers more efficiently.

    Again, this is especially important for those who have to use computers of two or three generations ago.

    A welcome movement indeed.

    P.S.: If you have never felt the need for less memory comsumption, then you won't probably understand how important this project is and probably this post makes little sense to you.

    1. Re:Time and space complexity concerns by Anonymous Coward · · Score: 0

      They aren't avoiding layers of abstraction, they're targetting poor design choices that had unexpected importance on overall performance. They're not going to sacrifice good engineering for lower resource consumption.

    2. Re:Time and space complexity concerns by Anonymous Coward · · Score: 0

      If you think that is an important matter, have you ever thought about doing something for it? You don't have to a programmer, submitting bugs also helps, like the article tells.

      I hate it if there is a memory leak in my program (or any bug for that matter) and if I get a bug report for someone, I usually make a priority 1 for me to fix that bug.

      If you are already doing everything you can, sorry about this post ;)

    3. Re:Time and space complexity concerns by Anonymous Coward · · Score: 0

      In Computer Science we always have this concern with both time and space complexity and it seems that if Free Software developers start caring about good data structures and good algorithms...

      Ssssh! I need to use Free Software as a strawman in my academic (CS) projects.

  32. Perfect Labor Capital Market by Doc+Ruby · · Score: 3, Interesting

    We might finally have the open source capitalism model that kills these "commie" snipes dead, and leaves proprietary competitors dead in the water. Offer to employ programmers by buying their labor in a contest! Leverage the open source on the Net to get as many job applicants as possible, who submit the finished work, then give the "job" to only a single winner whose superior work is used. The losers need only inspect the open source of the next version for any of their content to keep the process honest.

    This creates parity for labor in the capital markets. Programmers can sell their labor as a packaged product, just as vendors can resell the programs to consumers. Programmers can market their code with better documentation, APIs and popular features. While integrators like Novell can get access to the labor market, without risking that the labor they're buying is better at job interviews than at delivering on deadline.

    There is an issue of the "waste" of the losers' code submissions. But since these projects are open source, the losers can fork the project and compete with it. If the losers are really better, they can compete better with the original project - which itself might be forked by the original contest sponsor. Brand equity will determine winners in the long run, but the open source lets brand equity be earned by persistent quality, as determined by the consumer market, rather than the funder of the code.

    Ladies and gentlemen, start your engines!

    --

    --
    make install -not war

    1. Re:Perfect Labor Capital Market by hsoft · · Score: 1

      1. Create a "contest" for some code.
      2. Take none of them, or take a fake submission you created yourself
      3. Let the fool create a forked project
      4. Get the code for free (It's open source right?) and integrate it in the project.
      5. Profit!

      --
      perception is reality
    2. Re:Perfect Labor Capital Market by Doc+Ruby · · Score: 1

      How would you integrate it into the project, without publishing it, and getting caught? If you published your own code, why would you bother recruiting others' code (unless yours were actually better)?

      --

      --
      make install -not war

    3. Re:Perfect Labor Capital Market by hsoft · · Score: 2, Insightful

      There is no need to hide the fact that you took the code. It is perfectly legal and ethical to take GPLed code and integrate it into another GPLed project.

      Thus, what I'm saying is that to get a guy to create GPLed code for you for free, you only have to start a "contest", don't take the guy's submission, wait until he forks your project with the code he created for the "contest", and integrate that code in your own project. Perfectly legal and ethical, since your project is also GPL, and you didn't pay a penny for that code.

      --
      perception is reality
    4. Re:Perfect Labor Capital Market by Doc+Ruby · · Score: 0

      The GPL requires you publish the new code. If you use my code, you have to publish it, and I can see that you've used my code. If you don't pay me, you've violated the terms of the contest. Although it's legally sufficient that you solicited my code under the terms "I'll pay you if I use it", I would submit my code with a reaffirmation that you can use it if you pay me, as you offered. This transaction is pretty clear and simple, and protected from the abuse you describe.

      Any forking by the submitter is irrelevant to the contest, or requirements to honor its terms, unless the contest terms prohibit it (which hasn't been mentioned). Even if the terms do prohibit forking (competition), they can only be enforced if the code is used - which forces payment, as I've detailed. Pretty cut and dried.

      --

      --
      make install -not war

    5. Re:Perfect Labor Capital Market by hsoft · · Score: 1

      I guess I didn't make myself clear enough. Let's go with an example:

      - CompanyA has a GPL project ProjectA.
      - CompanyA wants to add a feature to ProjectA, and starts a "contest"
      - DeveloperA creates some great code, and submit it to CompanyA for the "contest"
      - CompanyA asks one of it's developers to create a fake entry to the "contest"
      - CompanyA chooses the fake entry as the winner.
      - DeveloperA, seeing that his code hasn't been chosen, forks ProjectA, and name the forked project ProjectB
      - CompanyA, seeing the GPL ProjectB, take a look at it, find the code create by DeveloperA in ProjectB, take that code, and integrate it to projectA.

      Now this was perfectly legal because CompanyA didn't use the DeveloperA submission, it used ProjectB (a GPL project) code. with GPL, you CAN'T restrict the use of the code. Thus, if DeveloperA releases the code under GPL, *anybody* can use it, including CompanyA. Free developer labor!

      --
      perception is reality
    6. Re:Perfect Labor Capital Market by Knuckles · · Score: 1

      Congrats, you just killed the reputation of the company

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    7. Re:Perfect Labor Capital Market by Spectra72 · · Score: 1

      I don't have to publish the source unless I distribute. I can take all the GPL code I want, make all the changes I want, but as long as I don't distribute the resulting work, I don't have to publish jack or squat. I can simply enjoy all the benefits in-house. This is quite explicit from the FAQ. Now, in terms of Novel and this contest specifically, it's quite obvious that they will be distributing the resulting work, so of course they will be required to publish the source. The contestants will therefore have that protection.

    8. Re:Perfect Labor Capital Market by Doc+Ruby · · Score: 1

      The contest rules don't prohibit Novell from getting your code from another publication other than your submission. Of course you can't prohibit them from copying a GPL'd copy on the Net, but you can prohibit them from accepting the copy you submit directly, by requiring they accept it only provided they do not use a copy available elsewhere. OTOH, if you fork the project to include your code upon rejection, why should Novell be different from anyone else in their freedom to use your code, just because they got you to write it?

      And your scam is not really free. CompanyA paid to run the fake contest, and even to create the fake winning code. Then they had to wait for DeveloperA to fork the project. Then they had to reevaluate ProjectB, to take the code, and take it.

      These bounties are for tiny tasks, which cost less in time and money than the overhead of the scam you describe. DeveloperA is going to fork the project only for code larger than they would risk developing on a no-guarantee bounty. In my original post, I was talking about many losing developers, with a large combined contribution and experience, possibly forking the project.

      --

      --
      make install -not war

    9. Re:Perfect Labor Capital Market by Doc+Ruby · · Score: 1

      True. Of course, this contest is no different in regards to this scam than any other submission of work that can be "rejected" without payment, but secretly used.

      --

      --
      make install -not war

  33. Ditch the dependencies and deprecated code by Florian · · Score: 4, Interesting
    The bounty is a first good step, but the Gnome project will have to go much deeper to get rid of its bloat.
    • Remove all deprecated libraries from the codebase of the Gnome core.

      In its history, Gnome has changed its libraries and subsystems several times, from imlib to gdk-pixbuf, from gnome-canvas to pango, from Corba to Bonobo to possibly Mono, from esd to gstreamer, and so on. Many Gnome apps still use older, deprecated libraries. Get rid of those libraries and port all apps to the standard core API.

    • Remove or replace subsystems which never really were useful

      I'm thinking of Bonobo and gnome-vfs here which are not consistently used in Gnome and whose quality and use value is questionable. If their functionality is still needed, it could be replaced by KDE's superior kioslaves and kparts (just as KDE is ditching its arts sound demon in favor of gstreamer)

    • Make all demons optional

      Neither Gnome, nor KDE applications should be depending on any desktop-specific userspace demons. Make it possible to deactivate gconf, for example, and have applications read and write configuration files the classical Unix way, by one central switch. Make the sound demon optional, so that audio output could just be written (in old-fashioned, non-overlapping way) to /dev/dsp. Etc.etc. The demons might have some use for some people, for for many, they are just bloat and unnecessary complexity.

    Yeah, I know that all would be a Herculean effort. Probably, it makes more sense to start with a lean and clean codebase like XFCE and just bring its usability to Gnome level, instead of cleaning up a bloated mess...
    --
    gopher://cramer.plaintext.cc http://cramer.plaintext.cc:70
    1. Re:Ditch the dependencies and deprecated code by Stween · · Score: 2, Interesting

      Yes, what you suggest would be a substantial effort, but it all makes sense.

      I particularly like:

      Make all demons optional

      Neither Gnome, nor KDE applications should be depending on any desktop-specific userspace demons. Make it possible to deactivate gconf, for example, and have applications read and write configuration files the classical Unix way, by one central switch. Make the sound demon optional, so that audio output could just be written (in old-fashioned, non-overlapping way) to /dev/dsp. Etc.etc. The demons might have some use for some people, for for many, they are just bloat and unnecessary complexity.


      I always run a fairly minimal setup, due to preference rather than any burning desire to use as few clock cycles as possible. To have settings carry for applications like Gaim I use on a regular basis, I have to run 'gnome-settings-daemon' before starting any application such as this for them to look how I want them to look.

      Sure, it's something I put into ~/.xinitrc and forget, but I could have saved myself some time many moons ago when I was figuring out just what the hell I was meant to be running for the application settings to carry.

      I'm all for this third and final suggestion of yours :)

    2. Re:Ditch the dependencies and deprecated code by zeromemory · · Score: 1

      Make all demons optional

      I'm sure making all demons optional will certainly be a welcome change...

      But, seriously, your suggestions seem crazy to me:

      Make it possible to deactivate gconf, for example, and have applications read and write configuration files the classical Unix way, by one central switch.

      Deactivate gconf with one central switch? Not only would that require rewriting a ton of applications, it would also be incredibly impractical. How would we deal with common variables? Oh yes, let's just make another randomly-named file stored in some random hidden directory and have all daemons read from it. No thanks, I'll stick with gconf.

      Make the sound demon optional, so that audio output could just be written (in old-fashioned, non-overlapping way) to /dev/dsp.

      You do realize that using the sound daemon is already optional in Gnome, right? Check Applications->Desktop Preferences->Sound. And sure, let's only allow _one_ application to use the sound device at a time. That really sounds like progress...

      The demons might have some use for some people, for for many, they are just bloat and unnecessary complexity.

      I don't know about bloat, but I find it ironic that the two types of demons you mentioned are usually transparent to a user's experience.

    3. Re:Ditch the dependencies and deprecated code by BenjyD · · Score: 1

      > And sure, let's only allow _one_ application to use the sound device at a time.

      With ALSA and DMIX, any sound card can be used by any number of programs at once. I think many cards will do hardware mixing as well. ESD really isn't necessary any more at all.

      The processor usage of ALSA vs ESD playing back Oggs is much lower.

    4. Re:Ditch the dependencies and deprecated code by oliverthered · · Score: 1

      'Make all demons optional'

      And this will reduce bloat in what way? I fail to see how having a central service instead of each application implementing the services it's self (possibly badly or out of data) is going to cut the bloat and complexity.

      Applications are free to cat dev/ramdom > /dev/dsp and screw up my system or assume that my fstab is in standard format and not XML any time they like, today, at no added cost. Or they could use gstreamer and getmntent and do the job properly.

      --
      thank God the internet isn't a human right.
    5. Re:Ditch the dependencies and deprecated code by Anonymous Coward · · Score: 0

      1. The canvas is not comparable to Pango.
      2. Bonobo uses CORBA, it is not an alternative.
      3. gstreamer and esd perform different operations, but esd is being deprecated.
      4. The VFS is used by all real GNOME applications, and ditching it is stupid.
      5. KDE's kioslaves are not superior to the VFS.
      6. Offering more options to remove the daemons that GNOME relies on for configuration and such adds more complexity and does not help performance.

      In short you're an ignoramous. Shut up.

    6. Re:Ditch the dependencies and deprecated code by moranar · · Score: 1
      Yeah, I know that all would be a Herculean effort. Probably, it makes more sense to start with a lean and clean codebase like XFCE and just bring its usability to Gnome level, instead of cleaning up a bloated mess...

      NIH Syndrome! NIH syndrome!

      Seriously, you seem to imply that it's somehow easier, or even possible, to replicate the insane amount of effort the GNOME and KDE desktops have made in all fronts in a short period of time, rather than pruning the bad fruits, as it were. Suuuure. Not to mention that you're assuming also that a clean, lean codebase actually exists and is scalable to this.

      The last time someone did that, they were called "Netscape". Rings any bells?

      --
      "I think it would be a good idea!"
      Gandhi, about Internet Security
    7. Re:Ditch the dependencies and deprecated code by Anonymous Coward · · Score: 0

      Now if the only Unix in the world was Linux, that would matter terribly, wouldn't it?

    8. Re:Ditch the dependencies and deprecated code by jcupitt65 · · Score: 3, Informative
      That's a good idea. There's also a lot of deprecated API (eg. GtkCTree) which can be removed from the system with just a few -Dsomething during configure. You can turn off the GObject run-time type checks with another -Dthing, which helps speed another 10% or so in my experience.

      Bonobo is slowly being removed since GtkUIManager came on the scene. I think gnome-vfs will be around for a while, especially since the new file chooser can plug in to it (I think).

    9. Re:Ditch the dependencies and deprecated code by cortana · · Score: 3, Insightful

      > Remove all deprecated libraries from the codebase of the Gnome core.

      I believe that deprecated libraries tend to be replaced by stubs that backport the new functionality to the old API. Eg, the gnome_sound_play function currently sends a sound file to Esound; when (if) GStreamer becomes part of the platform, the function in libgnome will be replaced with code to do the same thing in GStreamer.

      The old APIs can not be removed until the developers decide to make a new release backwards-incompatible--this will be Gnome 3.0 (http://live.gnome.org/ThreePointZero).

      > Remove or replace subsystems which never really were useful

      Most people I see using Gnome use GnomeVFS all the time. Being able to access files shared on the network without having to be root to mount them is really nice. Even nicer is the sftp virtual filesystem, used for accessing files over SSH's SFTP. If GnomeVFS is to be replaced by something else, it will be by freedesktop.org's D-VFS.

      As for Bonobo: I believe panel applets use it all the time, and I don't think KParts can be a sensible replacement for it: Bonobo isn't just for GUI components. Since it is a Corba implementation, one can use out-of-process components with it, as well as components running accross the network. It's more like DCOM, whereas Kparts are analogous to ActiveX.

      Furthermore, I don't see the Gnome developers starting to use C++ any time soon. Besides the matter of taste and familiarity, C++ has problems with ABI stability. It took an age for Debian to recompile every C++ program when GCC 3.2 came out; I believe one of the reasons GCC 3.4 won't be in Sarge is because it breaks ABI compatibility again.

      > Make all demons optional

      Sounds like you want to duplicate the code from the daemons and copy it into each application. This would only increase memory usage and the number of bugs, while decreasing functinality. The reason GConf is really, really good is because of the signals/notification system. I'm not sure one's desktop would run much faster if every program one used polled its config file for updates every second.

      As for Esound, it will go away in the future if GStreamer becomes a part of the Gnome platform. This will be really nice when it happens, because the job of picking which sound server to use (esd/polyp/arts/jack/none), configuring it, etc will be left up to the distributor. But GStreamer has a fair bit of improvement to do before this can happen; and since removing Esound all together is backwards incompatible, it will have to wait for 3.0.

    10. Re:Ditch the dependencies and deprecated code by idlake · · Score: 1

      How would we deal with common variables?

      We put them where they belong: into the X11 server. It is, in fact, depressing that the most common native X11 desktop fails to use standard X11 functionality and fails to work properly over remote connections, for this and many other reasons. KDE at least has the excuse that it's based on cross-platform technology, but Gnome is not.

      And sure, let's only allow _one_ application to use the sound device at a time. That really sounds like progress...

      Either Gnome should use a Gnome-independent network audio standard, or it should just leave the mixing to the kernel. There is no need for Gnome to invent and use its own sound daemon.

    11. Re:Ditch the dependencies and deprecated code by Anonymous Coward · · Score: 0
      In its history, Gnome has changed its libraries and subsystems several times, from imlib to gdk-pixbuf, from gnome-canvas to pango, from Corba to Bonobo to possibly Mono, from esd to gstreamer, and so on. Many Gnome apps still use older, deprecated libraries. Get rid of those libraries and port all apps to the standard core API.
      • Pango is used for rendering fonts, gnome-canvas is (as the name suggests) a canvas library. It might be replaced by / ported to Cairo in the future. These have nothing in common.
      • Bonobo is a component system based on corba. Therefore it's built on it, not replacing anything.
      • Esd is not replaced by gstreamer. Gstreamer is not a sound daemon but a framework which could be used to build a sound daemon.
      • The gnome hackers make sure that deprecated libs and APIs are not used in platform and desktop. If applications which are not part of GNOME are using deprecated stuff, GNOME itself can not do much about it.
    12. Re:Ditch the dependencies and deprecated code by BenjyD · · Score: 1

      What is this "Unix" of which you speak. Is that some kind of old-style Linux distro? ;)

    13. Re:Ditch the dependencies and deprecated code by Anonymous Coward · · Score: 0

      The kernel team don't want mixing in their ring 0 code, which means even if it is sneaked past them (as happened with color conversion in early webcam drivers) it will become unmaintained or eventually be thrown out altogether.

      So on Linux the pressure is on ALSA to deliver a reliable implementation of dmix, something that always seems to be just over the horizon (to be fair it's quite hard to get this right). For GNOME, which is cross platform, that's not enough, and they looked to ESD and later gstreamer to fix this.

      Honestly I think the Right Thing(TM) may be JACK plus some utility code in the GNOME libraries that can do simple tricks like "play this ding-noise once" without extra code.

    14. Re:Ditch the dependencies and deprecated code by cortana · · Score: 1

      FYI, if you create a .gtkrc-2.0 then GTK will look there after attempting to load settings from gnome-settings-daemon. A program like gtk-theme-switch2 will do this for you if you don't know how.

    15. Re:Ditch the dependencies and deprecated code by drinkypoo · · Score: 1

      Making daemons optional is really not a reasonable request. Removing deprecated libraries would really solve the problem that there are too many daemons. However, it makes complete sense that all configuration should be done through a daemon so that someday you can store all your configuration in a sql database, or as extended file attributes on a reiserfs system, or what have you. It makes more sense to use the daemons to provide the functionality to all apps in the same way, and to expect all of those apps to use the functionality in the proper way so that they will continue working when gnome is upgraded. Ever notice how some windows 3.1 programs still work properly on Windows NT 5.x? That's because they did what they were supposed to. It can be harder to get good performance, but when the system is upgraded underneath a program, it continues to work and even gains performance improvements.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    16. Re:Ditch the dependencies and deprecated code by Anonymous Coward · · Score: 0

      try static linking all you applications too, you know it makes sense.

    17. Re:Ditch the dependencies and deprecated code by oliverthered · · Score: 1

      it's all part of the Hurd

      --
      thank God the internet isn't a human right.
    18. Re:Ditch the dependencies and deprecated code by oliverthered · · Score: 1

      I have to run 'gnome-settings-daemon' before starting any application such as this for them to look how I want them to look. ... That's the price you have to pay to have everything looking the same.....

      You could always staticly link gnome-settings-daemon to all of your applications and not have to run the deamon, but I think you'll find your systems a lot more bloated.

      --
      thank God the internet isn't a human right.
    19. Re:Ditch the dependencies and deprecated code by TravisWatkins · · Score: 1

      I thought the point of esd and arts was that if you were using a remote X session the sound would come out on the computer you were using, not the one serving up X sessions.

      --

      "But I'm still right here, giving blood and keeping faith. And I'm still right here."
    20. Re:Ditch the dependencies and deprecated code by Sax+Maniac · · Score: 1

      Yeah, the daemon thing bugs the hell out of me. I run KDE, but occasionally use a gnome app, whether on my box or another. I get random gnome daemons stranded all over the network. Remember, this is X, and sometimes we do useful things like run apps on remote boxes.

      KDE seems to know how to start up DCOP and all that stuff, and then blow it away when you're not using it. Not well, but it does.

      The last thing that really drives me nuts is forcing apps and settings to be session specific. Example: I use VNC frequently for work. In the olden days, it was possible to run just sawfish and panel inside a VNC, because I could tell sawfish to do opaque moves and wire-frame resizes. Using VNC remotely over DSL, this is the fastest way to operate.

      Enter metacity. In the name of reducing preferences that people ostensibly don't use, they got rid of the option. Now you only have "reduced resources" which means wire-frame move AND wire-frame resize. BUT: wire-frame move over VNC is slower than opaque move.

      Gee, thanks. Guess I won't use GNOME anymore inside VNC anymore.

      I would like to use GNOME or KDE inside the VNC, rather than yet another environment. After all, I use plently of KDE and GNOME apps.

      On my main desktop, I want all that stuff turned on - font AA, opaque resize, blah blah. But not inside my VNC session.

      Finally, there seems to be no way to have two sets of settings, one stuck to my VNC desktop, and one stuck to my real desktop. Turn off font AA? Well, it's off everywhere. Turn on "reduced" resource? Too bad, it's off everywhere. There seems to be "session managers" and I've tried making a VNC session - but it does nothing. All settings still affect my main desktop too.

      --
      I can explanate how to administrate your network. You must configurate and segmentate it, so it can computate.
    21. Re:Ditch the dependencies and deprecated code by IamTheRealMike · · Score: 1

      As long as it's a GConf only option you could probably write a patch to implement that mode. Or just use Sawfish with GNOME, there's nothing forcing you to use metacity after all.

    22. Re:Ditch the dependencies and deprecated code by Anonymous Coward · · Score: 0

      The kernel team don't want mixing in their ring 0 code, which means even if it is sneaked past them (as happened with color conversion in early webcam drivers) it will become unmaintained or eventually be thrown out altogether.

      Why not? They put in one shitty file system after another, one bogus network protocol after another. Coordinating multiple audio streams is every bit as important for the kernel as coordinating multiple disk I/O operations.

      I think kernel hackers generally have a very limited view of the world and pretty limited experience, which is probably why all of today's major kernels (XP, Linux, OS X) are so bad. But, I suppose, like cleaning toilets, hacking kernels is such lousy and boring work that nobody else wants to do it.

    23. Re:Ditch the dependencies and deprecated code by Ulric · · Score: 1

      Running Gnome inside VNC doesn't seem like a very good idea anyway, but having separate settings for separate desktops (actually displays) is a problem that was solved until KDE and Gnome unsolved it.

    24. Re:Ditch the dependencies and deprecated code by Anonymous Coward · · Score: 0

      Neither Gnome, nor KDE applications should be depending on any desktop-specific userspace demons. Make it possible to deactivate gconf, for example, and have applications read and write configuration files the classical Unix way, by one central switch.

      So each application has to have code that does things two different ways? That doesn't sound like a way to reduce bloat. If you need to start up a daemon, then it's because you need the functionality.

      Make the sound demon optional, so that audio output could just be written (in old-fashioned, non-overlapping way) to /dev/dsp. Etc.etc. The demons might have some use for some people, for for many, they are just bloat and unnecessary complexity.

      A perfect example. If you're going to be outputting sound, then just tell the sound daemon to do it. Your suggestion is "tell the sound daemon to do it if it's running, and have extra code to do what the sound daemon would otherwise do for you, just in case it isn't running".

      Basically, it does the exact opposite of what you want it to. Sure, a daemon is an extra process, but that doesn't intrinsically mean that something is bloated.

    25. Re:Ditch the dependencies and deprecated code by nutshell42 · · Score: 1
      with KDE you can set KDEHOME to the config dir you want to use.

      Simply put a

      export KDEHOME=~/.kde
      in your .xinitrc (or wherever) and a
      export KDEHOME=~/.kde-vnc;
      in your vnc settings before you launch startkde.

      Alternatively you could create a copy your startkde and replace the default dir in the copy (it's around line 50). AFAIK kde doesn't care what the script's called

      --
      Don't think of it as a flame---it's more like an argument that does 3d6 fire damage
    26. Re:Ditch the dependencies and deprecated code by Havoc+Pennington · · Score: 1

      You can't make the daemons optional because the desktop environments are not a set of independent apps, they are a "swarm of processes" that work together. Some of the processes have graphical representations (such as the panel and window manager) and some don't. But all of the processes _do something_, they aren't just sitting there for the hell of it.

      So saying "make the daemons optional" is no different from saying "make the window manager optional" - you have to answer the question "what is going to do the thing that the daemon did"

      What would "make the window manager optional" mean? Either it means you can swap in any WM (as you can), or it means you suck the WM function into an existing process - old WMs like WindowMaker essentially put the whole desktop in one big process.

      In fact, in essence gnome-settings-daemon is a "catch-all" daemon that does a bunch of unrelated/random stuff to avoid having tons of separate daemons. So some of the "sucking the functionality in to a single process" has already been done.

      You refer to gconfd and gnome-settings-daemon specifically I think because those daemons don't have GUIs and thus it isn't user-visible what they do; but that doesn't mean they do nothing. Stuff virtually everyone does care about would break if you removed them.

      For example, the control center will not even think about working with old-type UNIX config files, because when the control center changed a setting the rest of the desktop would not know about the change. In most cases this would mean the change would not take effect. In KDE this is addressed through the dcop daemon rather than a special config daemon, but there's still a need for a daemon here.

      gconfd also keeps a shared cache of all the settings, so guess what... it *reduces* memory usage overall.

      The desktop need not be implemented in this "swarm of processes" way - desktops as diverse as Enlightenment and Lotus Workplace use a single-process approach. But there are advantages to multiple processes.

    27. Re:Ditch the dependencies and deprecated code by Curtman · · Score: 1

      Either Gnome should use a Gnome-independent network audio standard, or it should just leave the mixing to the kernel. There is no need for Gnome to invent and use its own sound daemon.

      Are you referring to esound when you say 'invent and use its own sound daemon'? That's exactly what the KDE crew did with artsd though.

  34. While they are at it ... by Alain+Williams · · Score: 4, Interesting
    fix some of the startup slowness. Have you ever done strace on a gnome app ? Did you ever see it open and read the same file again & again ? It might cost a little RAM to cache the results but should be worth it - most of these files are quite small. How about reading into a per user shared memory segment - just read once and share between all processes.

    The best way of ensuring that it stays fixed is to give all the gnome developers PIIIs with 128 Mb RAM.

    1. Re:While they are at it ... by Anonymous Coward · · Score: 0

      if you have enough memory linux will just cache a file that gets read over and over.

    2. Re:While they are at it ... by Anonymous Coward · · Score: 0

      Should I read "+5 Interesting" as "has no idea how operating systems work"? Hint: every time you open a file, the kernel CACHES the contents of that file. Thus, when any other process tries to open that same file, no I/O happens.

    3. Re:While they are at it ... by Lispy · · Score: 2, Funny

      Yeah, give them pills instead of bounty. ;)

    4. Re:While they are at it ... by Jeffrey+Baker · · Score: 2, Informative

      It is still costly to enter all those syscalls. You don't have to read the data from disk, but you do enter the kernel again and again. Once I looked at an strace of "yelp", the GNOME help program, and for a list of several tens of thousands of files, it would stat, open, mmap, and close each file 5-10 times. It was horribly bad, even with all the data already in core. In fact it was faster to start Mozilla than to start yelp.

    5. Re:While they are at it ... by cynyr · · Score: 1

      i think it should be a 386 with maybe 1MB ram
      that should fix all of that.

      --
      All of the above was encrypted with a Quad ROT-13 method. Unauthorized decryption is in violation of the DMCA.
  35. Remember... by CrackedButter · · Score: 1

    NO disintegrations.

  36. Yup, Eugenia from OSnews by sonamchauhan · · Score: 1

    Yup, it's her. I found out by clicking the link on her name in the story.

    1. Re:Yup, Eugenia from OSnews by hitmark · · Score: 1

      heh, i looked at that link to but could not find any reference to osnews, but it looked like the same person given the interest in beos :P

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
  37. -1, Not Sufficient Geeky by ggvaidya · · Score: 4, Funny

    In The Hobbit, gnomes were used to refer to the Noldor, but Tolkein changed that because of the stereotype gnome being short-and-fat and very unelvish (in the Tolkein universe). An overweight Noldor would look a lot like an overweight human. And, if the movies are to be believed, very gay, but I'm not buying that ...

    1. Re:-1, Not Sufficient Geeky by Anonymous Coward · · Score: 0

      Come on, fantasy elves have been known to be gay by anyone with eyes since their inception. How else do you think they manage to live thousands of years without overpopulation problems? In fact, Tolkien's elves are clearly stated to be diminishing in number! That's a serious number of non-heterosexuals right there... I suspect the elves only manage to make kids when they are young and still experimenting with their sexuality, which is when some of the sexually more imaginative elves figure out that males and females actually have physically compatible equipment. Not that I have spent much time thinking about this.

  38. Re:Need sex? by aneroid · · Score: 0, Offtopic

    hi Mike

    or is it Pixel...?

  39. Re:horrible idea by stevesliva · · Score: 1
    can't we think of other ways to motivate people besides money?
    Economists have been working on that very problem for centuries. They have not yet come up with a better way to motivate people.

    Forgive the sarcasm, but what's a better motivater than cash? A job that pays cash? Threatening developers with death?

    --
    Who do you get to be an expert to tell you something's not obvious? The least insightful person you can find? -J Roberts
  40. KDE has been doing this since day one by AntiOrganic · · Score: 4, Insightful

    While they've still got a long way to go, each successive release of KDE is substantially improved in terms of required CPU power and memory usage. KDE 3 ran a great deal faster than KDE 2 despite all sorts of added functionality, and KDE 3.4 RC1 is the fastest yet by a pretty big margin. The upcoming Qt 4 has a whole slew of performance improvements which should reduce requirements further.

    1. Re:KDE has been doing this since day one by Masq666 · · Score: 1

      Guess i'll have to update my KDE. KDE has done a good job optimizing but there's allways room for more. As long as they keep up the great work i'm happy.

      --
      Bits of News Giving you the latest bits.
    2. Re:KDE has been doing this since day one by WMD_88 · · Score: 1
      Argh.

      KDE fans always talk about how the team is optimizing it all the time. While I don't doubt that *something* is being done, in my own tests, there is contrary performance.

      Let's take the P1s I've run KDE on - a p1/133 with 40MB ram, and a p1/166 with 32MB ram. Both are low-end machines without a doubt. (And the one with less ram had a brand new hard drive.) One machine ran KDE 1.1, and the other ran 3.1.4.

      In short, 1.1 was moderately fast, but 3.1.4 was so slow that it'd be unusable to the average person (I have a lot of computer patience myself). I'd say the difference was around twofold faster for 1.1.

      Perhaps it's not the KDE team's goal to run on 32 or 40MB machines. Which I guess is okay - anyone running Linux on one of them is probably using Fluxbox or something. But still, the performance between old and new went way down - which it shouldn't if any optimization is taking place. (And I hardly believe that the extra 8MB ram given to 1.1 helped it *that* much.)

    3. Re:KDE has been doing this since day one by m50d · · Score: 1

      That's a 20% upgrade there, equivalent to probably 100mb on a modern system, and if it makes the difference between all the kde libs being able to fit into core and not, then it could easily give a 2x speedup. Anyway, there are many many more features in 3.x, but you at least get more "value for money" in terms of features/performance. It's being optimized but they are also adding more features.

      --
      I am trolling
    4. Re:KDE has been doing this since day one by WMD_88 · · Score: 1

      if it makes the difference between all the kde libs being able to fit into core and not, then it could easily give a 2x speedup.
      I've checked top. The machine was still swapping, abeit less than the 3.1 machine. So no, not everything fit into RAM.

    5. Re:KDE has been doing this since day one by evilviper · · Score: 1
      each successive release of KDE is substantially improved in terms of required CPU power and memory usage.

      Not true at all... Sure, KDE3 was a HUGE improvement over KDE2, but that's only because KDE2 was such a dog. KDE1 can smoke KDE2 any day, and I'm willing to bet it's still faster than KDE3, despite not getting the new optimizations.

      Now, I'm not trying to devalue the improvements made to KDE, just your own personal BS benchmark... KDE2 set the bar very low, so, of course, successive releases would be faster.

      If early versions of GNOME had been incredibly slow, they would have been speeding-up successively since then. Instead, GNOME started off with decent performance, so it couldn't possibly have kept improving by leaps and bounds. It's certainly bloated now, but that's besides the point.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    6. Re:KDE has been doing this since day one by Anonymous Coward · · Score: 0

      >In short, 1.1 was moderately fast, but 3.1.4 was so
      >slow that it'd be unusable to the average person

      Yes, 3.1 was *very* slow. But it is also two years old, and a *lot* of things happened since then... Give the new 3.4 a try: I bet you won't be disappointed nor by its speed nor by its features ;)

    7. Re:KDE has been doing this since day one by AntiOrganic · · Score: 1

      This is true, of course, but it does not in any way change the fact that KDE is steadily improving performance-wise regardless.

    8. Re:KDE has been doing this since day one by Anonymous Coward · · Score: 0

      In all fairness so has Gnome. It's gone from unusable on my 533 Celeron (really, Nautilus looked great but was uselessly slow), to *snappy* on the same hardware.

      The improvements were such that FC3 on my 533 Celeron (256 MB RAM) felt much snappier than FC1 on my 1.8 Ghz (512 MB RAM) machine at work. It's almost frustrating to use the work machine after using the newer gnome on my home abacus.

      The newest version of Nautilus is a snappy speed demon, and has been fast and light for a while now.

      That's impressive, and it just seems to keep getting better/faster with every release.

    9. Re:KDE has been doing this since day one by m50d · · Score: 1

      Yeah, but if it's the difference between having to swap parts of the libs and only having to swap the apps, that's going to make a big difference. Not that I'm saying 3.1 doesn't need more power than 1.x, it may well do, but at that little ram you really need to compare on the same machine.

      --
      I am trolling
  41. Pay Peanuts, Get Monkeys - Catch Fleas by Doc+Ruby · · Score: 4, Insightful

    The bounties Novell is offering are too low. They're offering $1-200 for tasks that will take an adequately skilled programmer, already familiar with GNOME, something like 2-4h to complete, including the docs that will let GNOME integrate the code (which will help win the bounty). The programmer doesn't need to spend time testing the code, though that will increase their chances of winning. So they're offering $50:h.

    That isn't enough to support a community of coders, even if the range of bounties were scaled up to supply a significant headcount with enough work to keep busy (say, 500-1000 bounties a year). The labor might be fueled by people who are coding GNOME anyway, to prioritize completion/submission of some tasks. But the better, even more productive coders won't be available at those rates. It remains to be seen whether a multitude of mediocre submissions can compensate for too-cheap bounties that can't attract quality coders. Or perhaps this model will merely send all coding offshore, to programmers who can work so cheap that a single $100 bounty won can fund a month of unsuccessful submissions to other bounties they lose.

    --

    --
    make install -not war

    1. Re:Pay Peanuts, Get Monkeys - Catch Fleas by Anonymous Coward · · Score: 0

      You're kidding right? That would be a raise for me. I've been writing software for five years for about $15 an hour. I'd feel filthy rich getting paid $50 an hour.

    2. Re:Pay Peanuts, Get Monkeys - Catch Fleas by XO · · Score: 1

      It'll take me longer just to install GNOME and get it working, on my P3/600 with 128MB RAM than it will for some of these things to get fixed.

      And to install the entire development trees and actually do a compile? Ludicrous. heh.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    3. Re:Pay Peanuts, Get Monkeys - Catch Fleas by Doc+Ruby · · Score: 1

      1000 bounties per year, at $150 per bounty, is $150,000 per year. That would feed 5 programmers at your $30,000 per year income, doing about 2500 hours of work. Which is almost right: A 40 hour week is a 2080 hour year, and programmers always do at least 10% paid overtime every year (though 2500:2080 is 20%). But what about all the losers? Every loser who submits to the bounty is another multiple, another fraction of the pie lost that leaves the loser hungry.

      And how good is your code, that you can't compete with people getting more than $15 per hour, though you've got at least 5 years experience? Can it win? If it can, do I want to use it daily in my desktop, for these hidden critical-path operations? And what about the overhead of work to participate in the contest, and the overhead of programming on a series of disconnected, specific tasks within the huge, complex GNOME system?

      --

      --
      make install -not war

    4. Re:Pay Peanuts, Get Monkeys - Catch Fleas by Doc+Ruby · · Score: 1

      I think this would work only for people "already doing it", to prioritize submission of these patches to Novell. For a GNOME-dev beginner, just finding/reading/reconciling their poorly documented code and specs will take over an hour, just to get started on one of these highly specific tasks. But if you've got to decide whether to start a new GNOME SourceForge project that will die in "pre-Alpha", or complete one of these useful patches, that $100 might decide you. And that will at least create a larger labor pool submitting patches, from which one might be acceptable for finishing that GNOME task.

      --

      --
      make install -not war

    5. Re:Pay Peanuts, Get Monkeys - Catch Fleas by Anonymous Coward · · Score: 0

      But say you have only have a 10% chance to win, then you are only getting $5/hour.

    6. Re:Pay Peanuts, Get Monkeys - Catch Fleas by Rahga · · Score: 1

      Doc: The only problem with theme is that they really quite a lot longer to do properly than 4 hours. Conceptually, it's easy. I could tell you how to fix the background bounty as well as include proper SVG background support in Nautilus, but implementation is where all the time will be wasted... Making sure there's no regressions and all the bases are covered. Heck, I fear how many days an average GNOME hacker might spend just getting familiar with eel before fixing this....

    7. Re:Pay Peanuts, Get Monkeys - Catch Fleas by Doc+Ruby · · Score: 1

      That's what I meant by "a single $100 bounty won can fund a month of unsuccessful submissions", for some people.

      --

      --
      make install -not war

    8. Re:Pay Peanuts, Get Monkeys - Catch Fleas by Doc+Ruby · · Score: 1

      Maybe limited success with the bounties will get Novell to invest in producing a much more productive theme system. Or other tools to contribute code/content to their system. Automating lots of these code submission systems more than just cvs, especially in documenting APIs, would make this system more reliable for production schedules. And generally improve the code available for all open source projects. SourceForge was a big step. But I'd love Novell to roll out some kind of Open-Xchange platform for development collaboration that could manage the distributed coding model they're indulging with these bounties.

      --

      --
      make install -not war

    9. Re:Pay Peanuts, Get Monkeys - Catch Fleas by xenocide2 · · Score: 1

      Think of it as a fairly cheap recruiting campaign. Maybe the bounty isn't all that great, nor the bug more than trivial, but you've likely found two or three guys who are knowledgable enough to install, run, compile, debug, fix, and submit patches for your software. Exactly the kind of employee you're looking for. And even if Novell isn't taking it like that, somebody probably should be.

      --
      I Browse at +4 Flamebait

      Open Source Sysadmin

    10. Re:Pay Peanuts, Get Monkeys - Catch Fleas by XO · · Score: 1

      not to even get into comprehending the ties to the other pieces of software

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
  42. Good luck! by daVinci1980 · · Score: 4, Interesting

    Seriously... I've spent a very significant amount of time optimizing four shipped titles now--mostly games, one commercial shrinkwrap application--for both speed and size tradeoffs.

    The big annoying thing with optimization is that assuming you are working with talented people (I believe the people who work on GNOME are talented), there is generally little low-hanging fruit. An example of low hanging fruit is places where you are using--for example--a vector, but you should be using a map or a hash table. Another example is places where complex code can be skipped over by checking some preconditions and bailing early.

    Although premature optimization is the root of all evil, most of us recognize these sorts of places early, and do the relevant optimization work in the first place. What you're left with in terms of optimizations is places where your initial architecture is *just wrong.* This kind of performance / memory deficiency really sucks, because most of the time the code is too complex and there are too many other dependent pieces of code to do the necessary rewrite.

    The other thing that makes optimization work hard is (lack of) tools. There are basically two types of problems you can optimize: speed and size. Sometimes you get lucky, and fixing size problems *also* increase speed (generally because your smaller code now fits in the instruction cache, or because your data memory fits in the L1 or L2), but that is usually the exception. With size problems, the best bet is usually to make all objects pooled individually. This allows you to dump out information during the program run as to how many objects you've allocated of a particular class, as well as how much memory they're taking up.

    With speed concerns, it's a little more difficult. There are basically two types of speed problems. Problems that occur constantly, and problems that occur as a result of user interaction or are themselves cyclical. Effectively it's a matter of identifying spikes versus identifying plateaus. Plateuas are the easier of the two, because they are identifiable via tools like Intel's VTune (which has been--I believe--ported to Linux by Intel). But spikes are harder, in that identifying them requires code instrumentation, and although there are some suites that will do it automatically, they often over instrument places which lead to artificial spiking.

    Anyhoo, sorry for rambling... optimization is something very near and dear to my heart.

    --
    I currently have no clever signature witicism to add here.
    1. Re:Good luck! by rbarreira · · Score: 1

      In my opinion, any decent programmer likes optimizing. It's just fun! So congratulations :)

      --

      The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
  43. Re:horrible idea by dont_think_twice · · Score: 5, Insightful

    I think this is a horrible idea. When you have to offer bounties to encourage people to alter open source, then you're basically hiring and paying programmers...Open source isn't about hiring and paying people, it's about everyone working together to make better software for themselves.

    I think you are confusing Open Source Software and Ken Kesey's Magic School Bus. One solution to this problem is for your to do way less drugs.

  44. Lies by Anonymous Coward · · Score: 1, Funny

    > Yeah, because GNOME is only developed by volunteer
    > hermits living in caves at the moment. It's not
    > like there are big companies paying developers'
    > salaries to work on it or anything.

    GNOME isn't developed by hermits. Let's clear this up:
    * GNOME is obviously developed by Gnomes (duh) and Simians
    * KDE is obviously developed by Trolls (and Dragons)
    * BeOS is obviously developed by colonial insects
    * GNUstep is obviously developed by Dancing GNUs
    * OS X is obviously developed by the porn industry

    And BTW, gnomes don't need no stinkin salaries. Just give them enough underwear and a TV to watch South Park and they'll be happy.

  45. open source IS about hiring and paying people by idlake · · Score: 1

    Open source isn't about hiring and paying people, it's about everyone working together to make better software for themselves

    Most open source programmers are employed and get paid to do open source programming.

    Open source isn't about some utopian, socialist community, it's about companies paying in order to develop software for their own benefit. Open source is a more efficient free market alternative to big software companies.

    To put it more bluntly, you can hire a lot of well-paid programmers with the money people spend on Windows licenses--a lot more than the number Microsoft hires from their revenue.

    1. Re:open source IS about hiring and paying people by XO · · Score: 1

      What?

      Are?

      You?

      Smoking?

      I doubt there's any way to do a survey to check this, but I'd be willing to lay odds that the ratio of People who Do This For Fun, and People Who Do This As Their Job are better than 1000:1.. Just the people who do this as their job, are the ones doing the most visible and active projects.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    2. Re:open source IS about hiring and paying people by idlake · · Score: 1

      There is a way to check this: you do look at the important and successful projects, and you do look at what people do for a living. And you will find that they are usually employed by some employer that has an active interest in the open source projects they are working on (this includes university students, where it is part of education--also, in a sense, job related).

      In fact, if you are in the US and working anywhere in the computer industry or academia, you usually cannot work on open source projects without your employer's permission because otherwise they would own everything you do.

  46. Re:Need sex? by Anonymous Coward · · Score: 0

    Pixel broke 5 keyboards with her hooves. No net for her now.

  47. Re:horrible idea by Anonymous Coward · · Score: 0

    (Score: -1, Doesn't Understand OSS)

    Perhaps you've been bitch slapped enough by now, but someone who just found /. a couple years ago doesn't need to come around telling *US* what open source is about. That took serious cajones. Especially when you come to find out that you are the one who doesn't understand it.

    OSS was licensed that way so that no one entity can maintain total control over a single piece of software and control its distribution. There's no mention of money. In fact, some of its roots come from the socialist concept of everyone having a job. If companies don't have to buy ridiculously expensive computers anymore and all the software is free (like it was in the old days), then that leaves more money to pay support personnel and developers to support and customize the software.

    No more funneling hundreds of thousands of dollars per year to Sun, IBM or Microsoft just for the right to get fixes and updates.

    Get it now? Cheap hardware. Good, free software with no restrictions on modifications and distribution. More buckage to keep people employed customizing the software and supporting the users. Maybe even selling their customized versions to other companies!

    Now, go read CATB newbie.

  48. The intobk_open call by Anonymous Coward · · Score: 0

    The biggest memory problem with GNOME is it's overly heavily reliance on the intobk_open library function. If you're looking for low hanging fruit, then that's it. I suggest creating a wrapper and then replacing this call entirely.

    There, now what do I win?

  49. How can Gnome be bloated? by Anonymous Coward · · Score: 0

    Its an Open Source project, so any bloat would be removed by the 'many eyes' principle? Or am I missing the point here? I use Open Source software precicely because its not bloated and bug-ridden like Micro$oft. Are you saying I'm labouring under a misapprehension?

    1. Re:How can Gnome be bloated? by bhalo05 · · Score: 1

      Of course. In real life, things are not so simple. But at least is Free Software, given enough time and resources things can be improved by anyone. Don't expect miracles though.

    2. Re:How can Gnome be bloated? by Ulric · · Score: 1

      No, the bloat has been increased by the "many monkeys with typewriters" principle.

  50. Re:horrible idea by Anonymous Coward · · Score: 0

    There is nothing about open source that is against paying people to program. It is about getting as many people to contribute as possible.

    If you can get people to contribute to free software by lighting your farts on PBS, that's just one more for us.

  51. Re:horrible idea by G-Licious! · · Score: 1

    Robert Love (inotify fellow) is a Novell employee, IIRC.

  52. Re:cat Gnome /dev/null by Anonymous Coward · · Score: 1, Funny

    Isn't that the Gnome2.x manual?

    You mean the gnome project aims for people not unix-knowledgeable to use a GUI? The horror!

  53. Re:The best way to improve Gnome... by X0563511 · · Score: 1

    Fluxbox.

    It runs KDE programs, i _think_ it runs Gnome applications as well. It's simple, powerful, SMALL, and FAST.

    And, it plays nicely if you put it on with KDE and/or gnome at the same time. You don't like it? Take it off without hurting what you already had on.

    --
    For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
  54. These bounties are not payment, they're prizes by Anonymous Coward · · Score: 0

    If you read the comments from Ben Maue (the bounty poster) (see http://osnews.com/comment.php?news_id=9889), you'll see the the bounties aren't for paid work. They're just prizes.

    Essentially, he's saying, if you want to contribute to GNOME in your spare time then it's better to work on these projects (which you'll get some recognition and a small prize) than another place (which won't get you as much recognition and their are no cash prizes).

    In the end it's all free software so you get to keep what you produce and if you use GNOME, it gives you a sense of pride to contribute and be recognized.

    As a side note, have you seen how little bountied software makers are getting (e.g. www.rentacoder.com)? You get low pay and even after you produce your code, if you're not quicker than someone else and no willing to get less pay than someone else, you will still lose out. There's an enormous risk in time and effort for little reward. IMO, I doubt anyone can make a decent living off of bounties.

    1. Re:These bounties are not payment, they're prizes by Doc+Ruby · · Score: 1

      Well, he can call the compensation whatever he wants. I'm sure Novell also pays lots of fulltime onsite "contractors", avoiding taxes and benefits obligations, like any other large American corporation. But it's still payment for work.

      As we agree, it's not enough to support a person's own economics, unless perhaps they live somewhere that programmers are willing to make about $1200:y. Or they're getting paid by someone else (perhaps their own project). It's really just a bounty to prioritize the patches that are submitted to GNOME, rather than languishing (perhaps unfinished) in someone's inbox or source directory.

      --

      --
      make install -not war

  55. Re:horrible idea by bhalo05 · · Score: 1

    Perhaps you've been bitch slapped enough by now, but someone who just found /. a couple years ago doesn't need to come around telling *US* what open source is about. That took serious cajones. It's spelled 'cojones' ;)

    BTW, I agree with you.

  56. Are you kidding me? by Inoshiro · · Score: 2, Interesting

    When you're like me, working through Univursity to pay for a computer science degree that's being paid concurrently, these are great. Rather than going to a soul killing job that has no relevance to my course of studies, but happens to pay me money, I can just do a mod to Gnome (which is relevant to my studies), and get paid 10 times my soul-sucking hourly rate.

    This isn't for people who have jobs which pay them so much money they can have sexy-parties with hookers and blow every Tuesday, this is for people who need a little financial incentive to do it, or for people who aren't established and want to make some money while they're making their name. Obviously you're a hookers and blow kind of guy, so maybe you shouldn't send in any patches.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
    1. Re:Are you kidding me? by Doc+Ruby · · Score: 0, Troll

      How much have you made from these bounties, in competition with all the other university-chained programmers submitting? When you get out of the dorms and cafeterias, you'll find that it takes a lot more than $1000 a year to support hookers and blow. BTW, our before-hookers-and-blow taxes are subsidizing the loans and grants that enable the finance of your education and subsistence. You'll appreciate the irony when you're dropping over $300 out of that $1000 to pay them yourself.

      --

      --
      make install -not war

    2. Re:Are you kidding me? by Anonymous Coward · · Score: 0

      Hey, you started out in this discussion saying it was giving $50 an hour. Now you're saying that works out at $1,000 a year. If you're only working 20 hours a year then what do you expect?

    3. Re:Are you kidding me? by Doc+Ruby · · Score: 1

      I posted "they're offering $50:h", and also that a contestant could probably expect $1000:y. The "discrepancy" comes because it's a contest, with multiple applicants. The format lets Novell pay a capped amount, while applicants work with a lower probability of getting paid. If you don't consider the waste and competition, making the single payout different from the share of total income, what do you expect?

      --

      --
      make install -not war

    4. Re:Are you kidding me? by Doc+Ruby · · Score: 1

      Moderation -1
      100% Troll

      I guess it's dangerous to taunt people who can't get decent programming jobs with visions of cocaine and hookers. Because they have lots of Slashdot time on their hands, and become enraged TrollMods at the very idea.

      --

      --
      make install -not war

  57. Re:cat Gnome /dev/null by InfiniteWisdom · · Score: 1

    That accomplishes exactly nothing. cat /dev/null > gnome, perhaps

  58. mega crap by Anonymous Coward · · Score: 0

    the real problem of gnome is a inutle file manager
    like nautilus....
    i suggest a bounty to replace it.

  59. Bloat? by Anonymous Coward · · Score: 0

    Ha ha ha! I thought Microsoft products were the only products with bloat. What next a Knoppix dist. that goes over 2 cds?

  60. Re:horrible idea by Nikker · · Score: 1

    I think what this will do is take the script kiddies that just talk and make them actually do it. Once they get that confidence that add to the people who code for OSS. Some will contribute for money only, others will contribute for reputation.

    The best thing maintainers can do is make sure people can attain a rep, this way it will work better than money in most circles.

    --
    A loop, by its nature, continues. If that didn't make sense, start reading this sentence again.
  61. Stop these posts, your code already exists by Ars-Fartsica · · Score: 1

    If you insist on running five year old hardware, just run ten year old code on it (early fvwm, xterm, xclock, etc) and go your way. There isn't going to be a version of GNOME or KDE optimized for Pentium systems with 64MB of RAM. EVER. So stop waiting for it. If you can't afford $400 for a new P4 system, you're on your own.

    1. Re:Stop these posts, your code already exists by Anonymous Coward · · Score: 0

      If you can't afford $400 for a new P4 system, you're on your own.

      We accuse MS of being in bed with Intel for less.

    2. Re:Stop these posts, your code already exists by Anonymous Coward · · Score: 0

      Blam! And there you have it: why Linux still only has 5% of the desktop after, what, nearly 15 years? Over 20 including GNU...

      What a terrible, terrible attitude. "Free Software, all about freedom and choice - oh BTW you must not insist on running hardware a few years old or we'll sneer and tell you to run bloody fluxbox and xclock."

      Great. Absolutely great. You carry on - you're just removing another incentive to switch from Microsoft!

    3. Re:Stop these posts, your code already exists by Anonymous Coward · · Score: 0

      well he won't be running xp or any other new ms code either, so whats your point? the free software world gives him dozens of choices - from lynx on the terminal to icewm to blackbox to fvwm to xfce to even gnome1 (i am sure someone is maintaining a tarball of it). is it so much to ask that we have a measly two environments (gnome2, kde3) for people with recent hardware???? in fact more than 80% of the window managers on xwinman advertise being "light", so when you buy a clue you'll realize this person has plenty of options.

  62. Next Bounties-Cheap Love. by Anonymous Coward · · Score: 0

    "And the next set of bounties will be offered for cleaning up bugs introduced by rapidly encouraging people motivated only by money to make changes to Gnome without fully considering the ramifications of these memory reductions. :-)"

    It all wouldn't be necessary if all those motivated by "LOVE" didn't bloat it to begin with.

  63. Re:horrible idea by Anonymous Coward · · Score: 0
    but can't we think of other ways to motivate people besides money?

    Beach vacations to the Carribean? Whores offering blowjobs? Then again, money can translate to any of these things so why not just fork over money?

  64. what a shame by Anonymous Coward · · Score: 0

    From bounties site:
    "Create a test suite for browsing in Nautilus"

    hey are you crazy ?
    this bounty is so bored

  65. Microsoft should take the idea too by TPoise · · Score: 1
    Just imagine if Microsoft just went across the board to all their application programmers and said "Hey, here's a $3000 bonus on your next paycheck if you can take time to reduce bloatage in WinXP or Office ". I would then think the world would be a better place.

    In all fairness, GNOME has a long way to go to reduce the bloat, but I wish them all the very best.

    Firefox could use the treatment too. This would be great if there could be some kind of metric available for the FireFox team. E.G., "Here FireFox with 3 tabs open only uses 300KB of RAM, while IE uses 30MB of RAM".

    1. Re:Microsoft should take the idea too by Ian.Waring · · Score: 1

      I seem to recall that the performance of VMS on small memory systems progressed leaps and bounds when a few hundred people at Spit Brook (VMS Engineering) got shiney new VAXstation 2000's on each of their desks with minimum memory only. It went from dog to decent performance in very short order.

  66. Open Source Bloat-Chasing Microsoft Users. by Anonymous Coward · · Score: 0

    "Open Source used to be pretty good at reducing bloat, but nowadays..."

    The price to beating Microsoft.

  67. Additive bounties by theantix · · Score: 4, Interesting

    What I would like to see is the ability for me as a user to add to the existing bounties and start new ones of my own. I would like to be able to propose a bounty and send money to a reputable bounty clearinghouse like at Novell or Ubuntu, and then they could offer the bounty as if it was their own since they have my cash until the bounty expires or is completed. And then while the bounty is still up for grabs I would like to be able to send the clearinghouse money to add to the existing bounties in order to make them more lucrative to potential hackers.

    I could setup this site right now fairly easily, but people wouldn't trust my joe random site as well as they would trust a bigger and more established organization like Novell or Ubuntu/Canonical. But I can't be the only one looking to put my money where my mouth is, so why does this functionality not exist?

    --
    501 Not Implemented
  68. Re:horrible idea by Anonymous Coward · · Score: 0

    There's people on OSDL's, Redhat's, Novell's, Intel's, AMD's, HP's, SGI's, IBM's, Cyclade's, Montavista's, NSA's (yes, really), etc, payroll working on the Linux kernel. Even Sun's (Mike Waychison, for example), or Dell's (Matt Domsch).

    Linux is not a hobby anymore, long are the times it was developped by a handful of heremit-type hackers. It's move on to the professiona world, where lots of people are being paid big bucks to make it happen.

  69. I like the idea by hsoft · · Score: 3, Insightful

    Sourceforge should extend it's donation system and create a bounty system. When you donate money to a project's bounty system, you get a vote for each dollar you give. People submit for the bounty, and then, you can vote for who will get the coding contract.

    --
    perception is reality
  70. Re:horrible idea by Anonymous Coward · · Score: 0

    Watch the hacking scene in the movie Swordfish for the best motivator a hacker could ever want.

  71. Re:horrible idea by Anonymous Coward · · Score: 0

    Forgive the sarcasm, but what's a better motivater than cash?

    Eternal life, perpetual youth, perfect health, godlike power.

  72. Some are fixed, yet bounty not paid by Anonymous Coward · · Score: 2, Interesting

    I just took a scan through all the bounties listed at the link and noticed a few things:
    1) Many of the bounties are already fixed
    2) The fixed bounties still haven't been claimed or paid after more than a year in some cases.
    3) The bounty hunters all start early on the bounties, but then no progress for months while people wonder if it's being worked on.
    4) Sometimes a patch is submitted, but it never gets applied by the coordinators.
    5) It's very collaborative. Many are just a long thread of incomplete fixes that go on for years.
    6) The patches often get lost after the original author gives up to it not being included after a period of months/years.
    7) Changes often impact other projects, whose maintainers may not want thier project patched.

    Frankly, I'm amazed that in some cases it takes 2 years to fix and patch a simple bug. Meanwhile, the source tree is changed, rendering the original patch unusable. Don't tell me how I should contribute to improve it. I was thinking about doing just that until I came to the realization of how horribly inefficient the whole process is. If I fix a bug, I don't want to wait 2 years, if ever, to get paid thank you.

  73. mod up please by Anonymous Coward · · Score: 0

    thanks, the grandparent poster really has no clue what he's talking about, but thats never stopped mod's from pushing him up in the ratings. lameness.

  74. Novell and GNOME by CarpetShark · · Score: 1

    Well, the thing is that parts of Novell DEPEND on GNOME, since they now develop evolution etc. SuSE might use KDE, but not in such a core-business way. Personally, though, I wouldn't be investing in GNOME these days. Seems like it's going downhill to me, while KDE is improving in leaps and bounds.

  75. You must be a yank. by Inoshiro · · Score: 1

    I have no problem subsidizing education, much like I have no problem subsidizing universal health care. Ooh, some money I don't really need is lopped off my paycheque. Big deal. There are larger things than what you take home every pay period affecting the country.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
    1. Re:You must be a yank. by Doc+Ruby · · Score: 1

      I have no problem subsidizing education, or health care. I lived and worked in Canada, and was happy to keep the quality of Canadians high, through the taxes my entrepreneurship paid - it was coming back to me in the quality Canadians upon whom my income depended. Those are two of the best investments people can make in our communities, in terms of return on investment. I do have a problem with people ignoring how subsidy investments depend on those who have capitalized on their own round, to create the surplus on which those subsidies depend. Especially when those ignoring the subsidy system talk about subsidizing it, when they actually don't - because they're net recipients.

      --

      --
      make install -not war

  76. If gnome really wants to reduce bloat by Anonymous Coward · · Score: 1, Insightful

    If gnome really wants to reduce bloat they should consider moving back to gnome office from OO.o

  77. Too much WoW by Johnny+Mnemonic · · Score: 1


    You know you've been playing too much World of Warcraft when you look at the headline and start thinking up ways to min/max the gnome character, and how to spend the money from the bounty for doing so...

    --

    --
    $tar -xvf .sig.tar
  78. My question is.... by p.rican · · Score: 1
    what type/specs are the machines most developers use to crank out code. I'm not a programmer but if they're creating code on a dual processor system with 512 MB RAM FSB ~800MHz, is that going to affect how well the software will perfom on my AMD 850?

    It would seem to me that you would want your development machine to have low end specs so you can get a better feel for how the software will perform on the majority of older PCs out there?

    I hope that made sense.

    --

    /. --"Demented and sad....but social" -Judd Nelson

  79. speed matters by mnemonic_ · · Score: 1

    I hate to say it, but the slow GUI speed is why I don't enjoy using Linux. Even xfce4 is slower than Windows XP, which is ridiculous. Gnome used to be my favorite environment (it's by far the easiest to use), but I got fed up by the sluggishness. I hope this project can bring me back to GNOME.

  80. Re:FUD by iamwahoo2 · · Score: 1
    These days you can choose from either QPL or GPL licensed Qt.

    "I am very pleased to see that Qt is now available under the GPL," said Richard Stallman, President of the Free Software Foundation. "This is a big win for free software and a great gift from Trolltech to the community."
  81. Re:The best way to improve Gnome... by Anonymous Coward · · Score: 1, Informative

    you sir, are a complete idiot. Fluxbox is a window manager it doesn't run anything. KDE / Gnome applications are just applications that use KDE / Gnome libraries, and so will run in any X environment, or linux framebuffer environment depending on the backend they use.

  82. ummm... by Bontux · · Score: 0, Offtopic

    ... nevermind, I can't remember what I say.

    --
    I stole this signature
  83. A head start by Anonymous Coward · · Score: 0

    Here, I'll give someone a head start. I'm busy with my daughter right now but need week I'm going to dig deeper with dtrace!

  84. omg, pseudo nerd, eugenia, jerk, world hates usa. by Anonymous Coward · · Score: 0

    "128 MBs of RAM (very usual configuration in developing countries or even European businesses)"

    OMG! This pseudo nerd Eugenia is such a jerk.
    .oO(That's why the whole world hates you americans.)

  85. How? by Luke-Jr · · Score: 1

    How do you pull this off? I've got two systems running KDE 3.4...
    The first one (running 3.4 final) has 1 GB of physical RAM. There is never a time when KDE is running that it isn't using at least 1.5 GB of RAM (including swap, discluding cache).
    The other one (running 3.4 rc1) has 256 MB of physical RAM. It is almost consistently maxing out while care is taken to be running only the minimum services/programs.

    So... how did you get KDE working properly with a mere 128 MB of RAM?

    --
    Luke-Jr
    1. Re:How? by Klivian · · Score: 1

      It does work without problems on 128MB ram, you don't have to do anything really. Perhaps increase with 256MB swap just to be safe for those corner cases:-) The thing is how Linux tend to fill up the memory, it is just lazy in reclaiming it that's why it is consistently maxing out. I used 128MB for years whitout any problems, it almost always was at 98% plus 64MB or more in swap. But you don't notice any performance loss when running, you can try it yourself and see. Perhaps the only way you'll get convinced(Use the mem option when booting). Only slowing you will see is in app start-up since you don't have so large disk cache, but it's about working not starting and stopping applications. As a curiosity, I for a time used 48MB to run a machine with KDE2.2. It was ok, as long as you didn't open too many apps, more than 5 Konqueror windows and it started swapping like mad:-)

    2. Re:How? by Espectr0 · · Score: 1

      So... how did you get KDE working properly with a mere 128 MB of RAM?

      You have to remember that no matter how much ram you have, linux uses as much as it can.

      One person said to me "in linux, unused ram is wasted ram".

      Sure it boots slow but it is usable for browsing and such, and if you have patience, maybe openoffice

    3. Re:How? by Anonymous Coward · · Score: 0

      kde 3.4 final has not been released yet

      My gentoo-kde 3.3.2 just started, autostart programs closed, use 150mb ram, without filesystem cache

    4. Re:How? by Luke-Jr · · Score: 1

      Maybe not released, but I'm pretty sure it's tagged... and I'm relatively sure my last checkout was either right before or after the tagging, so if it's not final, it's certainly close.

      --
      Luke-Jr
    5. Re:How? by Luke-Jr · · Score: 1

      Swap may be all good on x86, but disk I/O is extremely slow on x86_64 and PPC (even with DMA enabled on the x86_64) for swap.

      --
      Luke-Jr
  86. New systems with 64 MB of RAM by Luke-Jr · · Score: 1

    Have you considered that maybe such systems are not 5 year old hardware?
    The new Zaurus SL-C3000 (released within the past 6 months) computers all have 64 MB of RAM (along with 4 GB HD and 400 MHz overclockable to ~600 MHz).
    So where exactly do you suggest I find a similar system with better specs for *any* price (let alone something affordable)?

    --
    Luke-Jr
    1. Re:New systems with 64 MB of RAM by Ars-Fartsica · · Score: 0

      yes but annoying building linux for those devices strips out 90% of the code, so it is not an issue. by the same token you can run linux on an ipod (which is not powerful enough to decode ogg) once you isolate the 1% of code actually needed. this guy wants a general solution. as i said, there is one - fvwm1.

    2. Re:New systems with 64 MB of RAM by Luke-Jr · · Score: 1

      Not sure what you are saying... They can run at 600 MHz (400 MHz overclocked), so CPU isn't a big issue. 4 GB is plenty of space for a complete KDE/GNU/Linux system.

      --
      Luke-Jr
  87. vector is not "low-hanging fruit" by Chemisor · · Score: 2, Interesting

    Before you even touch any vector-to-map conversions you should make sure your disk IO is optimal. If you are reading/writing/opening any file more than once, you will see no measurable gain from adding binary search to some measly thousand element vector. If you are using the network without a pretty darn good reason, or not caching the results, you can forget about doing any other optimizations. If you need to start twenty daemons to run a word processor, you have some serious architecture design issues.

    In other words: fix the slow stuff first!

  88. Stupid Question by mslinux · · Score: 1

    This may be a stupid question, but here goes: Why don't these guys use languages (Python, for example) that are memory friendly?

    1. Re:Stupid Question by Anonymous Coward · · Score: 0
      My guess would be that people are afraid to put constraints on the programmers. Another problem is that a lot of people are resistant to using mono because of the whole (percived/real/imaginary) Microsoft issue, yet one of the top GNOME guys swears by mono. So a new language option has been added where none was required. If I had to make the executive decision I force official gnome apps to use: C, C++, Python, and perhaps one other language - probably scheme or something that's really popular among key people but not me.


      You can't clean up a mess without making hard decisions.

  89. This will work better by Mr.+Underbridge · · Score: 1
    find / -name "gnome" | rm -rf.

    I'd like my $200 now.

    1. Re:This will work better by Anonymous Coward · · Score: 0

      yeah, except that your command would do nothing.
      I think what you _meant_ was using the exec switch or piping to xargs.

      I dont think you'd get a bounty for that.

  90. Re:Math by Anonymous Coward · · Score: 0

    64 + 32 + 4

    I've seen weirder setups

    What gave you the idea that there is *any* number that can't be made up of powers of two?

  91. I'm sure you can be helped by a demon-start demon by RedLaggedTeut · · Score: 1

    What you are proposing sound like you could be helped by starting a demon which autostarts the needed gnome demons ;-)

    Another demon, but maybe you#d like this one ..

    --
    I'm still trying to figure out what people mean by 'social skills' here.
  92. $3000!!!! by SleeknStealthy · · Score: 1

    Wow, so much money, so much incentive. Honestly, I think Novell may get a little too much credit with what they have helped do with linux. I mean look at the contributions to the kernel mostly from OSDL, Redhat and IBM. What about Sun paying developers salaries for OO development. Meanwhile KDE developers make KDE much more memory efficient than Gnome for free and Novell profits. Novell simply is trying to get in the news with a prize instead of pumping a sufficient amount of money into either Desktop Environment. Lets all fight over $3000!w00t.

    --
    Math
  93. Mod parent up by willis · · Score: 1

    (lame post) This would be useful for normal users, and help get corporate users into the loop...

    --

    there is no thing
    what else could you want?
  94. Space is often traded for time by Sits · · Score: 1

    Actually it's quite common in an algorithm to trade space for time. Algorithms tend to work on abstract levels where there's lots of one resource in order to trade off. In fact many algorithms are concerned precisely about abstraction over anything else.

    The other catch is you've got to be wary of optimisations that complicate code. It used to be the case that gotos could provide a fast way to short circuit your way out of code at a cost to a reader trying to follow the code's logic.

  95. Best Possible Start by elmegil · · Score: 1

    Get rid of the horrendously evil clone of the Windows Registry.

    --
    7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
  96. I love Slashdot by bonch · · Score: 2, Insightful

    Basic visual cues are "eye candy," the favorite intellectual fallback weapon to describe anything that makes you feel less elite for using it.

    This isn't 1987 anymore. My CPU can handle drawing pleasing visual effects so that after 13 hours of programming, my eyes aren't fatigued.

    1. Re:I love Slashdot by Mr+Z · · Score: 1

      Some "eye candy's" helpful. For instance, drop shadows behind menus and the mouse pointer give better "figure-ground separation," thereby making them easier to spot.

      Menus that fade in/out, roll in/out, etc. aren't particularly helpful. Transparent xterms aren't particularly helpful either, unless you're trying to get your desktop on TV and can combine them with some fancy wallpaper and a photogenic (if unusable) theme.

      --Joe
  97. What this really means by Anonymous Coward · · Score: 0

    It seems that offering this bounty is an admittance that "volunteer effort" isn't as good a motivator as plain old financial incentive, which--shock--is what goes on in the commercial software world we all profess hate so much.

  98. What does this mean? by Anonymous Coward · · Score: 0

    This bounty means two things:

    1.) The code is bloated (just take a look at gnome-terminal sometime). Apparently, the "many eyes" idea of open source didn't work for GNOME.

    2.) Financial incentive is needed to get the software up to shape. This, too, goes against the OSS philosophy that all you need is volunteer effort to get things done. Here we see the same old capitalism in play, the same kind Slashdotters love to gripe about.

    Amusing. I expect to get modded down for pointing this out, but if you want, reply and explain why you disagree.

  99. Re:cat Gnome /dev/null by Tribbin · · Score: 1

    A desktop- and windowsmanager of your choise?

    --
    If you mod this up, your slashdot background will turn into a beautiful sunset!
  100. The reason by bonch · · Score: 1

    It's because so much gets pointlessly reinvented. Take a look at Mozilla sometime. So many wheels are reinvented in that code just for the sake of easy portability. The code is horrible. Take a look at that layout code sometime and attempt to decipher it. And Mozilla is supposed to be a golden child of OSS development!

    Also, there is less structure and discipline because it's not a corporate environment with lead programmer, project leaders, and so on overseeing things like performance and code size. Instead, it's a volunteer effort that takes code from all over the place rather than from the small pool of gifted programmers you hired solely for your project.

    Everything has advantages and disadvantages, and OSS has its disadvantages like any other model.

  101. Try XFce by Anonymous Coward · · Score: 0

    I gave up on the Gnome and currently run with the Mouse that flies. I have a 200MHz PPro with 128MB RAM. Gnome is usable if I'm not Gimping. When I am which is often ( I'm changing my carrer from programmer to artist) Gnome is intollerable ( 3 seconds for a penstroke!). I have found that XFce is at least usable on my antique hardware. The other nice thing about it is that it has not been Microsofted.

  102. Re:omg, pseudo nerd, eugenia, jerk, world hates us by Tribbin · · Score: 1

    How is somebody a jerk for being naive? How can you hate somebody for being naive?

    With 'the whole world' you mean everybody except the Americans and the people who do not hate Americans?

    --
    If you mod this up, your slashdot background will turn into a beautiful sunset!
  103. Re:horrible idea by Tribbin · · Score: 1

    Some kind of really wanted ring?

    --
    If you mod this up, your slashdot background will turn into a beautiful sunset!
  104. The real reason why memory usage on GNOME sucks by Anonymous Coward · · Score: 0

    The reason people haven't done profiling/memory usage reduction is because GNOME CVS is a pain in the ass to hack on (IMHO, of course), so the only people that work on it are *seriously* dedicated.

    My idea of a nice program to work on is one where you can sit down, pull CVS, implement and test your patch, and send it in. I used to do this quite happily with rxvt -- discover that a feature could be added, pull CVS, add code, test, submit. Piece of cake.

    Now, let's compare the process for working on, say, gnome-terminal. Well, I'm running Fedora Core 3, which is pretty up-to-date. But when I pull down gnome-terminal CVS, it won't build because it requires gnome-common from CVS. Okay, I pull that down, semi-manually bundle it up into an RPM (so that I can remove it later). Install it. Try again to build gnome-terminal, discover that it has a mass of more dependencies. Which require more dependencies. I'm not going to deal with the breakage ensuing from installing an entire set of CVS Gnome and waste the time involved with dealing with all the crap I just dumped all over my system just because I want to hack on one piece of software.

    This also bit me with Gaim -- I got irritated with something minor in Gaim, read through the code, realized that a patch would be easy to produce, pulled CVS -- and then discovered that because of one addition that the Gaim author chose to make (use of gtk_cell_view), CVS gaim requires gtk+ 2.6 instead of 2.4 (what ships with FC3). I'm not going to hassle with dependency hell, troubleshoot all the problems involved with dumping the stuff all overy my system, just to add my minor patch. So now *I* don't have my feature and all the other people out there who would have enjoyed the feature are also missing out.

    The problem is that the GNOME libraries are just too quick-moving of a target, and *all* of the GNOME software is rapidly updated to use the very-latest and greatest features (and hence *require* the latest and greatest GNOME dependencies). Which nobody who just wants to drop in a small patch wants to hassle with. If you are a GNOME author, and you want help from OSS developers out there, you simply need to stop requiring the latest-and-greatest. Give a six-month lead on new library versions, if you can, so that distros have some time to get out a system that you can code to.

    A similar example -- the Xlibs that ship with Fedora Cores have long been buggy, and trigger valgrind (or at least I see otherwise-nonbuggy software triggering valgrind's memcheck tool in Xlib code). But I don't really want to go through the hassle of dumping new X stuff all over my system just to investigate a problem that probably exists, but can't be directly linked to crashes or misbehavior on my system. You also see surprisingly few people hacking on X (given the number of people that use it and the number of people that have straightforward feature wishes involving it).

    Software that requires the latest-and-greatest of a vast dependency tree that that requires altering important software on the system will *never* be as well maintained as software that does not. GNOME makes it a pain in the ass to just drop in and submit a bugfix or a feature fix or two.

    I have submitted numerous patches to OSS software packages to reduce memory usage and CPU usage, and plan to continue doing so in the future (even though I don't have the old PII that inspired me to write a bunch of my earlier patches). But as long as it's easier for me to just continue using xterms than to start hacking on a piece of software in GNOME CVS, I'm not going to be touching the code.

    -0x0d0a (account and IP banned from Slashdot, making his first post in ages)

    1. Re:The real reason why memory usage on GNOME sucks by Anonymous Coward · · Score: 0

      Good to see you back 0x0d0a!

  105. Re:I'm sure you can be helped by a demon-start dem by Stween · · Score: 1

    The point was that it's not something that runs by default unless you log into Gnome.

    Run gtk apps outwith Gnome, and you'll lose some settings. Someone else points out that after the settings daemon, a ~/.gtkrc-2.0 will be checked by GTK, though as I recall this isn't bulletproof (font settings not stored in the rc file change the moment the daemon is up and running, last time I toyed with it).

    I have no problem with many daemons running, my point was purely that to have to carry this settings daemon around with you even when you're not using Gnome seems a bit excessive. Granted, anybody who truly gets off on using as few CPU cycles as possible isn't going to be using GTK-2.x... ;)

  106. Its the libraries! by Anonymous Coward · · Score: 0

    Library on top of endless library, based on the vain assumption it somehow decreases programming work and increases managability. Quite the opposite in reality.

    How many end applications are there? Not many. How many libraries are there, all developed in isolation? Umpteen jillion.

  107. A modest proposal by Anonymous Coward · · Score: 0

    Force all open-source developers to use 64-bit platforms (preferably amd64, PPC64, and MIPS64 at least, for as much cross-platform exposure as possible) with only 128 MB RAM.

    It sounds crazy but then you tackle 2 birds with one stone. Reduced memory bloat and 64-bit clean code all in one shot from day one.

  108. Implementations did exist. by Anonymous Coward · · Score: 0

    In fact, there has been several different implementations - the two best known during the dotcom boom. See here, for example:

    http://www.searls.com/linuxforsuits/industry.htm l

    I'm very interested in the topic since I first heard about bounties. Unfortunatly, a good implementation (ie. covering not only the US) is a little bit complicated.

    But it will come (back), I'm sure. As far as I know it has been (or is) under consideration by Canonical/Ubuntu.

    claus

  109. How about "Don't use CORBA?" by kriston · · Score: 1

    KDE realized this years ago and moved to the lightweight DCOP for inter-process communications. Come on, GNOME team, CORBA is for inter-computer communications and should be abandoned immediately in favor of a lightweight replacement. Bonobo doesn't count.

    --

    Kriston

  110. When are people going to learn? by e_xworm · · Score: 1

    Any DE will need a configuration system
    Any such system will be hierarhical
    Any hierarhical system can be displayed in a registry like format...
    Is THAT really a problem? Geez get a grip on yourselves

    --
    X~
    1. Re:When are people going to learn? by elmegil · · Score: 2, Insightful
      Guess what? Firefox needs a hiirarchical (note correct spelling) configuration system too, and didn't have to resort to the abomination that is the GNOME Registry Reimplementation. I'm sorry, but duplicating ALL the HORRIBLE non-features of such a NON TRANSPARENT configuration system was a really stupid move. There are plenty of ways to manage hierarchical data without resorting to such utter performance hogging shit.

      And there's nothing better than "oops, something screwed up my registry, gotta delete it and start from zero."

      --
      7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
    2. Re:When are people going to learn? by Anonymous Coward · · Score: 0

      hiirarchical (note correct spelling)
      wrong spelling dumbazz

    3. Re:When are people going to learn? by e_xworm · · Score: 1

      Read again. I'm just saying that any hierarhical configuration system can be displayed in a tree... just like registry. It's pretty nice if you think of it.
      Ah... when are people going to learn...

      --
      X~
    4. Re:When are people going to learn? by elmegil · · Score: 1

      I'm not objecting to DISPLAY, I'm objecting to IMPLEMENTATION. So one could advise you to read MY post again, eh?

      --
      7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
    5. Re:When are people going to learn? by e_xworm · · Score: 1

      Ermmmmm No.
      Totaly different Implementation.
      No CLSID's in gconf. And what's wrong with the implementation? Just good old xml

      --
      X~
    6. Re:When are people going to learn? by elmegil · · Score: 1
      Just good old xml

      Really?

      [Default]
      0,id=118199e006000110174345800000075260 002
      0,RestartStyleHint=2
      0,Priority=40
      0,Progra m=gnome-panel
      0,CurrentDirectory=/home/ph28385
      0 ,CloneCommand=gnome-panel --sm-config-prefix /gnome-panel-DzaISd/ --profile default
      0,RestartCommand=gnome-panel --sm-config-prefix /gnome-panel-DzaISd/ --sm-client-id 118199e006000110174345800000075260002 --screen 0 --profile default
      1,id=118199e00600011017442470000007526000 4
      1,Program=gnome-terminal
      And that's just one segment of one of dozens of little files running around in my .gnome2 directory. Doesn't look like any XML I've ever seen.

      I suppose that perhaps they DID reimplement using XML in the latest releases, but I'm not a "keep up with the Joneses" kind of guy. If they HAVE reimplemented, then you might have said so. But in the bad old 2.0 days, it was utter crap.

      --
      7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
  111. Re:omg, pseudo nerd, eugenia, jerk, world hates us by e_xworm · · Score: 1

    Actually (this may come as a shock to you) America is not just USA
    So with the whole world he means everybody (quite a bunch even if you just count china) except some Americans who do not hate Americans :) hope I helped you there
    Hope I didn't sound too korny I just wanted to be funny

    --
    X~
  112. Obligatory by Anonymous Coward · · Score: 0

    My backpack's got jets, I'm Boba the Fett
    I bounty hunt for Jabba Hutt to finance my vette.
    I chill in deep space, a mask is over my face.
    I deliver the prize, but I still narrow my eyes, cuz my time I don't like to waste. Get down!

  113. MOD PARENT UP by Anonymous Coward · · Score: 0

    Mod up, GnomeOffice is so much faster.

  114. Re:horrible idea by dustmite · · Score: 1

    Something non-monetary that is often an important motivator: glory/credit/recognition. Put their name in lights for their achievements/contributions.

  115. Re:I'm sure you can be helped by a demon-start dem by Anonymous Coward · · Score: 0

    Run gtk apps outwith Gnome, and you'll lose some settings.

    That's terrible design. The library should start the daemon if it doesn't find it running.

    my point was purely that to have to carry this settings daemon around with you even when you're not using Gnome seems a bit excessive.

    Why? It's merely partitioning functionality into an external process. The functionality has to go somewhere. It sounds to me that you are forgetting that, and assuming that a client that handles stuff itself magically gets the functionality for free.

  116. Re:Math by Mr+Z · · Score: 1

    sqrt(2)....

    Oh, ok, you can if you use an infinite number of powers of 2...

  117. free clue by Anonymous Coward · · Score: 0
    XFce is at least usable on my antique hardware

    i'll give you clue one for being a graphic designer - you better get some hardware that is vintage 2004 at the oldest if you want to get anything done.

    modern graphic design and "antique hardware" do not walk hand in hand.

  118. Novell is a newcomer but even so by Chuck+Chunder · · Score: 1

    I'd argue that they are indeed investing credible resources (if not "pumping money") into important parts of desktop infrastructure.

    Robert Love working on HAL.
    Robert O'Callahan working on Mozilla.
    David Reveman working on Glitz/Cairo
    Etc, etc.

    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
  119. This is JUST SILLY! by diablobsb · · Score: 1

    everyone knows that gnomes are fat...

    http://members.aol.com/TheRobots2/jpeg/gnome.jpg

    btw: i'm a kde user...
    kde 3.4 Rocks.... and kde 4 (with qt 4) will rock even more...

    --
    I for one, welcome our new hot grits... PROFIT!
  120. what I'd like by CAIMLAS · · Score: 1

    I'd like it if they'd optimize it so that the save dialog actually works instead of being a UI nightmare. It feels like it's about 10 years of negative progress.

    Even the Windows save dialog is better.

    --
    ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
  121. $800? by Anonymous Coward · · Score: 0

    So how many weeks of work does this $800 buy? I'm amazed at the apparently small size of these bounties, given the size of the industry that now exists around Linux. I guess they assume you live in a place with really low cost of living? Or just have tons of spare time? Or is it the thrill of winning the bounty?

  122. The answer to the bloat is.. by fishermonger · · Score: 1
    KD ^H ^H Emacs of course (eh, wait..)

    Not to trauuull, but KDE people: get over it, TrollTech just missed the the licsencing train by a few years. A good lesson to all s/w companies.

    --
    "...normal evolution would have gone Word to Frame to troff, but instead, the computer industry has gone the other way!"
  123. Re:horrible idea by LinuxHam · · Score: 1

    Thanks and thanks ;)

    --
    Intelligent Life on Earth
  124. Have you tried xfce4? by xororand · · Score: 1

    I've recently switched from kde to the gtk-based xfce4 because I wanted more free memory. It is stable, fast and still looks good. If you want to give it a try, check out http://xfce.org. The only drawback I've noticed personally is the (imo) odd file manager which can't be compared to Konqueror or Nautilus in functionality. You can still use one of these though.

  125. I don't agree with you... by leonbrooks · · Score: 1

    ...but I have cursed (metamodded against) the idiot who painted this with a "Flamebait" rating.

    Note to such idiots: modding is not about whether you agree with what's said, it's about how well the poster made their point. This post was well written, made some good points (if not as valid as the author might hope), was on topic and (-: hallelujah! :-) gramatically correct.

    I'd give it +1 Interesting. Perhaps Slash needs to do something like LXer and break the ratings out into separate agree/disagree, quality/trash scales?

    --
    Got time? Spend some of it coding or testing
  126. Re:cat Gnome /dev/null by aichpvee · · Score: 1

    Wait, you're saying you can use the gnome GUI? I'm calling bullshit!

    --
    The Farewell Tour II