Quote:
|
Originally Posted by brackett
While I agree that, in a lot of cases, there's little benefit in multithreading *now* - the dual+ core revolution will soon turn that idea on it's head. The main reason multithreading doesn't benefit a lot of programs is that you're still only able to execute a single thread at once. Dual (and the coming 4 and 8 way CPUs) change that, and multithreading will become the main way to speed up an app.
Hopefully, compilers will catch up and start to multithread optimize on their own. Until that happens though, I'd suggest getting pretty comfortable with threads.
|
You're confusing the issue here. Multi-threading at OS level is a seperate issue from multi-threading at process level.
At the process level its often necessary to have a program with multiple threads, even if they don't actually execute concurrently. For example, you might want to listen to console input while also performing some other computation in the background. And that is important here and *now*.