I was checking up on Anant Jhingran's blog and noted that he mentioned Erlang so going back up to the top realized that he was discussing a post from Sam Ruby. Sam is discussing a set of "long bets" although some seem pretty short bets to me. It also seems as if Sam's posting caused enough of a stir to cause an apologia posting :-) I agree with Sam's comments on Erlang, and while the world probably doesn't *need* another programming language I do think we can learn from the set of languages out there and in the area of concurrency I think there are lessons we need to learn.
I also try and separate out language, VM and library as Sam does, so I do like the .net CLR as a VM mainly because a lot of thought about the kinds of languages planned to run on it was done before implementagtion; this means adding Python (IronPython), Ruby (IronRuby) and others has been interesting to watch. As for languages I think many of my preferences are known, but as a collector of programming languages I am probably not an objective source.
One comment on Sam's apology mentioned Stackless Python, something I was planning to write a posting on myself some time. The difference I see is that stackless is an enabling feature of the VM, that we will still need the language-level primitives for message send/receieve I see in Erlang and then library support for managing local and remote distribution.