Whose waiting until dualcores

I feel like something's changed and I missed out on it.

Nearly everything in the past decade should be programmed with at least two threads. One thread handles the user interface, the other threads handle "anything else." Printing, automatic spell checking, POP mail checking, etc etc are all helper threads. Explorer is claiming a few dozen threads right now on my system, from tooltips to form elements.

Only a few programs have NOT used mulbreasthreading properly. Notepad is a good example. It grinds to a halt whenever anything over 1MB is opened. UltraEdit by comparison works like a champ. And surprisingly (to me anyway) iTunes is a threading nightmare. I don't recall any program grinding my system to a halt as effectively and consistently as iTunes.

But anyway, of the dozens of threads in the run queue or block queue, I agree, getting 100% utilization is a lot like bin stacking problems. It still doesn't mean the efficiency doesn't settle in at a favorable number. Even hyper-threading benchmarks look attractive.