|
Originally Posted by Cetra
It's not lighter at all. StyleXPs service size is determined by the theme being used but it keeps the built in WinXP themes service at a constant size. Patching the uxtheme.dll causes the built in WinXP themes service to grow in size. So if you are using a 2 meg theme and the standard themes service uses 5 megs, then a system using StyleXP would have a 5 meg SVCHOST process and a 2 meg STYLEXPSERVICE process. A computer using the uxtheme.dll patch would have a 7 meg SVCHOST process.
They use the exact same overall amount of system resources.
|
You're right. I remember using windowblinds and, after disabling the themes service, flaunting the fact that I was using less memory than users running the default XP setup.
However, with 1gb+ of system memory being the norm nowadays, who's counting? For most computers, the resource difference between uxtheme, stylexp and windowblinds is negligable.
I say that uxtheme is "light" because you don't need a third-party program running in the background. Perhaps "integrated" and "natural" are better words. I don't need any extra software to manage my themes, just the usual rightclick>properties>appearances. I also dislike using any software that costs you money in the first place, and cracks add their own problems with possible bugs, etc.
Of course, windowblinds can skin more things than uxtheme, so it comes down to preference--I personally don't need a ridiculously overhauled visual experience.
On top of that, has anyone noticed that good windowblinds themes are hard to find? It seems like 99% of them are bulky and oversaturated. Good VS themes are still difficult to come by, but just not as much as how WB themes are.
How ya doing, buddy?