2 ms·
> It's a bit like those benchmarks that show that a language that's a subset of Ruby, performs much faster than actual Ruby. I think this is unfair to my work.
by chrisseaton 13y ago
> It's a bit like those benchmarks that show that a language that's a subset of Ruby, performs much faster than actual Ruby.
I think this is unfair to my work. It's true that it is an incomplete implementation of Ruby, but to a greater or lesser extent so are Topaz and JRuby. Charles Nutter independently identified the tricky parts of Ruby that you are talking about, and said that people should implement these before speaking about performance numbers. We went through that list and implemented all of them to at least the same standard as JRuby, with the exception of C extensions, we have a GIL and we can't yet run Ruby on Rails.
So for example you can redefine Fixnum#+, or do any other crazy monkey patching, and we will run at exactly the same speed. This is actually unlike JRuby, which has a special fastpath for call sites calling these methods that if you monkey patch will be turned off.
This is all covered if you watch the full video. If that's still unclear, please join us on the Graal mailing list and we can chat. http://openjdk.java.net/projects/graal/ http://openjdk.java.net/projects/graal/
- derefr 13y agoI actually wasn't referring to Graal at all (I didn't realize it had anything to do with Ruby.) I was thinking more of IronRuby (I think?) back when that project first started, before they had much implemented, when they came out with performance numbers. Whichever one it was, it was what spurred the controversy that Charles Nutter was reacting to by doing that.