On old systems, bloat was causing a few megabytes of extra memory access, now it can be 100-400MB. And it's no 11 cycles, but CPUs wait 100's on cache misses, never mind if there's a page fault and disk access involved.
In my experience, it takes 2 generation of software to get things right. These days, you are not going to ask a developer to program in assembler just to get the most optimal memory allocation. The complexity of the desktop environments is going to grow constantly, and this is not a trend one can fight. Same for the underlying technologies, I don't think the devs see too much the memory consumption, many of it is hidden in all the frameworks involved. And often the first generation of a piece of software will focus on functionality and stability, and it takes another generation to profile and optimize. Erik. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org