I guess these kind of experience vary a lot .. so, something like "why does kde feel faster .. on my machine?" would describe the situation better.I've just switched to KDE and everything seems a hell of a lot more responsive. Not as responsive as win mind you, but not that far off either.
nsahoo wrote:I guess these kind of experience vary a lot .. so, something like "why does kde feel faster .. on my machine?" would describe the situation better.I've just switched to KDE and everything seems a hell of a lot more responsive. Not as responsive as win mind you, but not that far off either.
I am yet to see a machine, where windows is more responsive than kde. Seriously! the start menu, right click menu, native programs startup etc, everything comes up faster in KDE.
I am sure the rest of this thread will be full of similar experiences just to counter the claim that flux < KDE << windows.![]()
P.S. If you are talking about startup time of kde programs in flux v.s. their startup time in KDE, then it because of kdeinit processes. If it is different than that .. I am more inclined to believe that it's in your imagination only.
OK .. i believe you .. i guess i was in a flammy mood or something .. had a bad morning sorta ..I think im primarily talking about redraw time when switching virtual desktops. In flux i was waiting comparitive eons for gaim and firefox to redraw, and responsiveness went down the pan when i had a few windows open.
I should perhaps correct myself and state that im finding kopete and konqueror a hell of a lot 'speedy' a combination than firefox and gaim. Which is a shame, because i like msn file sends and i love firefox.

And 3.3.1 is even faster than 3.3 was (they made some serious optimizations to Plastik)tristure wrote:I find it interesting to see that minds are progressively changing towards KDE.
A few months ago everyone would laugh at the simple idea of comparing KDE and Fluxbox speed.
Since 3.3 such comparisons are not as dumb as they used to be.
I don't think KDE is a resource-hog. When my system is up & running, the system is consuming about 130megs of RAM. And that is standard Gentoo with some background-services, framebuffer-console, X.org, KDE with some services, 4 virtual desktops and few apps (Konqueror, Konsole, Kopete) running. And this is a 64bit system, so the mem-consumption is a bit higher than with 32bits.KDE is still a resource hog and it's still really bloated (which is no problem for me, I like that!), but the developers managed a great speed improvement since the 3.3 release!!

There is one other thing... The firefox GUI is written in their XML-UI format, and rendered through Gecko. And this is slow! IMHO the biggest mistake they made (although it makes firefox a quite powerfull and extensible browser)JackDog wrote:Firefox is noticibly slow on my machine. Takes 4x the amount of time to startup compared to konqueror. I know this is because konqueror preloads, but that doesnt change the fact that it loads faster.

Yeah the decision to use that XML UI framework is a little strange given that they want firefox to be atomic and fast. About the only thing that they layout manager helps with is themeing. I have seen/developedon many applications utilize XML layout managers and firefox is by far the slowest. Even compared with Java apps. Usually people dont even realize that an application has a layout manager is in use until they are told.vdboor wrote: There is one other thing... The firefox GUI is written in their XML-UI format, and rendered through Gecko. And this is slow! IMHO the biggest mistake they made (although it makes firefox a quite powerfull and extensible browser)

I believe that is exactly the paradigm that KDE and Gnome are trying to breakemorphix wrote:If you're using linux you should be used to opening up a configuration file and editing it to your linking to have that application/daemon operate the way that you would like.