I'm not opposed to anything that seems like it might help bring more people to JRuby (and by extension, to Ruby). You can already access most of JRuby's interna

I'm not opposed to anything that seems like it might help bring more people to JRuby (and by extension, to Ruby). You can already access most of JRuby's internals via our Java integration layer, and that includes the AST, various core types, class structures and method tables, and so on. So much of this you could probably prototype without us adding anything. Beyond that, I'm interested in possible enhancements in JRuby to "over-optimize" code (like opting out of certain Ruby behaviors in a limited scope if they're just overhead for your app), and we're obviously always trying to improve how JRuby integrates with Java itself. So yes, there are many great plans...and user demand (especially paid users!) can make anything happen.