The apparent poor support for dynamic languages in the dotNET framework is perhaps the most interesting conclusion that can be drawn from this effort.|
The S# story is yet more evidence for this conclusion. S# is the much-delayed-and-still-unavailable-even-in-preview-form implementation of Smalltalk that had Microsoft's backing since the early germ of dotNET. (See http://www.smallscript.com)
These two stories and the Python escapades are damning evidence.
Maybe it's the implementors' choices, or maybe improvements in dotNET are underway. At this point, the sign posts are not pointing in a positive direction.
I suspect Python will continue to grow in popularity until it reaches a point more visible on MSFT's radar and then there will be a concerted effort to get it running in dotNET. Two years after that, say 2006, performance will be reasonable in a production release of dotNET.
Am I too cynical?