--- Geoff Steckel <[EMAIL PROTECTED]> wrote:
> "threads" is a particular programming model of multiple execution
> contexts in a (mostly) shared memory and (mostly) shared resource
> environment which is not cost-effective for producing reliable
> software.
>
Only because people design threaded programs like single
threaded/forked programs. This has obvious results. Once programmers
finally start thinking in threads when they program threaded programs,
the benefits will start to take hold.
As has been said before, the hardware produced today will force this
issue. Multi-core CPU's certainly aren't going away. Nor,
unfortunately, are programmers that refuse to enter (intelligently)
into this new way of doing things.
Quite frankly, I find it rather sad that people who are in an industry
that requires perpetual learning refuse to learn (at least this). Why?
Because, it's difficult? Seriously, adapt or die.
best regards,
Reid Nichol
President Bush says:
War Is Peace
Freedom Is Slavery
Ignorance Is Strength
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
