Jul
3
Ruby.NET Compiler
By Antonio Cangiano. Filed under Ruby
The Queensland University of Technology (Australia) has announced the preliminary Beta release of their Gardens Point Ruby.NET compiler. It is not complete nor something that can be used in a production environment, but I’m going to keep an eye on it.
The opportunity to build .NET 2.0 assemblies from Ruby code has its appeal, and it opens interesting prospectives. For example, I think one of Ruby’s weakest points is its lack of a well done and extremely easy to use RAD tool to develop GUI applications (yes, I know there are a few, but they are miles behind VS.NET). Who knows, in the future this project may enable the usage of Ruby with Visual Studio .NET, Sharpdevelop or MonoDevelop. Furthermore, the integration with existing .NET applications and assemblies may lead to another means by which Ruby can enter into the world of enterprise.
Even if they clearly state on their site: “Please note, that we have so far made no attempt to optimize the performance of our system”, based on a few tests that I’ve run, the speed is good (faster than Ruby 1.8.4 on Windows XP). But a number of basic programs I’ve tried, fail to run given the fact that the project is in such an early stage of its development.
Related Articles:
- Comparing the performance of IronRuby, Ruby 1.8 and Ruby 1.9 on Windows
- Startup for sale on eBay (and it’s a great deal)
- A faster Ruby on Windows is possible (benchmarks for 4 implementations inside)
- Getting MacRuby’s compiler to work
- On JRuby’s importance for the future of Ruby
If you enjoyed this post, then make sure you subscribe to our RSS Feed.
Comments
3 Responses to “Ruby.NET Compiler”























I haven’t played with it yet, but can you post a couple examples of things you’ve tried that DON’T run correctly?
Michael, even a simple:
(1..Math.sqrt(x)).each{|i| puts i}
doesn’t work in Ruby.NET. Of course casting the float makes it work:
(1..Math.sqrt(x).to_i).each{|i| puts i}
Well guys, did you think about stopping praising that Smalltalk ripoff called Ruby and implement a proper Smalltalk VM on top of .net instead?