Linked by Thom Holwerda on Sun 5th Nov 2006 17:40 UTC, submitted by bmeurer
Xfce The Xfce development team is pleased to announce that the second and hopefully last release candidate of the upcoming Xfce 4.4 desktop is available for download now. The release focuses primarily on bug fixes and optimizations; see the release notes for a complete list of changes. The source tarballs and the graphical installer are available from the download page.
Permalink for comment 179139
To read all comments associated with this story, please click here.
RE[7]: Hope
by cyclops on Sun 5th Nov 2006 22:26 UTC in reply to "RE[6]: Hope"
cyclops
Member since:
2006-03-12

Shakes head. I am not going around in circles. Your statement is faulty. I have stuck to one kind of bloat. Feature bloat.

A new theme is not bloat. I can't even think where you are coming from with that.

There are many types of bloat, you mix and match them at will. Thats my problem.

Feature Bloat example Netscape too many features detract from the purpose of file browsing.

Code Bloat example Vista so much code to manage, unstable. BTW in your first example you talk about dependences. Dependences mean less code bloat

File Size you picked it apart from compiler optimization binaries make up a tiny fraction of a system and often contain debug information that you can strip. It can be an indication of code bloat, but really its not a good one.

Memory footprint. This in itself is a strange one, because it plays against your other mention start-up time. XFCE allows you to load into memory KDE/Gnome Libs to allow those programs to load faster. There is all kinds of caching for speed. It often comes down to Total Memory Size vs Hard Drive speed. The only real problems are memory leaks, and duplicate items in memory, look at how Gnome is trying to reduce it memory footprint.

Application Bloat. Give it a name Windows intergrated explorer, WMP into Windows...they are always there and cannot be removed. This is your problem XFCE does not integrate them you can pick your own media player or browser, you can even pick your own calender application, file browser and replace the old one completely, and they need not be loaded into memory at startup.

your throwing different definitions of bloat around to justify your statement, and hoping one sticks, the harsh reality is often these things are at odds with each other CPU Usage vs Functionality vs Code Bloat vs Memory footprint etc etc. Its complex.

Which is why I like the simple statement.
"All the features you need and none you don't".

Reply Parent Score: 1