JM: We made improvements in the .Net Framework 2.0 to be able to do dynamic calls. We’re looking at ways that we can make dynamic languages friendlier, but it’s certainly not unfriendly to dynamic languages right now. If you look a Jim Hugunin’s work in IronPython, you’ll see that there’s some really good things. In fact, that’s why he came to join Microsoft.... He turned around IronPython in a pretty short time frame, so it shows you that it’s not unfriendly.
IW: With these projects Phalanger and IronPython, does Microsoft actively support those with developer resources?
JM: No, we don’t. They’re very much driven by the community.
(Editor's note: IronPython started as a community project but has since been brought into the Microsoft fold).
IW: Is there a short list of specific dynamic languages that you guys are working to extend support for or to make easier to run on .Net?
JM: Not at this stage. We’re kind of looking at how dynamic languages in general can run better. So it’s really done in exactly the same way as CLR is common across languages. But that’s same sort of work we’re doing, or thinking of doing, for the runtime.
IW: So whatever improvements or tweaks you make to the CLR for dynamic languages should extend to any dynamic language?
IW: So you don’t envision a Microsoft version of PHP or Perl or any of these? You’re going to let pretty much the outside developers take care of that?
JM: We haven’t made any firm plans in that direction right now…. The .Net Framework should really be seen as an industry leader in enabling these sorts of languages. We’re constantly evolving it. It’s at Net Framework 2.0 right now, 3.0 will be out with Vista. [Version] 3.5 or something like 3.5 will be out with the next set of tools that we release. So we’re constantly improving, always looking for what’s important in the industry and from our customers. And you’ll always see us evolve this and do some innovative work.