Early look at IronRuby

Today we shipped the first source code release of IronRuby.


Both IronRuby and IronPython, released earlier this year at MIX07, target the Dynamic Language Runtime (DLR).  The DLR makes it easier to create high-quality, high-performance dynamic language implementations on .NET.  DLR-based languages make it easy to interoperate with the .NET Framework, as well as code written in other .NET languages.


The source code for IronRuby is released under the Microsoft Permissive License. The project will be hosted on RubyForge, the central source code repository for the Ruby community. We will also be accepting external contributions to IronRuby libraries initially, and expanding that offering to the entire IronRuby compiler once the Dynamic Language Runtime reaches 1.0.


You can also find out more about this from Scott Guthrie’s blog on IronRuby.



Comments (3)

  1. Jared says:

    I will be very interested in seeing a write up on the benefits and costs of Dynamic Language Runtime (DLR), specifically regarding actual performance, maintainability, development costs, etc.  I know some complexity overhead exists with .NET, and I will be curious is this overhead becomes greater when Dynamic Languages leverage .NET.

  2. Somasegar says:

    Have you checked out Jim Hugunin’s blog?  He has got a couple of very informative blogs on DLR.  



  3. Josh Nursing says:

    It’s quite a feat, considering that there is support for WPF through .Net 3.x and also for Silverlight. If, however, IronRuby is extended in such a way that it becomes incompatible with Ruby, then observers will cry foul with good reason.

    I have written a detailed tutorial about hacking IronRuby, including how I fixed a bug and how I extended it using Visual C# Express 2005, IDE for more comfortable development and debugging: