IronRuby is out, Built and Running

I have been working with Ruby for quite some time now and every time I hear of new things out I like to try them out.  Most of the time it is the latest gem or technique but this time the news comes from Microsoft.

John Lam and his group at Microsoft released a source code drop of IronRuby, which is a version of Ruby running on the CLR.  IronRuby is promised to give us all the power and compatibility of Ruby 1.8.6 with all the goodness of the .NET 2.0 Runtime and beyond.

IronRuby is an open source project and will end up on RubyForge but for now is available as a download from John’s blog.  So, I downloaded, unzipped and ran the included Build.cmd and viola…


It built in just under 3 seconds….

I went to my command prompt and to the release directory and ran the resulting rbx.exe and saw the familiar >>> of Ruby’s IRB.

I tested the Ruby implementation with a few commands just to see what resulted and everything I ran worked very well.  I didn’t do any work with using .NET classes, but I will.

One interesting item I noticed was this….can you see it?


In Ruby, typing something like “Hello”.class returns a type String but in IronRuby you can see it returns MutableString which is an interesting distinction from .NET, who’s strings are immutable.   I like the attention to details like this.

I will be running some of my utility classes with IronRuby and throw together some samples that integrate to the CLR.  I will also report back what I find.  All-in-all, it looks pretty good.

Technorati Tags: , , ,


2 responses to “IronRuby is out, Built and Running

  1. I’m glad that it worked well for you out of the box! The MutableString reporting will change to just String in the future. But if you look in the MutableString.cs file, you’ll see that our implementation is currently built around a .NET StringBuilder. In the future, it will evolve further, and become a byte array for maximum compatibility with Ruby 1.8.x.

  2. Yes, I noticed it was built around StringBuilder, very nice. I thought that would be the implementation going forward but the byte array is an interesting approach.

    Is there a public timeline for future releases and feature completeness with Ruby 1.8.6?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s