
John Lam About IronRuby
In this interview, John Lam, Program Manager on the Dynamic Language Runtime team at Microsoft, talks about IronRuby, what it means to .NET supporters and how it has been received by the Ruby community.
Tracking change and innovation in the enterprise software development community

In this interview, John Lam, Program Manager on the Dynamic Language Runtime team at Microsoft, talks about IronRuby, what it means to .NET supporters and how it has been received by the Ruby community.

Zed Shaw and Matt Pelletier sat down with InfoQ's Obie Fernandez at RailsConf to explore some of the reasoning behind setting up the mongrel project, getting adoption in enterprise and dealing with developers who just aren't ready. Watch the interview to find out how much Shaw's Enterprise Mongrel product will cost, where the support contracts are and who'll come out on top when the vultures land.
A recent article by M. David Peterson on the O'Reilly Network entitled "Ruby.NET vs. IronRuby: What's the Difference" received the attention of John Lam, leader of the IronRuby project at Microsoft. John follows up David's article with some clarifications of his own with respect to IronRuby.
Microsoft has announced that they are building an extension to the Common Language Runtime called the Dynamic Language Runtime (DLR). This extension is being designed to enable interoperability between dynamic languages in the same manner that the CLR enabled interoperability between statically typed languages.
Microsoft has just announced IronRuby at their MIX 07 conference. This also kicks off a bigger effort to support dynamic languages on .NET. Based on the experience gained in developing IronPython, a common Dynamic Language Runtime (DLR) builds the foundation for IronRuby, IronPython, JavaScript (EcmaScript 3.0) and Visual Basic.
John Lam, the creator of RubyCLR, has accepted a position at Microsoft. While he hasn't yet revealed his new duties, he has stated that he will not leave the Ruby community.