With the recent "high profile" exit of Jimmy Schementi from Microsoft, IronRuby looks to be in trouble. At least it looks to be in danger of being "put down" from a Microsoft resources perspective. If you’ve been following my blog for a while you’ll know that I am a fan of the Ruby language, and I love the fact that we now have a working Ruby implementation on the .NET platform. It really does give us a great dynamic language to add into our arsenal, and I hear occasionally about IronRuby and IronPython both being used as scripting solutions within .NET applications.
Yep, that’s right. Scripting solutions. You know why? Because if you want to write applications entirely in Ruby or Python, you probably aren’t writing on the Windows platform. Native Ruby runs just fine on Windows. So if you aren’t interoping with .NET code, then why would you run IronRuby? Honestly, there aren’t many good reasons.
Ruby and Windows, BFFs?
So, was Ruby good for the .NET platform? Was it a match made in heaven or hell? I’ve heard many people making comments in both directions. Some making claims that IronRuby was made to bring Ruby programmers to the Microsoft platform, and the other side making claims that it was to keep .NET developers from leaving the Microsoft platform. Somehow I doubt that either of these scenarios is very likely.