Chris Nelson
2007-08-17 18:32:59 UTC
Guys,
This sounds like an awesome list of stuff, but a feature that I think would
help a lot of with JRoR projects would be to improve the debugging
experience. Right now the only way to get JRuby on Rails debugging to work
in NetBeans is by setting an undocumented property in a config file. And
even then, it's quite buggy. From what I understand Netbeans needs to have
the fast debugger supported in JRuby before this situation will improve. I
would be willing to lend a hand on this if someone could point me in the
right direction. I've done a ton of Java and am doing more Ruby all the
time, but I'm not too familiar with the internals of JRuby or how this would
need to work.
Thanks in advance,
Chris
This sounds like an awesome list of stuff, but a feature that I think would
help a lot of with JRoR projects would be to improve the debugging
experience. Right now the only way to get JRuby on Rails debugging to work
in NetBeans is by setting an undocumented property in a config file. And
even then, it's quite buggy. From what I understand Netbeans needs to have
the fast debugger supported in JRuby before this situation will improve. I
would be willing to lend a hand on this if someone could point me in the
right direction. I've done a ton of Java and am doing more Ruby all the
time, but I'm not too familiar with the internals of JRuby or how this would
need to work.
Thanks in advance,
Chris
Here's the proposed 1.1 roadmap Tom, Nick and I came up with this
afternoon. Add remove as you see fit, we'll try to iron it out.
- compiler complete
- AOT compilation working with jrubyc
- stdlib all precompiled
- gem install precompilation
- virtual filesystem-inside-JVM (maybe) or hacked rubygems that can
run out of an archive
- performance improvement to be quantified...java integration,
execution, memory reduction
- yarv bytecode execution and compilation (maybe)
- AST sharing as an option (sharing across runtimes)...need to
explore AOT compilation and its (positive?) effect on memory too
- real threading brutalization, testably multithread-safe core
classes (maybe, needs heavy testing on many-core systems)
- Java API rubification, perhaps with require 'javax.swing' and so on
- RubyConf for release
I accept responsibility for the compiler stuff, and I'm confident I can
have it all done by then. The big remaining items are tough, but there's
two months.
All told, it should be a pretty wicked release.
- Charlie
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email
afternoon. Add remove as you see fit, we'll try to iron it out.
- compiler complete
- AOT compilation working with jrubyc
- stdlib all precompiled
- gem install precompilation
- virtual filesystem-inside-JVM (maybe) or hacked rubygems that can
run out of an archive
- performance improvement to be quantified...java integration,
execution, memory reduction
- yarv bytecode execution and compilation (maybe)
- AST sharing as an option (sharing across runtimes)...need to
explore AOT compilation and its (positive?) effect on memory too
- real threading brutalization, testably multithread-safe core
classes (maybe, needs heavy testing on many-core systems)
- Java API rubification, perhaps with require 'javax.swing' and so on
- RubyConf for release
I accept responsibility for the compiler stuff, and I'm confident I can
have it all done by then. The big remaining items are tough, but there's
two months.
All told, it should be a pretty wicked release.
- Charlie
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email