Re: threads uber ref-counting. Hit one of my hot-buttons: Threads have got to be one of the most massive WOMBAT boondoggles of the last few decades. Pro) no

Re: threads uber ref-counting. Hit one of my hot-buttons: Threads have got to be one of the most massive WOMBAT boondoggles of the last few decades. Pro) none of this slow inter-process-communication stuff! Con) EVERYTHING is now dangerous. (not quite, but close) But the industry (?) decided "TOTALLY worth it!" I forgot to mention that threads start a little faster than processes (well, quite a bit faster on a particular shitty OS in widespread use), but not so much faster that you won't need to pool and re-use the threads anyway. I think this is one area where Erlang (actor pattern), for instance, gets it right: pretend tasks run in their own process, and use an IPC proxy to send messages between the tasks/sub-programs, even if implemented with threads instead of OS level processes.