1. Does anyone know of a project that is implementing Ruby on the ..NET/Mono platform?
2. Do tools exist to port Python code to Ruby and vice versa?
3. Does a Ruby compiler exist similar to the python compiler for Java (Jython)?
4. How easy is it to interface Ruby to C/C++ class libraries?
1. Does anyone know of a project that is implementing Ruby on the .NET/Mono platform?
there is a proof of concept implementation, but nothing released.
Anyway you can use rubydotnet wich is an interesting bridge (it allows you to use every .net library but does not compile to clr)
I got it working and hooked into .NET (both straight-up objects and
WinForms stuff). It's neat, but I wouldn't use it for anything
production related. Also, I've only tested it on XP.
1. Does anyone know of a project that is implementing Ruby on the
..NET/Mono platform?
2. Do tools exist to port Python code to Ruby and vice versa?
3. Does a Ruby compiler exist similar to the python compiler for Java
(Jython)?
4. How easy is it to interface Ruby to C/C++ class libraries?
Not exactly but there is Groovy - if you need the looks of Ruby and the
speed of Java. See http://groovy.codehaus.org/
I've seen several posts that hint that Groovy runs at Java-like speeds. I haven't found this to be true at all. You can find one of my (very incomplete and probably totally useless) benchmarks here: Groovy - Groovy Speed
Don't get me wrong ... I think Groovy has a lot of promise for those living in the JVM world. However, it is still a very young language and has some growing to do.
···
--
-- Jim Weirich jim@weirichhouse.org http://onestepback.org
-----------------------------------------------------------------
"Beware of bugs in the above code; I have only proved it correct,
not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)
I've seen several posts that hint that Groovy runs at Java-like speeds.
I haven't found this to be true at all. You can find one of my (very
incomplete and probably totally useless) benchmarks here: Groovy - Groovy Speed
That's interesting, although I think you didn't choose optimal
implementations:
10:16:21 [source]: ruby /c/temp/ruby/fact-bm.rb
Ruby: 54.1 MicroSeconds per call
Ruby: 14.7 MicroSeconds per call
Ruby: 13.5 MicroSeconds per call
and
10:33:25 [groovy]: groovy fact.gr
Groovy: 67.2 MicroSeconds per call
Groovy: 59.4 MicroSeconds per call (HotSpot)
Groovy: 57.9 MicroSeconds per call
Groovy: 57.8 MicroSeconds per call (HotSpot)
Groovy: 57.8 MicroSeconds per call
Groovy: 57.8 MicroSeconds per call (HotSpot)