Comment by jff
13 years ago
Ah, that explains Ruby's concurrency situation.
(It's a joke, I understand the difficulty involved with concurrency in interpreted languages. But given that both Elisp and Ruby are well-known for having trouble with threading, well, too hard to pass up!)
Actually there is nothing about interpreted languages which makes concurrency particularly difficult other than their history.
As an extreme example, you can run Erlang as an interpreted language and concurrency will not be a problem.