I know this has been discussed even in the locked thread of myths and facts about WB, but I had to point out that when I unload WB, my memory commit charge (which is how much total physical and virtual memory your PC is using at that instant) drops by about 20Mb. So, it is not fair to just point to the wbload.exe process and say, "Lookies, it's only using 1.3 megs!" and brag. You need to check how much total memory is required to change your windows from the boring look to the fancy WB look. I am not saying 20 megs is still too much. If I thought it was, I wouldn't use WB on my home and work PC (where I run a SQL server along with a variety of other services full-time).

Anyway, just to get the record straight.

Cheers...
T.