2007
KDE 4 use much less RAM
Anyone paying the slightest attention to the Linux-on-the-desktop scene will have noticed that desktop environments are featuring more and more eye-candy with every release. While this has had the predictable effect of increasing processor usage and memory requirements (although the pretty things can always be turned off), it seems that the newest version of the K Desktop Environment graphical user interface will use nearly 40% less memory than current version 3.5 despite having a lovely composited windows manager (think Aero but free). The figure comes from a test run by German magazine Pro-Linux who ran tests comparing the performance and memory footprint of the second release candidate of KDE 4 compared to the latest version of KDE 3.5.
With further good news for those of you with older systems to support, KDE developer Will Stephenson announced in a post to his blog that he’d tried a pre-release build of KDE 4 with the 3D desktop effects enabled on a laptop running at 1GHz and with only 256MB of RAM. Rather than the single-frame-per-second slide show he was expecting, Will was pleasantly surprised to find the desktop completely usable even with all the glitz and glamour turned on.
It’s also worth noting that Will had some KDE 3 libraries loaded for compatibility reasons, and that final optimisation of the code has yet to take place: in other words, there’s room for still more performance gains.
The finished version of KDE 4 is due for release on the 9th of January 2008. If you can’t wait that long, you can grab the source for the release candidate from the KDE website.
Source: bit-tech
The 2007 Microsoft Office suite Service Pack 1 delivers important customer-requested stability and performance improvements, while incorporating further enhancements to user security. This service pack also includes all of the updates released for the 2007 Office suite prior to December of 2007. You can get a more complete description of SP1, including a list of issues that were fixed, in the Microsoft Knowledge Base article 936982: 