I wouldn't call Erlang and Python Blubs.
Probably a lot of them, if they tried. Because Ruby is so poorly specified, I frequently read the interpreter source code to figure out how things are supposed to behave. CRuby is really well-written in some ways and really poorly-written in others. It's poorly written in the sense that it's a painfully slow line-by-line interpreter. It's well written in the sense that the code is very clean and well-organized: I can usually find answers in the source faster than I can find answers in the pick-axe book.
http://www.welton.it/articles/programming_language_economics...
One of the reasons we try and convince other people to use our tools.
Source? With the bashing Python is getting because of the GIL, it surprises me that someone would switch to Python from elsewhere for any reasons related to threading.
Straight from PG:
"Incidentally, the last straw, I've been told, was some bug in CMUCL threads that kept making the system crash."
http://groups.google.com/group/comp.lang.lisp/msg/574d19d5e7...
From Reddit: http://blog.reddit.com/2005/12/on-lisp.html