Re^6: CLONE/DESTROY want work at all??

Threads are always a huge complication, ...

... "Perl is always slow"; "football fans are always hooligans"; "blonds are always dumb"; and "mindless generalisations are always pointless".

One of the above is true.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Comment on Re^6: CLONE/DESTROY want work at all??

Replies are listed 'Best First'.
Re^7: CLONE/DESTROY want work at all?? by tilly (Archbishop) on May 22, 2009 at 20:43 UTC
How is having a computer doing 2 things at once not more complicated than having it do 1? Furthermore figuring out the failure modes generally involves figuring out sequences of different threads hitting specific interactions. Threads are useful in figuring out how to use the maximum CPU power you can, and for solving latency issues. Threads are sometimes the simplest way of coming up with a solution that does what you want and addresses those issues. In those cases it is appropriate to use threads. But even in those situations the presence of threads is a complication in the code, and many (probably most) programmers are poorly equipped to properly deal with them. So I'm never going to suggest a multi-threaded solution unless there is a specific reason to think that they address a real problem which you have.	[reply]

Replies are listed 'Best First'.

Re^7: CLONE/DESTROY want work at all??
by tilly (Archbishop) on May 22, 2009 at 20:43 UTC

Threads are useful in figuring out how to use the maximum CPU power you can, and for solving latency issues. Threads are sometimes the simplest way of coming up with a solution that does what you want and addresses those issues. In those cases it is appropriate to use threads.

But even in those situations the presence of threads is a complication in the code, and many (probably most) programmers are poorly equipped to properly deal with them. So I'm never going to suggest a multi-threaded solution unless there is a specific reason to think that they address a real problem which you have.

[reply]