Sam Saffron wrote:
IMHO, "Threads are like goto" is a little harsh ... But the more I think about it a well implemented actors model http://en.wikipedia.org/wiki/Actor_model seems way more attractive than threads. Go Rubinius :)
A: Use spawn. We threw it at work at a silly problem that required one process to depart the Rails action handler, and just do its thing and quit without telling us how it went. Very clean! B: If two threads depend on a semaphore from each other, you get the worst possible kind of coupling. The private details in the waiting module depend - at runtime, not compile time or test time - on the private details inside the blocking module.
