Is the Linux Desktop Getting Heavier and Slower?
Johan Schinberg writes "Bob Marr wrote an interesting editorial about what many of us have have noticed lately: the three most popular Linux distros are getting "fatter" in terms of their memory footprint and CPU demands for their graphical desktops. Fedora Core 2 isn't usable below 192 MBs of RAM while Mandrake and SuSE aren't very far off similar requirements either. There was a time when Linux users would brag that their favorite OS was far less demanding that Windows, but this doesn't seem to be the case anymore. Modern distros that use the latest versions of KDE and (especially) Gnome feel considerably heavier than before or even than Windows XP/2k3. Sure, Longhorn has higher requirements than XP (256 MB RAM, 800 MHz CPU) and the final version will undoubtly be much more demanding, but that's in 2-3 years from now. For the time being, I am settled with XFce on my Gentoo but I always welcome more carefully-written code."
I like using GNUstep/Window Maker on my *nix boxes. It looks great and it's a lean, mean window moving machine.
I haven't heard someone say they use Linux because it's somehow "lighter" since about 1997. The face of computing has changed, and the Linux distros have changed with it. More and more users are using Linux because it's getting more feature-rich. This is not a bad thing.
Those people that want mean, lean systems can install the distro they prefer. The commercial distros need to complete with other commercial operating systems, including Windows. So if they need an equivalent amount of memory, I have no problem with that.
Yes, it is comparable. And you are not getting any more. Possibly not even as much. This is a sad fact - but not for me. I'm using ratpoison and lynx.
Linux desktop reform NOW! One unified clipboard methodology with user definable semantics!
Personally -- I prefer fluxbox's minimalism. It doesn't really matter what the distros ship with because at least you're given an option on going with a lean option or a feature-ridden one.
Massive networking attempt for friends
Sadly it used to be that you could run Linux on just about anything. I install all my servers with out any kind of X environment because it pigs up too much space. It is a pain too because RedHat automaticaly installs all sorts of crap that is unneeded, so I have to remove it after a generic install.
I used to run XWindows on 8 megs of RAM. (circa 1994)
I think the complaint that Linux desktops are getting too fat is spot-on. Then again, does anyone really run GUI applications on their important Linux servers?
I think the important point here is missed: At least under Linux you _have_ a choice.
Trainee BOFH -- Just give me your username & password
Windows 2000/XP is very quick with 128MB. Like some users have reported, less than 256MB and the latest Linux distros are pretty un-responsive as a desktop. Blame the newer KDE/GNOME.
I am amazed that people do not realize that it becomes difficult to run NEW 2004 software on old 1999 hardware.
Perhaps the best post on this from the OSNEWS discussion on this editorial:
- - - - -
Anecdotal evidence --> meaningless conclusion
By Andrew (IP: ---.fbx.proxad.net)
Posted on 2004-06-10 09:46:37
Summary of the arguments presented in this thread:
- My X yearx old computer with Y MB RAM is slow with the latest Z Linux distribution.
where 3 < X < 6,
and 64 < Y < 256,
and Z is an element of the set of full-fledged Linux distributions like Fedora, Mandrake, SuSE, you name it.
The meaningless conclusion is: "Linux is getting very fat".
How the author jumps from his anecdotal evidence to his meaningless conclusion is clearly fuel for a long thread, seeing as this thread is growing fast...
Currently I run crux, this is a nice alternative to the bloated distros out there. It's a "build what you want" (aside from the 'base' and 'opt' packages). Personally I gave up on RedHate about 2 years ago, it's way too bloated and slow. I run crux with xfce4, it's light and fast, on my 500mhz laptop that does make a difference, especially when you are trying to get something done while compiling firefox :).
Seriosly, you need more space to build a fluid, friendly OS / windowmanager, but you don't need bloat.
I like having a nice core set of tools, I don't need three gui calculators and 5 CD playing utilities. There is a lot of bloat, and it's not doing anyone much good.
http://monkeyserver.com --- weeeeee
With today's modern PC's, it's not too far out there. I think one of point the author was trying to make was that with requirements like that, you lose one of the advantages of a Linux based system. You can no longer claim (using the big 3 distro's) it's faster. Sure you could use Xfce or a similar streamlined window manager to get some of the speed back, but if you want same polished look and feel (IMHO), and really want to sell Linux on the desktop and workstation, you're going to have to make that performance/visual usability sacrafice.
the gui stuff should NOT eat so much memory.
it just shows that the kde/gnome/whatever guys are trying to compete with each other and windows by throwing in the latest fanciest stuff without really thinking.
let me repeat it: desktop software should NOT eat that much memory. it only shows the low quality of the code.
Amen
i have my slackware 9.1 box (700mhz celeron, 192 megs of ram) booting from power button to fully usable (it's a laptop - so it automagically logs in) in ~1 minute, and have no problems with the responsiveness in gnome or kde. (that boot speed took quite a bit of fine tuning, though)
On the other hand, I use a fedora core 1 box for work, and it's sluggish in both gnome and kde on an athlon XP2500+ with 256 megs of ram.
seems to be getting faster and faster. Jump to 3.2 was pretty big when it comes to performance. And Qt4 brings with it even better performance (application start-up time drops by about 20%) and mem-usage (down about 15-20%). KDE has been pretty aggressive recently when it comes to performance and optimizations. Of course KDE gets more and more eye-candy, but that stuff is completely optional.
Is Linux less demanding than Windows? yes it is. If you want to, you can run the latest whiz-bang desktop from Gnome or KDE, and the performance will be roughy similar to Windows. Or you could use some lightweight UI, like Xfce. If you decide to run som graphics-heavy UI with lots of eye-candy, it's your choice, and you should expect it to be somewhat slower than some lightweight UI would be. But you have the choice.
I for one think that the progress of features and eye-candy should not be held back by that guy who still runs Linux on his 200MHz Pentium. If he wants to, he can keep on using the UI he currently uses, or switch to some lightweight UI. Or, heaven forbid: upgrade his machine! If you have the hardware, you should have the ability to put that processing-power to use by using some kick-ass UI with lots of eye-candy.
Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
My first inclination was to hate this editorial... after all, I'm happily using Fedora Core 2 on my 512MB RAM 1.6Ghz P4. No problems here, it performs fine. But the more I read the more I found myself agreeing with his basic thesis.
.wmv video files and I say err, shit... I'm not positive this will play...
He's right. It *is* a shame that Linux needs more memory and CPU power than XP, yet still feels slower. It's also more annoying, btw.. in the time I've been writing this response, Rhythmbox with the mp3 gstreamer plugin, playing an mp3 from a samba share, has dropped audio three times for a second or more. My coworkers laugh at me when they send me
Linux as a desktop os is bloated, slow and unreliable. As as Linux on the desktop advocate, I often feel like a vegetarian... sure, it's virtuous, but I'm stuck eating pasta and potatoes instead of lamb chops and meatball sandwiches.
I'm just not sure of the solution. The author of the article is a little bit glib when he says "We need to put a serious emphasis on elegant design, careful coding and making the most of RAM, not throwing in hurried features just because we can." Easy to say. Hard to do. I know the Gnome developers and the rest of the thousands of people working hard for little or no money on the OS collectively known as GNU/Linux are doing their best to pay attention to elegant design and careful coding. The problem is that as many voices as there are screaming for elegant design... there are as many voices screaming for mono, java, and other "next gen" development tools.
Total disk space: 120MB. With 16MB knocked off for swap that's not a whole lot of disk space.
These days it's hard to find a linux distribution that will even let you use console mode applications in that amount of space, but I have a sneaking suspicion that slackware is the answer. However, the last few times I've tried to install slackware (on a lark, to see what it's like lately) it wouldn't install or wouldn't run, and I've ended up installing gentoo. A slow install is better than no install... maybe that ought to be the new gentoo motto? :)
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Just fire up top and see what's running. You may be surprised by how much RAM some applications take, but keep in mind that the number reported for X tends not to be accurate (They nmap the video card RAM so it gets reported as used RAM or something like that.)
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
A lot of it is illusory. When dragging windows around, for example, XFree86 seems slow because it renders the whole process poorly. Things jitter and blink and just look horrible. In Windows and MacOS X things look nice and smooth. However, if you actually measure these things, XFree86 is faster. The same can be said for a lot of things. That is, they seem slower because the way XFree86 does things (which, by the way, is being worked on extensively thanks to people like Keith Packard).
And why do you think that MS Word pops up instantly? Think about it - it's a large program split over multiple files, all of which have to be accessed before the program can be run.
Now consider how long it takes to open a New window in OpenOffice.org once it is loaded.
Finished thinking? Good.
At this point, you are hopefully at the right conclusion - MS Word is already mostly loaded when you clicked on it to run. Almost all MS apps preload large sections of the core functionality in a standard install to improve responsiveness once the system is up and running. Alas this approach is also taken by a load of other apps on Windows with the net result that even though the desktop in Windows XP pops up faster on boot than previous iterations of the Windows OS, it can often be a couple of minutes before the hard drive stops popping and thrashing and the system becomes quiescent (and usable).
Real start up times for apps are difficult to gauge even when they aren't preloaded. OpenOffice.org is a slow starter although it is leaps-and-bounds better in version 1.1 than it used to be when it was first released and I hope that the improvements in start time continue . That said, on days when I'm writing a lot of documentation, it gets loaded in the morning once and gets used all day without complaint. If I accidently shut it down, most of the files used are still in the linux file cache and restarting it is a matter of a couple of seconds of turn over.
Cheers,
Toby Haynes
Anything I post is strictly my own thoughts and doesn't necessarily have anything to do with the opinions of IBM.
The problem here seems to be that you're trying to run the latest and greatest on old hardware. Why not try a distribution from a few years ago?
> I'm using Gnome and sometimes KDE for Mandrake and
> when I'm in WinXP the system is a lot more fluid
> then in KDE or Gnome.
I did the KDE/Gnome thing for a while, until one day when I was dorking around with some opengl stuff and playing with some test apps.. I think at the point I noticed the problems with KDE or Gnome the most was when I was testing a physics library that's out there.
Under Gnome or KDE (default config, though under Gnome I did kill off as many services as I could) I would quite literally get 3-5 fps on a test app that was dropping blocks out of the air and bouncing them around. It was unusable. On a lark, I swapped to twm for a few minutes to see if the issue was my machine or the window manager.. instant 50 fps boost running the same program. I've now sworn away using KDE or Gnome, and settled on one of the "lightweight" managers out there.
I'm sorry, but if the desktop software is that inefficient then there's no way linux is ever going to improve its status.
Those of you who are posting stuff about Fluxbox, Windowmaker, Ratpoison, *insert your favourite WM here*, are missing the point, and need to RTFA.
There is a huge segment of the market with 64-128M PCs who don't want to be forced to upgrade their hardware just so as to run XP. If Linux could run responsively on that much memory, it could own that market. But instead, modern distros are too slow.
For this segment, Fluxbox, dillo etc. are not an option - they need the user friendliness of a proper desktop environment (help browsers, tooltips, proper word processors etc). KDE and Gnome could provide that - but they need to control the bloat.
To be fair, I hear KDE has improved a lot in this respect, and my mobile PII with 192M is reasonably nippy running Gnome and openoffice. So improvements will come.
But talking about the command line and fluxbox and all that is just irrelevant.
Windowmaker provides a very pleasant environment and it's a lot smaller and lighter than the Gnome or KDE desktops. And while you can't theme it to hell and back... it's got a nice, consistent and user-friendly configuration tool, including support for its lightweight themes.
OpenStep (GNUStep) is a decent toolkit, and it should be possible to use GNUStep and write applications that will compile under Cocoa on Mac OS X as well...
Why these aren't more commonly used, I don't know. They don't have that Windows-style panache, I guess.
Fr'instance, I have a Thinkpad 600 with 64 MB of RAM. The thing is just sitting in a box right now because I've been unable to find a distribution that will run gracefully on this machine.
;) But seriously, I don't think you'll be able to get much of a graphical setup going on 64M of ram nowadays. Mainly because most of the cool-new-graphical-apps are memory hogs. You're probably better off doing a console only install with Screen to manage all the apps you could need, mutt for email, naim for IM, mpg123 for music playback, and links for www. Use ctrl+a-n to flip through all those apps, you could probably leave em all open all the time too since they're light enough.
It's called Windows 98.
Linux is NOT obviously more rock solid. People have been saying this for years but it is simply no longer true. Win2k and XP effectively eliminated the stability gap, especially when compared to KDE or Gnome.
I don't know how things stand on the server side, but in my experience on the desktop, XP wins in both stability and speed. I could comfortably run it on a 400 MHz AMD k6-2 with 128 Mb of RAM. Try doing that with Fedora core 2 or Mandrake 10.
It is definitely time people let go of old saws like "Linux is obviously more rock solid" and face up to the reality of desktop users experience.
Download my free songs!
Because people keep insisting that they be as friendly and action-packed as a typical windows desktop.
As long as the powers that be insist upon making popular desktops do everything without the need of a shell window, then they are going to be bloated. I don't care how pretty KDE is, it actually irritates me when after a default install of it I have to go hunting through the menus to find the well-hidden shell.
This is what you guys get when you keep preaching that linux is just as friendly as windows so everyone should switch. You get the same kind of bloat windows has.
And note that Linux is a kernel. Don't want to run some bloated window manager? Then don't! I'm using fvwm95 right now and it's only using a few MB of ram. Yes, this box does have 1 GB of ram, but fvwm95 gives me what I need. And if you don't need X, don't start it, and even brand spanking new Linux distributions will run ok in 32 MB or so of RAM. Such a machine could make an ok small DNS or Web server ... try getting XP or 2000 to even install with only 32 MB of ram. Mostly because Windows doesn't let you turn off the GUI.
It would be easier to grasp if it wasn't so mind-numbingly oversimplified.I used to run Linux + X11 on a 8Mb 386DX-25 desktop. Worked fine and fast running Window Managers like IceWM and AmiWM.
You are not alone. This is not normal. None of this is normal.
I wouldn't blame the newer KDE or Gnome releases. They only require more power because that's what people want; an environent that has Windows-like features and capabilities that are often expected in a modern and easy-to-use desktop. The same could be said for Mac OS X, which requires reasonable amounts of power to perform nicely as well.
I run Gnome 2.6 on a PC with a 450 MHz P3 and 256 MB of RAM, which is piddly by today's standards. It runs fine.
An no.... Windows 2000 is not "very quick" with 128 MB of RAM, it swaps in and out very frequently. It's only reasonable if you have at least a 7200 RPM hard drive.
As for the original post on the subject, XFCE is great if you want the look and features of a 20-year old UNIX interface... That's exactly what it is, which is why it runs so well on older hardware. Gnome is carefully written and runs fast for what it does, so it's not fair to complain about it if you are on hardware that is half a decade old and are trying to use a desktop of 2004.
This is such a tired and silly subject... People complain when they don't even know how Linux uses shared and caches memory when they see the system monitor and scream (on IRC): "Why is t3h Gnomer terminal using 15 MB!!!!111 OMIGOSH!!111 T3H Epiphany is using 104 MB!!!111"... Bah. Get real.
I wonder... did s/he compile the lastest custom kernel for their hardware? Did they tune ATA I/O performance with hdparm? Did he disable non-essential daemons running in the background? I doubt it.
True, but then again they didn't do it for Windows either. Regular users don't care to dig that deeply into their system, they expect it will simply work. If it doesn't work at least as well as Windows out-of-the-box, well then there is another Windows user.
teeker
Also, by making the user interface more and more bloated, it becomes less and less useable on older hardware. And that used to be one of the strengths of Linux, that you could run the latest distributions of Linux on old hardware and have them still be quite useable.
The jittery window dragging... that may be true for kde and gnome, i don't know. I do know that running Enlightenment (no kde or gnome) i get smooth moves. This is on a crappy rage mobility video card from 3 years ago, with something like 8 megs of shared video memory, and a modile duron 800MHz, with 128M RAM. So maybe it's the window manager acting as a bottleneck for redrawing. But as you said, that is why it is good to have separate layers that can be independantly improved.
Another thing, if something "seems slow" to the user, then for all intensive purposes you might as well say "it is slow". If it gets the task done faster, but leaves the system unusable for 2 seconds, who cares? thats 2 seconds that you are forced into "serial mode" instead of a "parallel mode" of work.
You make a good point, I just don't think it can be a general statement.
No matter how well a C compiler is written to create optimal code, it just isn't the equal of someone experienced writing in Assembler from the get-go. The problem is, where do you find the sort of qualified Assembler programmers you need to write the sort of tight code required to increase speed and reduce memory footprint? Does anyone even know Assembler anymore? The big loss, of course, in using Assembler would be portability across different CPU's.
"My country, right or wrong; if right, to be kept right; and if wrong, to be set right." --Senator Carl Schurz (1872)
What seems to be the most reason of slow desktops are
anti-aliased fonts (yeah they look nice, but everything is done on the client side, not server side as it should be) and horribly inefficient toolkits generating too many X calls. One example that I would like to highlight is the FOX toolkit which has very efficient automatic delayed paint / layout algorithm. FOX applications start up in the matter of milliseconds.
To quote the original author of FOX:
"The delayed painting is important, as it prevents stacking up huge piles of expose events when for example dragging [solid-, or opaque-dragging] windows over FOX applications. By NOT doing the unnecessary work, the system actually catches up more quickly, and never falls behind more than one repaint.
The delayed layout is responsible for the extremely fast startup times of FOX applications. As hundreds of Widgets are being added during construction of an application's GUI, recalculating layout after each addition really kills startup performance.
Delayed layout benefits performance each time many GUI Widgets are added or removed, or if layout hints are changed with widespread effects. It also makes opaque resizing [supported by a few X Window Managers] quite fast."
Recently though they added anti-aliased fonts, startup times almost trippled and overall performance went down with it (still not as worse as some other toolkits).
As expected on slashdot there are whole ton of stupid comments exonerating Linux for one reason or another. Instead of addressing each of them individually, I will hit a bunch in in this post.
In light of the Windowes System Requirements, is this really that big?
Why does it matter what the requirements on the box say? KDE/GNOME are as slow or slower than windows when run on the same hardware! So the fact that windows has hich system requirements doesn't excuse the fact that Linux has higher ones.
But it isn't as heavy if you don't run those Desktops and applications.
That is not a fair comparison. It is easy to be lighter weight when you don't do as much.
If you need to do everthing that you can do in windows, then Linux is signifcantly slower (mostly footprint and loading time) than windows.
But Windows preloads thier applications.
That is a good argument for Mozilla vs. IE on windows, but in most cases is not valid. Like the submitter stated, even third party applications tend load quicker on windows that most linux applications do in windows. I have used Linux for years and I can't tell you how many times I have gotten tired of the slow responsiveness of KDE and GNOME and have reverted back to my old TWM (or even more lightweight) ways. Where-as on the same machine Windows 98 or 2000 were quite responsive (just not very usefull for what I was doing).
Secondly there is no reason that Linux could not preload common applications to make them run faster, and if that makes the system more responsive they should do so. But I really don't think that would completely solve the problem, it would just make the boot time longer, and boot for a Linux desktop is already longer than for Windows XP or OS X.
So basically it comes down to the fact that it is (relatively) easy to write full-featured software and it is easy to write light-wieght software but doing both is hard. Microsoft is doing a better job than the open source desktops in that regard.
When I saw GNOME under development, I never thought to myself, "self, now that GNOME thing looks to speed things up". Never once did it even occur to me that all that PrettyFactor would be light on memory or CPU. Is the Linux Desktop getting heavier and slower? If you use GNOME or KDE or any other "user friendly" desktop environment, yes.
I've got a 486/66 at home running a mail / web / name / shell server. He's keeping up pretty well, but I must admit that console dselect takes a minute longer than I would prefer to start up. For his every day tasks, even keeping up with updates, it's more than enough-- so really, this is a question of the GUI end of things.
I wonder how well it would work to introduce one of those reviewers to a very well set up and themed tvtwm2 or whatnot. You know, without all the Kapps or Gapps. I bet the reviewer says it's snappy as a rubber band, but it doesn't do anything (most of those setups don't have any easy to find buttons, you have to click on a blank background to start anything). I think under that environment, Moz, OO, Wine, etc. work, but the plethora of free apps that make Linux interesting to the hobbyist seem to take advantage of the easy to use Glibs and Klibs. The reason for the "bloat" (i.e. heavier and slower) is the added functionality and eye candy.
You can take your lean and mean Linux Desktop, but don't expect it to run all the pretty apps nor expect it to have anti-aliasing and PrettyFactor3.0.
KDE has only been getting faster. KDE 3.0 was way faster than 2.x, and it only got better in 3.1 and now in 3.2. Also Distros based on kernel 2.6.x also feel more responsive. To me things are getting better...
what the hell is anyone doing about it!
Seriously, if KDE is so big and fat, then why isn't it being stripped down? If the libraries and recycleable components are taking up too much RAM, why isn't anybody pairing them down to "lean and mean" pieces.
Is it because this development isn't sexy? If so, I'll say that's BS. When the Firefox RC came out the other day, the first thing I wanted to know was if:
A) the installer was smaller
B) the RAM footprint was below the 18-30MB that it usually runs at
(and if they fixed leakage... why is it when I close all my tabs I don't get back to 18MB anymore?)
That kind of stuff is cool. Making an iTunes ripoff just because it's "new to Linux" isn't.
Just so you know, 2 years ago when XP came out ( was it 2 or 3? ) a 1.5ghz was god damned fast and people were buying 600mhz systems because they were good enough to run the latest windows os. Now compare redhat 8 or mandrake 7.2 to windows xp and im sure it will seem on par with windows for the time. Thats the key difference in my mind between linux and windows. Linux: You can get the newest WM feature tonight. If you wanted you could install Gnome Dashboard. Windows: I gotta wait until 2007 for the newest system to come out. Its not anyone's fault that Linux is where MS will be in a few years.
Because word was written in C and OO is wrtten in JAVA
So software developers are taking advantage of faster CPUs and the dirt cheap price of RAM. How is this bad? I want my computer to do more over time, not to minimize featuresets just so hobbyists can screw around with full installs of the latest distros on an old Sparc 10 taken from an office trash heap.
People who want to Linux on crappy old hardware need to use crappy old distros or run BlackBox. That's life. Obsolesence is just the way of computing, and that isn't going to change just because a few morons refuse to give up on that old Pentium 233 and buy an Athlon.
>A lot of it is illusory.
Isn't that the point of a windows-based system?
>XFree86 seems slow because it renders the whole process poorly
So how isn't it slow? How does a display system just "appears" slow to the user, but it actually isn't?
>if you actually measure these things, XFree86 is faster.
And what measurement is that?
If it appears slow, why isn't it slow?
The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
1) Is your X server using an accelerated driver, or the framebuffer device, or even the generic vesa driver?
2) If you are using an accelerated driver, which one? Some provide more acceleration than others.
3) Are you using anti-aliased font rendering? If so, did you check to see whether your driver supports hardware acceleration of the RENDER extension?
4) Did your friend disable unnecessary background processes, or did he just do a "full" install so he didn't miss out on any goodies.
Finally, users don't want fast machines that do nothing, they want machines that perform some useful task. For years, the calls were for "usable desktop applications", tools such as xpaint, xfig, midnight commander and Lyx + latex being judged as being "unsuitable". Well, now we've got the kind of fully-featured applications that were being called for, but in order to create them _in reasonable amounts of time_, and with a reasonably high level of reliability, reusable component architectures (e.g. GTK, DCOP, Qt, etc) need to be used.
As the motto goes - "Good, fast, cheap - pick any two" (where "good" in this case means "efficient", "fast" means "available now rather than in 10 years time" and "cheap" still means low cost). The mass market appears to have decided that it likes "Cheap" and "Fast" - just like with PC hardware, in fact.
If you think there's a market for "Good" and "Fast", go right ahead and try to make some money doing it.
--
is because there are so many different widget libraries still in use. Suppose the user is running kmail in gnome, and browsing with mozilla, with OO.o in the background. Hardly an uncommon situation. But that's 4 different widget sets, and a lot of memory could be saved if all apps used the same widgets as they do on Windows. Sadly, choice is often not good.
I'm trying to adapt to Linux, but it's painfully slow. I've got a 300MHz K6-2 with 192MB RAM, but I'm going to have to try a slim window manager because KDE bogs everything down. My complaint is that it seems there aren't many window managers that are in a middle ground. I've looked at several of the smaller window managers, and they seem way too spartan. They're barely better than a straight Xserver. Can't you get wallpaper, desktop icons, a Start menu, and taskbar without the thing sucking resources like a sponge? That right click program menu is a waste of time because you have to minimize the apps you're running to right click for that menu.
We may experience some slight turbulence and then...explode. -Capt. Mal Reynolds
Just because you can't think of any useful graphical tools doesn't mean that there aren't any.
I think that the many people who use Photoshop, Quark, Excel, Visio, etc. would agree with me.
Slower/faster cannot be measured by clock speed alone. If it feels slower, it is slower. The reason is that there is more going on than just the movement of a window. There is a person moving that window. That person is likely thinking and may even be reading something on that window while they are moving it. If it is flashing and ugly, just the distraction from a thought train in progress may in fact "slow" that person's process down. It might even derail a thought and cause something to be missed that was vital. A concentration on speed instead of the holistic process of the common computer user (as opposed to the specialist) is part of the reason Linux is behind on the desktop.
The point isn't that Linux does necessarily use less resources... it is that it can use less resources... out of the box. Just because some people choose a distribution that is bloated by default doesn't mean Linux is bloated or getting bloated. The Linux kernel is still relatively small. Whatever you decide to use beyond the kernel is up to you.
"THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
I buy computers for a large university in Virginia. Engineers, Bus, CS and Arch majors now must have a minimum of 1GB of RAM. This will get them through 4 - 5 years of college. It costs an extra 250.00 to buy a Dell D600 Latitude laptop with 1GB of Ram instead of 512MB.
/. have posted this, but it needs to be said until all of the idiots out there that contiunally talk about "running Linux" get it through their thick, ignorant skulls. One should say that a Linux based OS that uses KDE is bloated... that would be true, but saying "Linux" is bloated is misrepresenting the issue entirely.
What's the problem? RAM is cheap and fast. It's natural to see apps such as KDE and Gnome and the Windows GUI use more of it.
Also note that "Linux" is only a kernel... not an OS. Many on
Err, no. I've used more window managers under various *nix systems over the years than I care to count including Openview, Motif, Openlook, DCE, fvwm2, blackbox, WindowMaker, KDE2, KDE3, and Gnome.
They all run fine if you shut off the extra eye candy, fade/slide effects, transparency, skinning images, etc.
There are no CD player docklets on my desktop, nor midi managers, MP3 rippers, or anything else that wants to periodically check to see if it needs to do anything. If I need it, I'll start the app required at that time.
In other words, modern window managers give you the option of leaving all the glitzy CPU-wasting eye and ear candy enabled, or you can have it fast. Even WindowsXP has the same problem -- you have to shut all the junk off before it'll respond with any kind of speed.
As to memory requirements, I'll just point out that the window managers being compared don't include all the audio and internet hooks that KDE or Gnome do. Modern users expect those hooks, and they take space. Get over it.
I do not fail; I succeed at finding out what does not work.
Just because someone has no need for a gui doesn't make them elitist. The grandparent post was mainly refering to experienced computer users. Obviously a beginner needs more help, but experianced users who use DEs (I use Gnome myself even though I like to think of myself as hardcore) do it mainly because it looks nice and it has gimmicks, that's why I have always either used Gnome or KDE and am not planning on giving them up.
One can achieve a lot through a text interface, it is not the only way to do things, but it is a legitimate way to do things, and for many people it is the most efficient way to do something. File operations are especially fast from the console. Things like spreadsheets and video editors can be invoked through the console with FVWM just fine.
I agree with the grandparent. If you have the skills to live without one, using a DE is a personal preference. I have chosen to use one because of my playful instinct and the grandparent has chosen not to use one because of their desire for efficiency. These are both legitimate causes of action.
When Argumentum ad Hominem falls short, try Argumentum ad Matrem
RTFA.
The point of the article is that mainstream desktop distros are not any better off than windows xp in terms of requirements. Therefore, they cannot be used to replace windows 98 instalations on corperate desktops and as a consequence linux is losing a major oppertunity. That is the only point the author was trying to make.
Well.. maybe. Or Maybe not. But Definitely not sort of.
If you can start typing in the WORD PROCESSOR, it's pretty much ready to use, isn't it?
Running old distributions is not a great idea. Remember all those security notices that you ignored? Well, they didn't go away. Old (unupdated) Linux distributions make great targets for script kiddies.
TZ
This is the same ol' get-out-of-zealotry-free card that gets slung around on slashdot. is slower than the big bad alternative? Pah! is faster, but looks slower! So there!
Please.
We can't expect KDE, GNOME, or OO to suddenly trim down to where we can run them on old PCs. Someone else will need to "scratch an itch" to accomplish this task. If we are thinking of third-world countries, I would think that there are certainly enough programmers in those areas (considering the outsourcing boom) to accomplish this mission.
And I'll say it again. KDE and GNOME not only want the broken UI behaviors of Windows, but the bloat as well.
If you look at the Amiga, RISCOS, and (for the most part) the Macintosh, they achieved unbelievable usablity not because they had flashy libraries or k3wl tr4nsp4r3nt t3rm1n4lz, it's because they use the hardware well and tried to give a small, innovative UI to the user. Just because their not mainstream you might not see them, but look at XFCE and ROX. Both are desktops (hell, ROX is trying to write our own desktop apps) that take the GTK libraries and make fast, powerful, and small desktops that do their jobs and do them well. Not only are their easier to debug, they are easier to use and faster even on dated hardware because they are not trying to be the massive beasts KDE and GNOME are pushing them to be.
You will not see ROX push a web browser into ROX-Filer. You won't see XFCE do alpha-blending in the dock. You'll just see programs that do a job, and do it well. With GNOME's main library.
They follow the UNIX way which has been lost on the big desktops and it shows.
For a example of how bad the big desktops are at deciding where to put things, look at the fake SSH/FTP/HTTP/HTTPS things in KDE via FISH, and GNOME via GNOME-VFS. THESE SHOULD NOT BE DONE BY THE DESKTOP AT THE LEVEL THEY ARE! They should be pushed to a small userland daemon at best, or a small combination of userland and kernelspace at worst. This way all apps could use them seemlessly and without the massive overhead of bringing in Yet Another Library, including current commandline tools, without changing a line of code. It's simple things like that that bloat them, and as they act as a point of code "contention," hurt them both because it forces KDE developers to work on one implementation, and GNOME developers to work on another.
And for the last time, UI and library bloat != UI ease of use. Just look at the old Macs. If a interface is correctly done, even if it bares no resemblence to a existing one, the time to relearn it should be trivial.
... to put it mildly.
I see exactly the opposite, and so do my coworkers, who primarily use Windows. Starting a year or so ago, they've all been pushing hard to get us new laptops with 1GB of RAM, because the tools we use just don't fit in 512MB... on Windows. On Linux, I can run DB/2, Websphere Application Server and Websphere Application Developer in 512 MB without hitting swap... with swap *off* if I want to, whereas their machines with the same stuff running grind continually.
(Note: To run with swap off, I have to use a different Window Manager... KDE pushes me over the edge and into mild swapping -- nowhere near as bad as on Windows, however).
As far as the size of KDE, well here are my numbers: With Linux 2.6, X and blackbox running, my laptop (Debian unstable) consumes 28MB of RAM just after boot, excluding disk cache and kernel buffers. With KDE 3.2 instead of blackbox, that number rises to 114MB, and that includes a hidden Konqueror instance, a bunch of systray apps and one GNOME app. So KDE plus some GNOME consumes 86MB more than blackbox, which is a very minimal WM. That's a lot, but it's hardly "hundreds and hundreds" of MB. Starting openoffice pushes that up by another 20MB. Mozilla (full suite) is about 40MB.
Getting back to the Windows comparisons, with Linux and KDE, my system runs acceptably well with 128MB of RAM, swapping a bit, but not too badly. With Windows 2000 it's horrible with only 128MB. It boots up okay, but as soon as I start trying to run more than one app... ugh.
With 1GB (hey, I may not *need* the RAM like the Windows users, but I'm not going to turn it down!) in my new laptop, I never yet seen my box even touch the swapfile, even with KDE, Mozilla, OpenOffice, WS, WSAD and a couple of small GNOME apps running. After being up for a while, I always see nearly 100% of RAM in use, but that's because Linux uses it for disk cache, which is a good thing.
Meanwhile, my colleagues running Windows can push their 1GB machines into swap -- although it's difficult.
Since my basis for comparison is machines running a certain set of heavyweight development tools, it's possible that the difference isn't actually Linux/KDE vs Windows, but rather the implementation of those tools on the two platforms. However, since the bulk of the tools (and the part that consumes lots of RAM) is all implemented in Java, and therefore is the same code, it's hard to see how the tools could differ that much across the platforms.
So, I'm not saying you don't see what you see, but something is clearly different, because I see completely different behavior on both my Debian and my Gentoo systems (the Gentoo box consumes less RAM than the Debian boxes for the same set of running packages, at close to the same versins).
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
It's a mistake to paint it in broad strokes and say the Linux desktop is getting slow. One type of approach to a desktop is slow.
Yes, we will, it's just that my "we" is different than your "we." But he knows this: Yeah, they don't rival them, in the sense that they don't suck enough.Obviously, when I say Evolution sucks compared to Sylpheed, I'm speaking from a certain point of view. But when he says Evolution is better than Sylpheed, so is he: he's talking from the infiltration point of view. Ok, so infiltration is having a problem. But let's just be honest about the limited scope and premises behind what we're saying, ok?
Oh, and..
This isn't a realistic expectation. The Amiga is never going to be matched by anything mainstream; not enough people care about snappiness for there ever to be a sufficiently critical-mass market. But the better Linux desktops (not Gnome and KDE) can get to within a factor of about ten, and given the hardware situation (a machine is now considered "old" if it only has ten times the processing power as the fastest 68k Amiga) that's good enough. But quit expecting it from Gnome; Gnome's goal isn't to be like an Amiga, it's to be like Windows. Did Miguel ever say he was trying to make an environment that the huge Amiga market would comfortably migrate to?Now I just gotta find a file manager comparable to DOpus 5.x...
As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
Yes, I think that's the point, and that a lot of people didn't read the article - it's not that both Windows and Linux desktops are getting fat (they both are), but Linux with one of the two major desktop packages is actually performing WORSE on the same hardware, with debatebly less features.
It used to be that you could argue that you could take that old machine and instead of throwing it away and buying a costly new system, or spending a lot to upgrade it, you could just switch to Linux and get the same or better responsiveness as Windows running on a new box.
Now it's reversed itself. Keep in mind we are limiting the subject to the big two Linux desktops, which are what a new user would be expected to use.
Stupid sexy Flanders.
Despite all the +5 upmods in this article describing very valid criticism of poorly programmed desktop emulators like KDE, nothing will change.
I've been saying for YEARS how Linux desktop environments are jokes, are bloated, are slower than Windows, and more. I've been knocked down as troll, modbombed, told my opinions are flat-out wrong, and been called a "Microsoft shill" more times than I can count. The fact is a large part of the Linux community will never leave its little shell and realize the truth of things. They're too busy circle-jerking over the latest version of KDE because it "sure shows Microsoft."
All your criticisms are valid, but nothing will change. We'll continue to get bigger and slower versions of KDE and GNOME and XFree86. Nobody wants to change, because a lot of Linux users fear change. We just HAVE to still be able to run xclock, right? Heaven forbid we move off of old technology and try something new.
Linux is always getting feedback like this from users, but developers ignore it. The community will tell you "so where's your patch?" or "don't criticize a volunteer effort." The developers don't seem to have any sense of sanity when it comes to mature, professional desktop design. It's still the same hacky, silly, amateurish attitude from 1998 when these projects first began. I mean, compare the "feel" of using OS X to the "feel" of using KDE. This subtlety is what volunteer hackers working on 20 more sidebar buttons for Konquerer lack.
It's become a penis size contest. "Microsoft has Win32? We'll have Xlib, GTK, WxWindows, QT, Mono, etc. etc.!" The idealistic "freedom of choice" absolutist mentality was a neat idea for the magazines in the late 90s when Linux was a poster child, but that era has died and gone and now it's about RESULTS. No, you don't need two desktop environments. Any sane individual would see that we have wasted over half a decade in spreading our efforts across two desktop emulators when Linux needs one really good one. Think in terms of a project manager--would you have your teams working on two projects that do the exact same damn thing in order to give your customers "choice" between them? No, you'd combine efforts to make the single product you put out extremely good, so the user WON'T NEED to choose anything else. Because in all honesty, copping out to the choice excuse is just laziness being justified with ideology. "But this is how we've done it since the late 90s! It's all about choice!"
Everyone wants to reinvent the wheel. Everyone wants to do things a different way. The result is this massively huge mess of desktop incompatibility that looks completely unprofessional to everyone outside the niche communities that embrace it because it's "not M$." When someone like me brings up the need for standards, there is always the requisite freedesktop.org reference, even though fd.o has done jack-shit to bring KDE and GNOME together. When exactly does this mysterious combining of standards occur? It's all hype to shrug off criticism.
Think of all the time that's been wasted. We could have developed one incredible development library, running underneath one incredible desktop environment. Commercial apps might have existed by now because they would know they could put out a binary installer (you know, since there would be a binary installation/uninstallation API instead of relying on whatever hacky package manager exists on the command-line) that would always be able to install and run on the environment. You know how you can run Office 95 even today on XP? Companies need that kind of assurance, as do consumers.
It would be one thing if people just admitted where things really are. "We do have a lot of redundancies and amateurish approaches to these solutions, but someday we do plan to get there." That would at least be respected. But no, it's "KDE and GNOME blow OS X and Windows out of the water! There is absolutely no reason to use anything else!
Desktop Linux will never happen until dependancies can be quickly and easily resolved (even if it means each app that would run comes with its own copy of every library it needs and keeps it in its local folder -- Windows style) and there's no building from source.
./configure;make;make install type things. Too complicated for regular people, although not too bad for people like us.
Windows works the way it does because the Kernel is virtually unchanged during updates...the external API and syscalls don't change. (XP SP2 changes a few of them to be more secure, that is however, the last time I can remember an API change in the middle of a revision.)
Linux desktop already works for basic stuff -- but to be a truely multipurpose desktop, we can't have desktop users futz around with dependancies, compling from source
It is one registry key!*
Ye gods, I mean, most shells' installers even change the key for you!
Mind you, this is coming from someone who is using Litestep as a shell and a heavily modified command line as a file manager, but come on... no need to exaggerate what you just did. Maybe it is just because you were too "anti-Windoze" to realize that Windows is actually not nearly as difficult as you make it seem. Linux isn't that difficult either.
*(This is, of course, only for NT4/2000/XP - Under a 9x, you don't even open the registry to do it!)
--- Ãther SPOON!
I'm not pretending that OpenOffice.org isn't slow at getting started. In fact I wrote precisely that in the last paragraph of my parent post. On my A31p Thinkpad, OpenOffice.org Writer takes 8 seconds to pop up the flash screen and a further 8 seconds to complete loading on the first attempt. Once cached, a reload takes 1 second to pop up the flash screen and 2 more seconds to pop up the main screen. Loading an entire Word processing application from disk (not cached memory) in sub-second time isn't possible on todays machines without some tricks, whether they be file caching, library pre-loading or popping up the window to give feedback to the user even though you can't actually start using that window for several more seconds.
Note also that my parent post said a Default MS Word install. Not a customized install. Most people breeze through the install clicking next and leaving the defaults alone so Startup wizard is almost certainly on for most MS Word users.
Cheers,
Toby Haynes
Anything I post is strictly my own thoughts and doesn't necessarily have anything to do with the opinions of IBM.
As a previous poster said, if a GUI system "feels" slow, it is slow. If the system "gives the impression" of being fast, it is fast.
The only evaluation criteria of a GUI is user perception, not "number of widgets per second" or "number of window moves per second". User perception is notoriously hard to measure, however, so people tend to revert to the "number of X per second" style measurements. Such measurements are useless, unless they can be tied to user perception (such as "more widgets per second makes the system feel more responsive").
The idea of this post needs to be strengthened: this is how the standard software development cycle works; first make it work, then make it work better. In this case the 'it' seems to be catching up to the Windows desktop; we can argue whether this is a good goal, but it seems to be a necessary goal that is getting a lot of broad attention.
Think about how open source development works -- the single most important issue is 'Is there a way to do it?' That's what matters -- you're cool if you find a way to solve a problem. Initially nobody cares if the solution is inefficient. Only later, when things are more stable and there are relatively few complaints about lack of features, do performance and efficiency become important.
Let's face it... the linux kernel is much farther along the optimization curve than the GNOME/KDE projects and OpenOffice; GNOME/KDE and OpenOffice are still throwing out major new functionality left and right with all the inefficiencies inherent in that process. Only when the user interface issues stabilize, meaning all the necessary functionality is basically there to compete with Windows, will thoughts turn to issues of performance and efficiency. For me personally, the point where the Open Source desktops were good enough was passed several years ago; perhaps this thread indicates it's been passed for a much larger number of people as well.
Here's an idea specifically for GNOME/KDE to chew on: the UI should be like a typical game and adjust its behavior to the resources available on the machine -- an old machine with few resources should not even attempt animations or textures, while a new machine with many resources could. A mature UI should be able to adjust to available resources to optimize the user experience.
Similarly, the OpenOffice people are aware of the speed problems, and are balancing them with cries for important features.
More generally, this is just standard software development -- get it working, then get it working well.
The only reason we can even hope that Open Source will work better than Windows in the long run is that ideally Open Source will settle around proven long term stable solutions which will be polished to work very well (such as the Unix-style influences with the proven 30 year track record), rather than the Windows world which requires the upgrade treadmill to generate revenues and constantly writing new code for solutions in search of problems. If Open Source development continually thrashes around on the feature treadmill and never settles on stable solutions, there is no reason to expect Open Source to be any better than commercial. Let's hope that GNOME/KDE are simply in the process of converging toward a fairly stable idea of what a 'modern desktop' is, and OpenOffice is converging toward a fairly stable idea of what a 'modern office suite' is. Beware the Microsoft strategy of competition by feature war and constant distraction with new technologies -- not every feature and technology is important.
i would have let it go but... who the hell wants to worry about object frameworks? i want a system to run my applications without me worrying about the way they were developed. i want to start a bunch of applications and do multitasking without any of those worries. remember, not every person who uses a computer is a developer.
I'd have to say that I am not only more productive on a computer because it's easier to learn new tools, but that the gui itself is one of the main tools I use. I use the desktop not only to switch between apps, but as a clipbook/news reader/clock/media player, and only do so because it it is convienent enough to not interfere with "work" I have to do on the same machine. Those are tools I couldn't take advantage of in a CLI-only space.
As a new linux user, I find it horrifically interesting that there aren't any(?) DE's that allow one to work without a shell. Constantly, one has to open command shells to perform trivial tasks. When adding that to learning a semi-functional DE, I understand why so many people are linux-shy. I must give props to Kuake for taking some of the sting out of this, but it seems it should be in every distro's default DE, since they require a terminal so much.
This may lead to a bit of hatred from both sides, but the complete integration of basic UI (classic), graphic features (skins) and a command line (adress bar, command prompt) in XP is one interesting solution. Additionally, the XP installation takes a more friendly approach to what a user's GUI should look like for them: By default all the graphic bells and whistles are "on" and can be turned off by those experienced and inclined to do so. I think this is an important advancement over a typical linux distro's philosophy, which has a lot of features (sub-pixel blending, etc.) "off" by default. Users inclined to seek these features are those least interested in using them.
Despite all the windows-bashing here, perhaps people should appreciate what they have done well (as well as bash their wicked ways). A great solution would be a new linux based GUI that offers 100% of shell functionality (and no prettiness), rather than "live on top" of an existing CLI, and then develop optional graphic touches as a layer above that. This would scale as well, or better, the current MS offering. Graphic flourishes could be added later in a consistent and pleasant manner.
Looks good for your age..
Why not use the Win Key, instead of these fingers stretching key combination ? Why not just use that very Win key just for the Window manager, and keep the other ones (Ctrl, Alt, Meta, Compose, Whatever) for regular applications, since regular applications usually depend on these anyway ?
When I first started setting up linux as a server and as a desktop (rather than just fiddling with it), we had the brand new 1.2 kernel series, and X11R4.
./setiathome -nice 19 /usr/bin/gnome-session /usr/local/pgsql/bin/postmaster /usr/X11R6/bin/X
Back then, we built a 486/133 machine with a whopping 16M of RAM, and an uber-l33t Vesa Local Bus video card (3dfx #9, if I remember correctly).
Loading up a dozen text shells, a copy of netscape with several windows open, xpaint, emacs(!), and a few dozen copies of xeyes... it REFUSED to swap!
We were finally able to get it to swap by loading GNU Chess and having it play itself (which forks a second copy and talks over sockets).
Our first server was "tested" with 4 Megs of RAM and a copy of DOOM under both DOS and Linux. The linux version performed better.
Now, given that the 1.2 kernel could perform remarkably well with X windows and netscape, for what should be considered a "normal" workload... why is it that virtually every distro I can find today feels like a salt-crust grill with molassas syrup and eats up enough ram just sitting there idle to choke Bill Gates's horse?
From my whitebox linux desktop at work, here are the top 10 Bloated Sacs running right now...
VSZ RSS START COMMAND
18020 15216 Mar10
18384 2560 Mar08
18504 1020 Mar23
19476 668 16:26 sort -n -k 5
22692 6736 Mar08 gnome-panel
36088 5096 Mar08 nautilus
36736 14344 Mar08 gnome-terminal
69616 38132 13:28 thunderbird-bin
76276 47712 13:34 firefox-bin
116172 40324 Mar04
Note that this is 40+14+5+6+3 = 68M of RAM just to allow me to have a prompt. Yes, I know I could stop using gnome, but that only trims the outside fat.. the marbled fat inside X11R6 and the mozilla twins are harder to get at.
Do I get MORE done now with all this cr@p running than I did 10 years ago? Nope. Do you?
That would be good UI design, hiding the load times from the user, as long as that feature does not create new errors. We are not discusing some race, it's about the time, and the experience of the user.
On a dual-boot Fedora/XP 2600 Athlon I administer the difference is staggering.
Boot time (from GRUB menu to login screen):
Windows XP/Lunar: ~20 seconds
Fedora/XFree86/gdm: ~1.5 minutes
I don't know what Microsoft do, but they've tuned their boot process something wicked.
Granted, a stock Fedora install runs a whole lot more services (apache, sendmail), but I'm sure it can be much faster.
Many services don't need to run in series. For example, the random number generator can be started while ethernet discovery is taking place, or sendmail can start up while X is probing the monitor. Similar reasons why a 'make -j4' runs so much faster than 'make'; the two bottlenecks when compiling (or loading an OS), cpu and disk, just aren't being used the whole time, one is usually waiting on the other at any given time.
Time to experiment with the & parameter...
"Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
You've hit the ol' nail on the head there, Slashdot will always have people who bitch and moan about something.
However: The thing is that a large chunk of comments and articles these days on Slashdot are about 'Linux becoming mainstream', 'This year is Linux's year', 'Why the f*ck isn't the entire world using Linux dammit?', 'Windows suxxors'
So, the retort to the increasing realisation that each year that Linux is supposed to be 'the' desktop environment that slips by with it still floundering is: 'Make Linux usable for the average desktop user'.
How do you do that?
Make it have an easy to use interface that is attractive and does everything the 'average' user wants...
No, Windows has this... bitch and moan as much as you like about MS, but their interface works pretty darn well... people seem to be able to pick it up pretty well.
"But, but look at those system specs you need"
OK, so do better.
Guess what?! Linux is finally getting desktops that work in a similar fashion, and they TAKE UP RESOURCES!
You don't get things for nothing people... you're starting to see that maybe MS isn't quite as stupid and incompetant as you've always believed... that maybe it's not quite as bloated as you first believed... Hell, you've had the open source community slugging away at this for... how many years now? and they haven't really done any better... so give them a break and rather than trying to convince everyone that Windows really is shit, create something that comparable.
Most people don't distinguish between the apps and the desktop. People think of the computer as an appliance which does various tasks, not as an app on top of a desktop on top of a WM on top of a windowing system on top of a C lib on top of a kernel. The GNOME and KDE teams are trying to improve the overall user experience.
This bullshit where GNOME is adding P2P and blogging, and KDE thinks it has to have 20,000 sidebar buttons and configuration panels on everything is completely ridiculous and unnecessary. All that stuff is supposed to be taken care of by the app writers.
It is being taken care of by the app writers. Who do you think wrote the p2p and blogging apps? They didn't just pop out of thin air. You sound as if you think it's a bad thing that such apps are available.
It's hard to be religious when certain people are never incinerated by bolts of lightning.