I was wondering if any jruby dev’s could give a run-down of the current
state of jruby 1.5 compatibility with ruby 1.9? And if you guys/gals
have done any performance tests recently, are there any gains from using
–1.9 vs --1.8 and if so could you elaborate on those?
Thanks,
Chris
On Tue, May 18, 2010 at 1:32 PM, Christopher Dancy
[email protected] wrote:
I was wondering if any jruby dev’s could give a run-down of the current
state of jruby 1.5 compatibility with ruby 1.9? And if you guys/gals
have done any performance tests recently, are there any gains from using
–1.9 vs --1.8 and if so could you elaborate on those?
Ruby 1.9 support has pretty decent coverage of most 1.9 core libraries
(cannot remember if we synched standard libraries recently or not).
Some language-level semantics are still somewhat messed up [98%
feature complete] (e.g more esoteric parameter stuff like: def foo(a,
(b,c)); …; end). M17n is mostly there in the code, but we have not
hooked it up properly. The performance is not so great because we are
still only running 1.9 mode in our interpreter only.
For JRuby 1.6 we will have good 1.9 support since we will be making a
push to finish it up. This should mean JITting as well, which should
make it at least as fast as our 1.8 support.
We strongly suspect next significant release after Rails 3 will
encourage Ruby 1.9.2, so we want to be ready to have even parity with
1.9 before that happens.
-Tom
–
blog: http://blog.enebo.com twitter: tom_enebo
mail: [email protected]
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Thomas E Enebo wrote:
On Tue, May 18, 2010 at 1:32 PM, Christopher Dancy
[email protected] wrote:
I was wondering if any jruby dev’s could give a run-down of the current
state of jruby 1.5 compatibility with ruby 1.9? And if you guys/gals
have done any performance tests recently, are there any gains from using
–1.9 vs --1.8 and if so could you elaborate on those?
Ruby 1.9 support has pretty decent coverage of most 1.9 core libraries
(cannot remember if we synched standard libraries recently or not).
Some language-level semantics are still somewhat messed up [98%
feature complete] (e.g more esoteric parameter stuff like: def foo(a,
(b,c)); …; end). M17n is mostly there in the code, but we have not
hooked it up properly. The performance is not so great because we are
still only running 1.9 mode in our interpreter only.
For JRuby 1.6 we will have good 1.9 support since we will be making a
push to finish it up. This should mean JITting as well, which should
make it at least as fast as our 1.8 support.
We strongly suspect next significant release after Rails 3 will
encourage Ruby 1.9.2, so we want to be ready to have even parity with
1.9 before that happens.
-Tom
–
blog: http://blog.enebo.com twitter: tom_enebo
mail: [email protected]
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Hey Tom,
Thanks for responding and I’ll look forward to jruby 1.6. Meanwhile 1.5
has been a great release. Thanks.
Sincerely,
Chris
Hi Christopher,
As Tom says the features are almost complete, my last count was 800
specs
failing more or less, most of them were new methods added to ruby 1.9
and
still uninplemented in jruby or M17n issues.
Cheers