According to my very unscientific measurements (I didn't bother looking which files are potentially auto generated), I got:<p><pre><code> 182kloc of C (.c files)
110kloc of c++ (.h + .cpp files)
558kloc of ruby (.rb files)
</code></pre>
That puts C/C++ at roughly 40% of total. Unless proven otherwise I would say "ruby written in ruby" is a bit untrue.
Awesome, the great thing about rubinius is playing around with the internals, since they're mostly written in ruby. The C++ core is quite tiny actually.
Obviously great news. It dampens my enthusiasm a bit to know the same company funds development of JRuby however.<p>EngineYard really should clarify their vision behind maintaining two VMs. Going beyond the obvious "JRuby is for integration with existing J2EE infrastructure" angle would be nice.<p>Under what circumstances would they actually stand behind Rubinius as the better choice? Is the MRI C extension API compatibility an official feature now? Is it that I could switch from REE to Rubinius without having to worry about finding alternatives for all the libs I'm using that carry C-extension baggage?